Note that words here follow old terminology.
In Chrome 89, a conversion destination is stored as a schemeful site of eTLD+1.
We have multiple service domains under one eTLD+1, and this change affects our conversion measurements.
In the following examples, example.jp has two services of shopping.example.jp and travel.example.jp, and each service has its own impression and conversion URLs.
As the figure below shows, its credit of 100 is attributed to the impression of travel.example.jp regardless of conversions on only order.shopping.example.jp.
It is better to set the FQDN of conversion origin in the conversion destination and select reporting conversions with the conversion origin to resolve this issue. But it might increase user tracking risk.
Alternatively, I think that we can introduce a new attribution of domain id to separate impressions/conversions under eTLD+1 and reduce the maximum impression data size to keep its entropy.
Or can #114 solve this issue by filtering conversion data?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3
