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
{{ message }}
This repository was archived by the owner on Mar 16, 2023. It is now read-only.
As per the qualifying user's definition I do not see the feature & js API working in the latest chrome release 89.
The chrome feature status also states this as behind developer flag. I was able to force enable API using blink feature but doesn't seem to be ideal for OT.
Can we please elaborate on the Origin Trial scope and coverage around following:
Is this FloC data available by default to only Chrome/Google at scale through account sync?
How can any publisher , ssp , advertiser analyse the floc data at scale during OT phase?
Will this ID / API be available for all qualifying users or there are other sampling / selection criteria?
There was an initial proposal to expose this through headers as well - sec-ch-flock is that still in roadmap?