How to QA custom events before sending them to the main project
New
Hi there,
When implementing custom events for a specific product, is there a QA/Staging environment within FullStory that they can be sent to for QA before they are ready for being sent to the main project? In other product analytics tools like Mixpanel and Amplitude, you are encouraged to create a project specifically for event data QA. This prevents potentially bad data from getting mixed with production-ready data. Does FullStory offer something similar?
0
Comments
2 comments
Hi @mentat-analytics! FullStory doesn’t offer QA or Staging environments, so most users choose one of two options for capturing data on multiple domains.
1. You could use a separate account for your QA work. This account would be totally independent (billed separately, with different quotas, settings, etc.); however, you could use the same username and password to log in for simplicity’s sake. Depending on how many sessions you need for testing purposes, our FullStory Freemium accounts are always a nice option. More details on what’s included with a free account here.
2. You could capture all sites into the same account and use segments to differentiate them. For example, you might have a "Site A" segment, which is a saved search of the form "Page host is ", and then another "Site B" segment that filters on another domain.
I hope this is helpful! Please let me know if you have any follow-up questions.
Got it, thank you for the explanation Megan!
Please sign in to leave a comment.