4 ms·

It sounds like you're referring to the sell-side of advertising (i.e. a publisher running ads on their site). I'm referring to the buy-side of advertising (i.e

It sounds like you're referring to the sell-side of advertising (i.e. a publisher running ads on their site). I'm referring to the buy-side of advertising (i.e. an ecomm business running a marketing campaign). Each task could be "Tell Google that person 123 visited landing page X." or "Tell Facebook that person 456 purchased a tshirt." This lets you create targeting segments on the platforms and measure the results of your campaigns.

dillondoyle 6y ago
i think we just have different views of the current ad tech ecosystem. you can already tell google/fb/dsp/ssp directly no need for zapier - they already have pixels. now fb (and more are building) have server to server. puttin zapier in the middle especially for individual pageviews/impressions would be inconceivably ginormous scale for sure it's super complicated with the changes google is forcing and a ton is up in the air. but assuming google's vision of the future comes true this type of data exchange will likely be blocked in whole or minimally as we know it now from what i understand, in that future the browser holds the 'interest groups' e.g. targetable user data we're talking about for remarketing, interest cohorts etc - i think that's floc + turtledove in action in thinking from sell side example publisher.com would create a (i think k-anonymous?) interest group in browser. it looks like google might go so far as to kill something like TTD universal id by enforcing a privacy budget. so there goes that idea of a middle man syncing publisher.com login pii identifier -> ssp/dsp google's write up says bidding happens in the browser via 'worklet' but i think that can be delegated to a DSP if done to their likeing as a 'trusted 3rd party server' which also gets rid of all these identifiers including IPs/UAs (google will obviously control the market lol). so i guess that could be some product but zapier moving into but totally completely different than now

dillondoyle 6y ago

i think we just have different views of the current ad tech ecosystem. you can already tell google/fb/dsp/ssp directly no need for zapier - they already have pixels. now fb (and more are building) have server to server. puttin zapier in the middle especially for individual pageviews/impressions would be inconceivably ginormous scale for sure it's super complicated with the changes google is forcing and a ton is up in the air. but assuming google's vision of the future comes true this type of data exchange will likely be blocked in whole or minimally as we know it now from what i understand, in that future the browser holds the 'interest groups' e.g. targetable user data we're talking about for remarketing, interest cohorts etc - i think that's floc + turtledove in action in thinking from sell side example publisher.com would create a (i think k-anonymous?) interest group in browser. it looks like google might go so far as to kill something like TTD universal id by enforcing a privacy budget. so there goes that idea of a middle man syncing publisher.com login pii identifier -> ssp/dsp google's write up says bidding happens in the browser via 'worklet' but i think that can be delegated to a DSP if done to their likeing as a 'trusted 3rd party server' which also gets rid of all these identifiers including IPs/UAs (google will obviously control the market lol). so i guess that could be some product but zapier moving into but totally completely different than now