paidAffiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. A desk about how a screen is measured and tested should not leave its own funding unsaid: one link funds the site, no operator and no product is named, rated or recommended anywhere on it, and this site runs no analytics of its own on its readers.
The Test Group / The vendors
One tag on one page, and everyone it notifies
The vendor chain behind one tag
The event is produced in one place and consumed in several. A tag on the page passes it to a manager, which forwards it to a platform, which feeds a dashboard, a replay tool and sometimes an advertising pixel. On the samples the reader makes one choice and four companies receive the result.
Desk spec
- vendors from one tag
- 4
- retention range
- 14 to 400 days
- events a month
- 535.7 GB
- vendors named in the notice
- 2 of 4
the eventOne interaction, written down. A click carries a name, a time, an account, a session and what was on the screen, and it is kept whether or not the reader chose to be measured.
the funnelThe order the steps happen in. A landing visit becomes an account, an account becomes a deposit page, and 100,000 visits end in 2,074 first bets - a 2.1% path the whole loop is aimed at.
the armsTwo versions of one screen shown at the same time, and a rate for each. 4.30% against 5.16% is a 0.86-point lift, and the interval decides whether it is a result or a coincidence.
Direct answerBehind one analytics tag is a chain: a tag manager on the page, an analytics platform that counts, a replay tool that records and often an advertising pixel that re-identifies. On the samples one consent choice feeds four companies, two of which are named in the privacy notice, and their retention ranges from 14 days to 400.
The chain, hop by hop
Each hop has its own purpose and its own contract, and the reader's relationship is usually with the first party only. The chain is why "we do not share your data" and "we use partners" can both appear in the same notice without contradiction.
Sample B - one event, four recipients
| Hop | What it receives | Retention | Named in the notice? |
|---|
| the tag manager on the page | the raw event | none, it forwards | no, it is "our tooling" |
| the analytics platform | the event plus an account id | 400 days | yes |
| the replay tool | the event plus the screen state | 30 days | often only as "analytics" |
| the advertising pixel | the event plus device and referral | 14 days | yes, in the advertising section |
| one choice, four recipients | - | 14 to 400 | 2 of 4 clearly |
sample B - the same event, four retention windows
events a month = 535.7 GB
share that is page-level and replay = 34.0 GB a week, 145.9 GB a month
analytics platform holds 400 days = 535.7 GB x 13.1 months = 7,017.7 GB
replay tool holds 30 days = 145.9 GB
advertising pixel holds 14 days = a copy of the referral, not the session
so the longest window is 13.9 times the shortest, for the same
event, decided by which vendor received it rather than by
what the reader chose.
and a deletion request has to travel all four hops to be complete,
which is the practical reason one is often only partly honoured.
What a vendor is for, and when it is the wrong tool
Each hop exists because it solves a problem the others cannot. The tag manager exists so the page does not need a developer for every change, the analytics platform so the counts are joined, the replay so a gap can be looked at, and the pixel so a reader who left can be found again. Only the first three are the loop's own instruments.
Sample B - the four vendors against the question each answers
| Question the loop asks | Which vendor answers it | Could the loop work without it? |
|---|
| which step did they leave? | the analytics platform | no, this is the funnel itself |
| why did they leave? | the replay tool | with difficulty, and the desk's own samples show it is barely used |
| how do we change the page quickly? | the tag manager | yes, at the cost of developer time per change |
| how do we reach them again? | the advertising pixel | yes, and it is not part of the loop at all |
| the loop's minimum | the platform, and arguably the replay | 2 of 4 |
sample B - the share of the chain the loop needs
vendors behind one tag = 4
required for the funnel to exist = 1 (the analytics platform)
useful but marginal = 1 (the replay, watched on 2.1% of sessions)
not part of the loop = 2 (the tag manager and the pixel)
so half the chain, including the vendor with the shortest window
and the widest reach, is there for reasons other than the
measurement the reader is told about:
2 of 4 = 50.0%
and a reader who wants to limit exposure has to reason about the
whole chain, because the banner describes one choice.
The vendor count, the retention windows and the naming counts are invented. Which companies a named operator uses, what each is called in its notice and how long each keeps what it receives are facts in its own documents and in its contracts; the desk's claim is only that one choice travels a chain, and that the chain is longer than the choice suggests.
Reading a notice for the chain rather than the headline
- Look for a list of named processors, not the sentence about "trusted partners".
- Check the retention line per category, because one window rarely covers the chain.
- Check whether session recording is named at all, since it is the broadest of the four.
- Check whether an advertising pixel fires before or after a consent choice, and from which vendor.
- Send a deletion request and ask it to be confirmed for each named processor.
Read next