- Shipped
- 20 Agosti 2026, 04:41 UTC
- Author
- Kamo
- Commit
- 4bc6a72
The ingest worker now calls reattributeWhileAnonymous after the traffic bumps. The repository method carries the entire rule, so there is nothing to check here and no window to race through: a return of 1 means credit genuinely moved to the link this visitor just arrived on, 0 means they came back on the same one or they already have an account and their sponsoring member keeps them for good. Only the attributed code moves. The visit and page-request bumps have already credited the code that served this pageview, which stays true however attribution lands. A move writes an ATTRIBUTION_MOVED row on the visitor's timeline, after the page view so the two read in the order they happened. It is the only event in this feature that changes what a member is owed without anyone doing anything wrong, so it is worth stating outright rather than leaving to be inferred later. The signup handler resolves the code on the envelope and, when it names a live one, stamps the account and settles attribution in the same statement. That is the case the beacon can miss entirely — idle-deferred, at most once per pageview, and a visitor can follow a link and go straight to the register form. Retired codes resolve to null and leave attribution alone, so a link that stopped earning credit through the beacon cannot start earning it again through the signup door.