Why Pathmonk doesn't show microexperiences to every user?

Sometimes you may notice that a user, or even yourself when testing, appears in the Pathmonk enabled group, even though no microexperience showed up during a particular visit. This is normal behavior and part of the scientific validity of the A/B testing.

1. You're part of the Control group

When someone lands on your website for the very first time, Pathmonk creates a unique fingerprint and assigns them to one of the two experiment groups:

• A – Control group (no Pathmonk experiences)

• B – Pathmonk-enabled group (eligible to receive microexperiences)

If a visitor has been assigned to the control group, they will never see microexperiences. 

2. A/B testing works at the user level, not the session level

The assignment to one group or the other is “sticky”, so it follows the fingerprint across their entire buying journey, meaning:

• If the visitor is assigned to group the Pathmonk-enabled group on their first visit,

• They will remain in that group on every future session, regardless of whether a microexperience triggers or not in their later or first visit.

Example:

1. Day 1: A new visitor enters your homepage for the first time → Assigned to Group B but leaves before doing anything and before Pathmonk show something.

2. Day 2: They return, browse 3 pages, and a customer testimonial shows up.

3. Day 7: They revisit and make a purchase.

Even if Pathmonk didn’t show anything on Day 1 or Day 7, their conversion will still be counted under Pathmonk-enabled traffic, because that was their initial assignment and the test only showed a personalized experience when it predicted it was needed.

3. Pathmonk optimizes for accuracy, not for showing experiences every time

Pathmonk's AI only triggers microexperiences when they are likely to have a positive impact and avoid friction, so if the system detects that a user:

• already has a clear intention to purchase,

• is navigating efficiently,

• or doesn’t show behavioral signals that require assistance,

…it may intentionally decide not to show anything, but the visitor still belongs to the experiment group, and their conversion rightfully counts toward it.

Example:

A user goes straight to the pricing page → then completes the form, because the journey is already clean and predictable. Pathmonk doesn’t intervene, still, that user is counted as Pathmonk-enabled because they were originally assigned to group B.

4. Why you might not see an experience yourself?

When testing your own site, it’s common to expect microexperiences to appear immediately. But depending on how the AI reads your behavior, it might decide not to show anything. Some factors that triggers this behavior may include:

• visiting predictable, goal-oriented pages (e.g., Pricing → Checkout)

• navigating too quickly

• triggering patterns that don’t match any experience rules

• already having converted in the past

• using browser autofill or shortcuts that bypass behavioral cues