Anonymous decision progression interpretation

Install

One script tag for anonymous progression interpretation. Your stack wires GTM, Adobe, or React — nested events by default; Optiview does not change the site automatically.

Optiview does not claim to know who the visitor is. It helps teams understand where anonymous progress may be slowing.

Signals strengthen as the visit evolves.

Default: nested events, not automatic GTM variables

On each meaningful change, the tag updates a nested si object and fires browser events (si:personalization-signal). Your rules listen to those events or read SessionIntel.getActivationPayload().

Optional: call pushCommercialSignalsToDataLayer() when you want flat GTM-ready keys (si_context_*, si_commercial_state_id, etc.).

What you get

Tag live in about an hour. First experience rule when your team is ready.

How to read the tag

Observed — What the visit shows — traffic source, device, timing, and browsing pace.
Inferred — What behavior may suggest — hesitation, comparison loops, slowing momentum (heuristic, not certain).
Suggested — What your stack could do — calmer modules, clearer next steps. You own rendering; Optiview does not change the site automatically.
Not known — Identity, exact location, weather, and personal details. Some fields stay unknown early in a visit; interpretation strengthens as the session evolves.

One script tag

Place before the closing body tag on pages you want to instrument.

HTML

<script async src="https://cdn.optiview.ai/si.js" data-si-key="YOUR_SNIPPET_KEY"></script>

Connect to GTM (optional flat keys or event listener)

// After the tag boots — optional flat keys for GTM Data Layer Variables
window.SessionIntel?.pushCommercialSignalsToDataLayer?.();

// Or listen without flattening:
window.addEventListener("si:personalization-signal", (e) => {
  const si = e.detail?.si;
  // branch on si.commercial_signals.commercial_state_id, si.context, etc.
});

Integrations →

Verification and developer reference

Confirm the tag with window.SessionIntel. Default emit: custom events and getActivationPayload() — not automatic flat si_* variables unless you push them.

Technical reference → · Emit catalog →