Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.
Atribución
When are attribution shares recalculated?
Attribution shares are produced in runs, not on every page load. After changing the model or windows, the new values apply from the next run; late-arriving contacts also change an already calculated journey.
I changed the settings. Why do I still see the old numbers?
- A change to the model or windows takes effect from the next attribution run.
- Late events (for example from a locally buffered batch) can complete a journey after the fact.
- An executed Article 17 deletion retroactively reduces shares already reported.
- Refunds change the value of a conversion, not its attribution.
- When a calculation rule changes, the background run recalculates the affected conversions. Most recently on 25 September 2026: “Last non-direct click” no longer gives viewable impressions a share; conversions where it did are recalculated.
Note
Past figures being able to change is intended: a report that ignores late-arriving evidence is stable but wrong.
Revisado por última vez el 30 sept 2026
También se pregunta
- Why do numbers change retroactively?
- Attribution run
- Numbers are not updating
- Why did the figures under “Last non-direct click” change?
Artículos relacionados
- What are the click window and view window?
How long does a touchpoint before the conversion count?
The click window sets how long a click before the conversion still counts (30 days by default); the view window does the same for a viewable impression (one day by default). You set both under “Settings”, together with the default model.
- How long until data appears?
When do I see the first numbers after installing?
Individual events appear in the live test within seconds. Journeys and conversions are created during processing and usually appear within minutes; attribution shares are calculated afterwards.
- How do I handle access, deletion and objection?
A data subject exercises their rights. What do I do?
Privacy requests are handled in the portal under “Privacy”, not by ticket. Every request is recorded and logged in the change log; the data subject is located through a pseudonymous identifier.