A/B Testing for Copilot
None
We are looking for an easy way to split a power list in half to send a message to one sub group and a slightly different one to another sub group to compare the results. Of course, we can set up a flag and populate it. I am just looking to see if we can do it easier than that. Is this something we have considered as a feature for copilot?
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Steps below as follows:
This is just one example. You could use the basic principle on any field data that is present on all accounts and I'm sure some may even devise more complex methods using the other statistical functions like Correlation, Covariance, Std Deviation/Variance and Median.
Average should be used with caution as a single large outlier can skew the entire dataset's mid point.
Would you have a minute to look at my transformations? For some reason this survey failed to send… was trying to use this A/B suggestion.
I’ve included the sources attached here
HI@scott_sigsci - at your last step you are aggregating by company ID name, which instead of pulling in the email address and other relevant data of your contacts, is showing the count and sum of those values. You’ll want to remove that aggregation.
So close... I’ll remove that and have another go. Thank you @dan_ahrens
Hi Scott, without working in your org specifically, it’s hard to dig very deep on troubleshooting and advising using screenshots, but you might find it helpful to do that field length calculation in it’s own step and then merging that data back in with your other company data. Your Gainsight Customer Success Manager can probably work 1 on 1 with you to tune this query.
Thank you@dan_ahrens , much appreciated.
In any case, I think it would be great to have the fork functionality that@dale_parent suggested above. Having that option directly in the flow and, ideally, also being able to compare the results directly in the Analytics would be absolutely amazing!
Do posts tagged ‘Work around available’ ever get revisited? This would be nice to have as an actual feature and not a 3 task transformation. It also doesn’t solve for powerlists or segments, as that feature grows in adoption.
We are looking at some options to do this in Journey Orchestrator and might have some more updates closer to the start of the new year.
Is there any update to make this a feature? All of our account IDs are exactly the same length, so this crazy complicated workaround is really not feasible for us. It would be really helpful to have this as a feature with similar parity to other email systems where I can just configure the A/B settings and let it deploy with randomization.
This would also help with company conversion. My marketing team is showing more interest in using JO rather than Marketo for certain drip campaigns and surveys, but this is a basic functionality they use all the time.
This is a feature that is being planned for 1H 2021.
Hello! I wanted to follow up and see if there was still hope for this to be a feature in JO? Our company would love to start doing some A/B testing as we bring more complicated programs into Gainsight and adding the additional transformations would complicate things a bit leaving more room for error when trying to complete the testing.
Hello! I wanted to follow up and see if there was still hope for this to be a feature in JO? Our company would love to start doing some A/B testing as we bring more complicated programs into Gainsight and adding the additional transformations would complicate things a bit leaving more room for error when trying to complete the testing.
Hello@anirbandutta and everyone on this thread!!
Despite being on our backlog, this requirement was not picked up due to other conflicts. Although this is a valuable addition to the platform, we will not be able to implement it anytime soon.
If it helps, I’d like to suggest an alternative solution (can share more details if needed) -
Thank you.