Skip to main content

As a new user, I found this one a bit tricky…

My context

I had a guide that I needed to fix and it workshopped the (somewhat “major”) fixes in a clone of the original guide, as I wasn’t quite sure what the fix was going to be and I needed the option to test and iterate without losing the original guide. 

Once I had the fix identified, I wanted to pause the v1 guide and launch the v2 guide, but exclude those who saw v1 from the audience. 

The Solution

It’s neither ideal nor elegant, but the In-App Engagement rules allow you to set rules based on the number of times they {action: completed/viewed} the guide. If you set either or both of those to less than 1, it will exclude those who saw the first one. 

 

Hi ​@DannyPancratz 

Thank you for writing on community!

Unfortunately, there isn’t another way to directly target users who have viewed one engagement in order to exclude them from seeing another.

As mentioned earlier, using the "In-app engagement viewed < 1" filter is the best approach to target users who haven’t seen a specific engagement. I don’t believe adding "Completed < 1" is necessary in most cases, but including it won’t significantly change the targeting if you choose to add it.

Let me know if you’d like help setting up the filter!

Great call out, ​@DannyPancratz!

This logic can also be leveraged for surveys when seeking to avoid user fatigue and facilitate fresh insights from a diverse customer base. We’ve used this logic for multiple survey engagements. 

Terms & ConditionsCookie settingsAccessibility statement