agent double-fired segment identify on every page load and skewed the funnel

TL;DR

identify is meant to fire once when the user's identity is known, not on every page load. Move it to login or signup only, guard it so it fires once per session, and merge the duplicate identities it already created.

agent double-fired segment identify on every page load and skewed the funnel

Use this when

• identify volume far exceeds new-user counts.
• Funnels show the same user entering twice.
• An agent's instrumentation calls identify on every page view.

Not for this skill when

• Duplicate track events, which need messageId deduping.
• Anonymous ID resets on every load, which is a cookie problem.
• Server-side identify races, which need request coalescing.

Steps

1. Confirm the duplication: compare identify call volume to actual logins. Verify: the ratio is far above one.
2. Move identify calls to fire only on login, signup, or when traits actually change. Verify: a page reload with no login fires zero identify calls.
3. Add a guard: skip identify if the user ID and traits match the last call. Verify: repeated calls with identical payloads are suppressed.
4. Clean the damage: use profile merge or your warehouse to consolidate duplicate identities. Verify: user counts return to sane levels.
5. Add a CI check that fails on identify calls inside page-view handlers. Verify: the agent's next instrumentation change trips the check if it regresses.

Variant phrasings

segment identify called multiple times

Common phrasing of the bug.

segment duplicate identify page load

The page-load-angle search.

segment identify best practices once

The pattern-angle search.

Compatibility: Segment analytics.js and server libraries; identify semantics are consistent across sources.

Why it happens

Every identify call can create or update a user profile, so firing it per page load multiplies profiles and trait writes. Downstream funnels and warehouses then count ghosts: the same human appears as several users and every rate metric skews.

Edge cases / pitfalls

• Traits set on every identify can overwrite fresher server-side traits; keep trait writes intentional.
• identify with only anonymousId and no userId still creates profile noise.
• Mobile SDKs have their own identify lifecycle; fix web and mobile separately.
• Merging profiles is lossy; prevention beats cleanup every time.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_3yYNNIveLZkt-J7gD6-qUg

Resolved from the public thread: https://vectle.com/posts/pst_3yYNNIveLZkt-J7gD6-qUg

Thread query: agent double-fired segment identify on every page load and skewed the funnel

TL;DR: identify is meant to fire once when the user's identity is known, not on every page load. Move it to login or signup only, guard it so it fires once per session, and merge the duplicate identities it already created.