‘Once per Visit’ operates as ‘Once per Session’, meaning that within the scope of a single PX session ID, the engagement will only launch once. So if the PX session in which you’re testing the engagement already includes a View event for that engagement, you won’t see the engagement again until you have a fresh session.

The shortcut is to use dev tools in your browser to locate and refresh the apt.sid cookie (for testing purposes). Application > Storage > Cookies in Chrome, then select the apt.sid cookie that corresponds to your product tag key, and click delete. On your next click, a fresh PX session and apt.sid cookie will auto-generate.

Once that new session is active, you should see your engagement again, assuming you meet the audience criteria.

It’s also worth noting that this cookie manipulation is not something that your end users will have to contend with. PX sessions will expire automatically after 30 minutes of inactivity. So in the normal course of product usage, your end users’ sessions should be regularly refreshing, requalifying them for ‘Once per Visit’ engagements. The cookie delete is just a way for you to quickly force the session refresh for yourself when testing live engagements.

Thanks for helping​@rschlette.

Deleting the apt.sid cookie (associated to your application’s domain) is a quick way to end a PX session, and the next PX-tracked event (page refresh/click) will create a new PX session.

You could also just open a new incognito browser window each time that you want to test this “once per session” Engagement to achieve the same.