We’ve added a badge trigger to our NPS survey as an on-demand option for those who don’t want to respond via the random automatic triggers. 

To do this the badge visibility is set to Always. 

Once they respond, the Schedule > Qualification Scope > Intervals should prevent them from seeing it again for a few months. As a back up, I have an automation that also updates a field that’s part of the Audience criteria; which should make them ineligible to see the badge. 

In my testing, I’ve noticed that there can be a bit of a lag for the system to re-evaluate the user’s qualification for the engagement and hide the badge. Not a big deal, but we did have one user respond five times this evening within a short time span. 

My question: are there faster, more effective ways to update the audience criteria to hide the badge and prevent users from having this option? If I send a Custom Event occurrence, would that be more effective (for Audience criteria toexclude the user) than updating the User Attribute I’m using? 

My hypothesis is that the lag comes from the natural cycle of when engagement qualification happens. And that the response to the NPS survey doesn’t trigger one of those; for example, the page doesn’t reload.

Anyone have any advice?