For the Power Users & Layman Optimizers Alike
Overall Satisfaction with Convert Experiences
In layman's terms, when we want to do an experiment very quickly but need to target accurately, we turn to convert.
While Convert's WYSIWYG editor is really great, we actually almost exclusively use it in the custom JS / CSS modes. It's incredibly powerful with regard to being for engineers and your non-technical marketers.
We use it for:
- Feature Validation
- Testing the riskiest assumption from Product teams
- Lifting specific Pirate (AARRR) growth metrics
- Audience targeting IN ADDITION to all that fancy DMP targeting. This means I can define demographics or other data as a qualifier AS WELL as the previously mentioned qualifier. This can be setup in so many ways: Traffic source, Visitor Data, Include / Exclude users part of a current experiment (!!), Date/Time, Device/Browser/OS, JS Conditon
- Real-time reporting that makes sense to the whole company to view. Seriously, I can share a Convert Report to any level of intelligence on my team and they understand what's happening.
- Audiences and Goals are saved as presets, so your entire team can use them. Using the example above, we have an audience called "Wrote a Review" that we exclude from the Review Prompt treatments.
- Their customer support is seriously fast at answering questions. I've never had to wait more than a day.
- You will immediately experience frustration (at least as a developer using JS Conditions) with the CDN times. Experiments often don't appear to you after saving new JS for up to 5 minutes. This can be crazy painful if you're going from Local Development > Staging > Production.
- There are some minor UI quirks inside the experiment editor if you're using the more advanced features like we do.
- It's almost mandatory that you're onboarded by a human. There's so much to this tool it'd be pretty hard for you to just dive in like some other apps. If you're like me that can be a bit frustrating. Some people need that though and enjoy the human touch, so I hate even giving this as a negative.
- We've lifted retention every month, mostly through discovery of this tool.
- We generated 9,000 reviews off one experiment. After many rapid and fast learnings from failed experiments of course ;)
- It has freed my whole department up to move as fast as we want to move. It overcame every single technical hurdle we had faced after going through 3 different injection tools and being priced out of 2 others.
I feel like I've gushed a lot about the DMP and power user features of Convert in other questions, so I'm going to leave things a little sparse here.
- Non-technical Marketing Teams
- Fast moving Growth Teams
- Really technical experimenters and optimizers that are frustrated with the lack of technical targeting most tools provide (this was me)
- Teams wanting to run lightweight to medium weight technical experiments but don't want to impact the development cycle or wait for the development cycle to add their experiments.
My entire job function is speed and throughput of growth experimentation, so I can't honestly testify to what it isn't suitable for.
Using Convert Experiences
- Directionally experimenting to quickly / cheaply find where we should pivot to lift metrics.
- Feature Validation
- Using the DMP Profiling, we've been able to really quickly patch a bug while we let Dev get caught up to the problem.
- Sales "What-if" scenarios and demos
- 3rd party data integrations
Convert Experiences Support
Problems get solved
Immediate help available
Support understands my problem
Support cares about my success
Quick Initial Response
Just curious how often a unique visitor is able to trigger a goal.
Is it 1x per unique user? Or is it 1x per unique user session?
I feel like it's 1x per unique user based on my testing, but I would just love to clarify and be sure.
Only once. When a unique visitor is bucketed to the experience, he/she can trigger the goal once. Next time that he/she will match the conditions of the goal, nothing will happen.
Let me know if you have any other questions,