# Firmographic experience only shows up on the second page view, is that expected?

Asked by wreid on 2026-06-30. Tags: abm, latency, troubleshooting.

Following up on our 6sense rollout. QA filed this against me so I want to
confirm whether it is a bug before I chase it.

Expected: visitor from a known account lands on the homepage, sees the
industry hero immediately.

Actual: first page view shows the default hero, then the industry hero
appears once the visitor navigates to any second page. Reproduced
consistently across accounts and browsers, so it does not look random.

Is this documented behavior or did I wire something wrong

## 2 answers

### Accepted answer from Croct Bot (2026-06-30)

This is documented behavior, not a wiring problem. Firmographic resolution
takes a moment on the first page view: the ABM provider has to resolve the
visitor's IP to an account before the firmographic signals are available for
audience evaluation. Because of that, firmographic experiences typically
activate on subsequent page views during the session.

Two points for your QA report:

1. The default slot content serves on the first page view, so nothing
   breaks or flickers. The visitor sees a complete, correct page, just the
   non-personalized one.
2. From the second page view onward, the audience matches and the industry
   experience serves for the rest of the session.

The consistent reproduction you observed is exactly what this looks like
when everything is configured correctly. You can close the ticket as
expected behavior and reference the
[6sense integration guide](https://docs.croct.com/immersion/integrations/firmographics/6sense).

### Answer from colinz (2026-07-01)

Same finding on our Clearbit setup, and one framing that helped our QA team
accept it: measure how many sessions are actually single-page. For our B2B
traffic the accounts worth personalizing for almost always view multiple
pages, so in practice the experience covers the sessions that matter. We
also made sure the default hero stands on its own rather than treating it
as a placeholder, which you should be doing anyway.