Post View Conversions

Further Consideration

This is very much a POC demo that shows we can accomplish, within some reliability tolerance, getting conversion signals that are immediate, event level, and deterministic, using the APIs as they exist between now and >= Q3 2025.

However, there are lots of interesting edge cases not completely accounted for in the code here. Here is a list of them along with bamboo man solutions.

• What to do with multiple AuctionTargets: we have this problem today, if anything this could make it easier as we'll have all the data "packaged up" for an attribution algorithm to resolve.
• What to do about multiple conversion triggers: what if multiple conversion triggers show up, either b/c the clean up operation fails or because of something unforseen? I think this can be handled with additional metadata on the ConversionTrigger object, such as date_time, which can then be used inside an attribution algorithm.
• Leftover AuctionTriggers: once an auction trigger has converted, do we try to remove it? Since we won't know the names of each AuctionTrigger we cannot easily just call leaveAdInterestGroup. We could clear all the IGs for conversions but that would impact other Targetable pixels; we could use the pixelID as subdomain idea for leaving the IGs, as of now I don't think we can leave all the IGs joined everywhere, just on the current page (verify). (The pixelID as subdomain also seems likely to proliferate and get us to the IG ower per browser limit).
• On a positive note it's worth considering how we can use this local storage to our advantage. For instance, it is conceivable we can keep a "list" of activity that gets sent in with the AuctionTriggers for attribution.