Sessions

What happened after the click?

Every index in this product ranks something — platforms, campaigns, browsers, connections. This is the one screen that ranks nothing: a single paid visit, opened, with the tagging it arrived on, the walk it took through the site, and every event in the order it actually reached us.

intelligenceads.io/org/acme-dtc/site/acme-fr/?session=s_4b1e90d7c2af
Overview

Aug 22 · 20:41

s_4b1e90d7c2Aug 22lasted 7mwindow last 30 days

Campaignspring_2026_retargetingBrowserv_8f2c41Address192.0.2.203Consent thenMarketinggrantedAnalyticsgranted
Pages5
In-page activity7
Billed clicks1
Conversion€129.007m after the click

Conversion

€129.00+7m after the click
WhatproductVeste en lin écrusizeMthe custom_props your site sent with it
Fired onMerci pour votre commande/commande/confirmationpage 5 of 5 in this visit
IdA-20418the conversion id your site sent
The road to it7m and 5 pages from the click
+7m · €129.00
Veste en lin écru2mVotre panier1mPaiement3m
0 · the ad click7m · last event

Arrival

The tagging this click carried, and the network it connected from.
The clicktagged landing
Landinghttps://acme.fr/collections/vestes-mi-saison?utm_source=facebook&utm_medium=paid_social&utm_campaign=spring_2026_retargeting&utm_content=carousel_3&fbclid=IwAR3nQ8yV2pK7dLm4xRthe full URL as the browser reported it, parameters included
Taggingsource=facebook · medium=paid_socialvia Feedad carousel_3what the campaign, ad and search term were tagged as
Referrerhttps://l.facebook.com/what the browser reported on arrival
Ended on/commande/confirmationthe last page the visit reported
The connectionmobile
NetworkHome internet · Freeregistered as a isp network
PlaceLyon, FRAuvergne-Rhône-Alpes · postal 69003 · ~20 km
ClockUTC-2· Europe/Paristhe browser's own clock, beside the zone the network resolves to

Pages

Every page the visit opened, in order, with how long the visit stayed on each one.
Journey5 pages
  1. 47sVestes mi-saison/collections/vestes-mi-saison68%
  2. 2mVeste en lin écru/produits/veste-lin-ecru91%
  3. 1mVotre panier/panier44%
  4. 3mPaiement/commande100%
  5. ended hereMerci pour votre commande/commande/confirmation52%converted here · €129.00

Each bar is that stay against this visit's longest — shapes compare within the visit, not across sessions. The last page has none: no later page view bounds it.

Events

The raw sequence as it arrived, page views, scrolls, clicks and conversions.
Timeline14 events
AtEventWhere
0sPage view/collections/vestes-mi-saison
+12sScroll50%
+31sScroll68%
+47sPage view/produits/veste-lin-ecru
+1mScroll40%
+1mClick
+2mScroll91%
+3mPage view/panier
+3mClick
+4mPage view/commande
+4mScroll100%
+5mConversionsecondary
+7mPage view/commande/confirmation
+7mConversionprimary · €129.00id A-20418
Page view0s/collections/vestes-mi-saison
Scroll50%+12s
Scroll68%+31s
Page view+47s/produits/veste-lin-ecru
Scroll40%+1m
Click+1m
Scroll91%+2m
Page view+3m/panier
Click+3m
Page view+4m/commande
Scroll100%+4m
Conversionsecondary+5m
Page view+7m/commande/confirmation
Conversionprimary · €129.00+7mid A-20418

Unfiltered — a single-page app can report the same page twice on one transition, and those repeats are shown here where the journey above folds them. A path prints on every page view and whenever it changes; the rows under it are on that same page.

One visit of the browser on the Visitors page — the fifth billed click of that week, and the one that finished. Six and a half minutes, five pages, fourteen events, ending on a purchase the site’s own dataLayer named.

Demo workspace, fictitious data.

The walk, and the sequence under it

Two objects, on purpose. The journey folds a single-page app’s repeated fires away, because a reader following the visit does not want to see the same path four times. The event log does not fold anything — it is the sequence exactly as it arrived, which is the only view that is any use when what you are debugging is your own tagging.

The landing URL, parameters and all

One grain up, the log prints the path. Here it is the whole URL, because the ad platform’s parameters ride the query string — the click id, the source, the campaign, the creative. This is the screen where you can read what your ad actually sent, rather than what your tag manager was supposed to keep.

Two clocks, side by side

The browser’s own UTC offset, and the timezone the connection resolves to. They usually agree. When they do not, both are printed and neither is scored — a phone on a plane, a laptop that never left a previous holiday, a masked exit on another continent all produce the same disagreement, and only you know which one you bought.

The refusal

We never show a consent choice that was not true at the time.

A browser’s consent state is easy to fetch: ask what it chooses now. Every screen that shows one visit beside one banner decision is doing exactly that, and it is quietly wrong — a visitor who accepted a banner on Thursday did not accept it for the click you bought on Monday, and printing Thursday’s answer next to Monday’s visit states something that was never the case.

So this screen asks a narrower question: what governed THIS visit? — the latest choice observed at or before the moment the session began, and nothing after it. It is one clause in one query, it is invisible on screen when the answer happens to be the same, and it is the difference between a record and a reconstruction. There is a test whose only job is to stop someone tidying it away.

Boundaries

What the free plan shows you.

On this screenStarter and up
Opening a sessionOpenOpen
The walk and every event, in orderShown, uncappedShown, uncapped
The landing URL and its parametersShownShown
The consent that governed the visitShownShown
City and regionShownShown
The address it arrived onMasked to its network prefixIn full
The provider behind itShown
Postal area and placement accuracyShown

The screen is never refused and the timeline is never shortened: a plan does not buy you more of the visit, it buys the identity around it. What a plan does bound is which sessions you can still reach — seven days back on Free, ninety-two on Solo. Every event is kept on every plan, so a wider window opens visits already recorded rather than starting a new collection.

See where your ad budget really works. Then put more there.

Free plan, no credit card, no trial timer. Install in under 5 minutes — drop a script, load a page, and watch your first observations arrive.

Start free
We observe sessions, not people · No PII fields at ingest · EU-hosted (Paris)