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.
%22%20d%3D%22m24.49%2037.3c14.24-21.95%2034.79-37.3%2058.36-37.3%2013.65%200%2027.22%204.04%2041.39%2015.61%2015.5%2012.65%2032.02%2033.48%2052.63%2067.81l7.39%2012.32c17.84%2029.72%2027.99%2045.01%2033.93%2052.22%207.64%209.26%2012.99%2012.02%2019.94%2012.02%2017.63%200%2022.03-16.2%2022.03-34.74l27.4-.86c0%2019.38-3.82%2033.62-10.32%2044.87-6.28%2010.88-18.52%2021.75-39.11%2021.75-12.8%200-24.14-2.78-36.68-14.61-9.64-9.08-20.91-25.21-29.58-39.71l-25.79-43.08c-12.94-21.62-24.81-37.74-31.68-45.04-7.39-7.85-16.89-17.33-32.05-17.33-12.27%200-22.69%208.61-31.41%2021.78z%22%20%2F%3E%20%3Cpath%20fill%3D%22url(%23b)%22%20d%3D%22m82.35%2031.23c-12.27%200-22.69%208.61-31.41%2021.78-12.33%2018.61-19.88%2046.33-19.88%2072.95%200%2010.98%202.41%2019.41%205.56%2024.51l-26.48%2017.44c-6.8-11.31-10.14-26.15-10.14-43.06%200-30.75%208.44-62.8%2024.49-87.55%2014.24-21.95%2034.79-37.3%2058.36-37.3z%22%20%2F%3E%3C%2Fsvg%3E)
Meta- the click
- 5
- 6m 43s
- €129.00
Place in the journey
- PaidAug 22 · 20:41
EmailAug 23 · 08:12
Page journey
Click a page to read it in Details and in the table below. The figure on each arrow is the time between two page views — measured, not reading time. Columns are in time order, not to scale; the timeline keeps the scale.
Pages & observed signals (5)
| # | Page | Opened | Until next page | Deepest scroll | Other signals |
|---|---|---|---|---|---|
| 1 | Vestes mi-saison | 20:41:09 | 47s | 68% | — |
| 2 | Veste en lin écru | 20:41:56 | 2m 01s | 91% | — |
| 3 | Votre panier | 20:43:57 | 1m 08s | — | — |
| 4 | Paiement | 20:45:05 | 2m 42s | 100% | secondary |
| 5 | Merci pour votre commande | 20:47:47 | ≥ 5s · exit not observed | — | €129.00 |
One row per page of the graph above — the same pages, the same numbers. An order form that keeps its path and moves a query key (step=) is one row per step. Until next page is the gap to the next page view: measured, not reading time.
Conversion
Session timeline
The visit to scale — each page as long as the visit stayed on it, every event at the second it arrived.The last page is drawn open: nothing after the visit’s last event is observed, so its exit is never invented. Hover any mark for its exact second.
Events (14)
The raw sequence as it arrived — page views, scrolls, clicks and conversions.| # | At | Event | Details | Page |
|---|---|---|---|---|
| 1 | 0s | Page view | ||
| 2 | +12s | Scroll | 50% | |
| 3 | +31s | Scroll | 68% | |
| 4 | +47s | Page view | ||
| 5 | +1m 03s | Scroll | 40% | |
| 6 | +1m 28s | Outbound click | ||
| 7 | +1m 36s | Scroll | 91% | |
| 8 | +2m 48s | Page view | ||
| 9 | +3m 10s | Outbound click | ||
| 10 | +3m 56s | Page view |
Unfiltered — a single-page app can report the same page twice on one transition; those repeats show here, where the Pages table folds them. A path prints on every page view and whenever it changes.
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.
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.
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.
What the free plan shows you.
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.