You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To compute attribution results in the PCM protocol, the destination domain (i.e., advertiser website) must make a HTTP request to all possible ad source domains (i.e., publishers). This places the burden on the publisher and destination domain.
Some publishers, small businesses in particular, may not have the ability or resources to manage this. PCM has proposed a new JavaScript API to resolve this issue. This suggested approach, however, will raise implementation costs and slow adoption of the PCM privacy-based measurement methods. We recommend enabling trusted ad tech partners to support this functionality, allowing publishers to define the attribution origin of a conversion event.
The text was updated successfully, but these errors were encountered:
I just wanted to add a strong +1 here. Many publishers rely on ad tech partners for their campaign optimisation/measurement, and not having a good option to receive the attribution reports outside of the click source domain feels like a major blocker to adoption.
To compute attribution results in the PCM protocol, the destination domain (i.e., advertiser website) must make a HTTP request to all possible ad source domains (i.e., publishers). This places the burden on the publisher and destination domain.
Some publishers, small businesses in particular, may not have the ability or resources to manage this. PCM has proposed a new JavaScript API to resolve this issue. This suggested approach, however, will raise implementation costs and slow adoption of the PCM privacy-based measurement methods. We recommend enabling trusted ad tech partners to support this functionality, allowing publishers to define the attribution origin of a conversion event.
The text was updated successfully, but these errors were encountered: