Unexpected Repeat Display Behavior in Web Intercepts

Question

I have several web intercepts running in my project, but I’ve been experiencing strange behavior in how they’re being displayed, which led the client to request that all of them be disabled.

These intercepts each have only one action set, and all of them follow rules similar to the example below.

In addition, I have repeat display prevention enabled, with the browser cookie set for 14 days.

Even so, I’m receiving reports that the intercepts are being displayed every single time the user accesses the target URL.

I’m not exactly sure how to proceed or where to start investigating this.

Has anyone experienced something similar and can share their two cents?

vgayraud · Accepted Answer

Hi,AND statements are evaluated before OR statements, so what you’re evaluating now is “A OR (B AND C)” and not “(A OR B) AND C”. Maybe that’s what you want, but seeing how A and B are based on the URL, it might not be what you had in mind.To check that cookies are correctly set, use your browser devtools (in Chrome, F12 / Application / Cookies).Best,

cami_mq · Answer

​@vgayraudThank you!We reviewed some of the rules to improve performance and add a bit of redundancy for safety.But at the end of the day, the intercept configuration was using session-based storage. These intercepts are shown on logged-in pages. Every time the user logs out, the session resets — which is why the intercept displayed again every time the user accessed the page.We changed that strategy and, apparently, things are behaving much more smoothly now. We disabled all intercepts and are reactivating them gradually under an assisted-operation approach, monitoring intercept statistics, dashboard comments, and direct reports from the responsible stakeholders to validate everything as we bring them back online.

Sign up

Login to the Community

Scanning file for viruses.

This file cannot be downloaded