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
One of the key items we identified as a likely essential extension to a core attribution API was the ability to have the API invoked as a side effect of ordinary HTTP requests. That's how the business operates today with its pixels and whatnot.
Things get a little gross when you want to have the browser generate responses to requests from servers, so you end up with API requests being carried in HTTP responses and API responses being carried in subsequent HTTP requests. But if we hold our noses for long enough to get over that, it's possible to build something that isn't too offensive... I think.
We've some sketches of how this might work with our current API. We hope to have more fully developed proposals to share before we meet.
Agenda+: Attaching API calls to HTTP exchanges
One of the key items we identified as a likely essential extension to a core attribution API was the ability to have the API invoked as a side effect of ordinary HTTP requests. That's how the business operates today with its pixels and whatnot.
Things get a little gross when you want to have the browser generate responses to requests from servers, so you end up with API requests being carried in HTTP responses and API responses being carried in subsequent HTTP requests. But if we hold our noses for long enough to get over that, it's possible to build something that isn't too offensive... I think.
We've some sketches of how this might work with our current API. We hope to have more fully developed proposals to share before we meet.
Time
20-30 minutes.
Links
The text was updated successfully, but these errors were encountered: