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
I understand the following from the public documentation on the Attribution API:
The API does not rely on third-party cookies. However, in the testing phase, third-party cookies need to be enabled for the API to be enabled.
My question is whether we are still in the testing phase or is this API now enabled independently of third-party cookies? If it's the former, then when do you anticipate that this API will be enabled for all (who haven't opted out). Also, could you clarify whether this would be opt in by default? Thank you!
The text was updated successfully, but these errors were encountered:
Thanks for the question. To clarify, the API is enabled independent of third-party cookies, but third-party cookies need to be enabled to enable transitional debug reporting to compare the API results with cookie-based attribution.
Ok that's great, thank you for confirming. Are there stats on the percentage of Chrome traffic that has the Attribution API enabled? Is it on by default?
Ok that's great, thank you for confirming. Are there stats on the percentage of Chrome traffic that has the Attribution API enabled? Is it on by default?
I understand the following from the public documentation on the Attribution API:
The API does not rely on third-party cookies. However, in the testing phase, third-party cookies need to be enabled for the API to be enabled.
My question is whether we are still in the testing phase or is this API now enabled independently of third-party cookies? If it's the former, then when do you anticipate that this API will be enabled for all (who haven't opted out). Also, could you clarify whether this would be opt in by default? Thank you!
The text was updated successfully, but these errors were encountered: