Re: [w3ctag/design-reviews] Event-Level Click Conversion Measurement API (#418)

Hi,

Thanks for additional clarifications! Will have a look. 

So

> This requirement is based around the fact that sophisticated ads ranking is done via complex machine learning, where individual inferences need to be annotated with labels. Without the 64 bits to identify which ad / click converted, we don’t get the labelling.

Is "we" here a royal "we" or any particular "we"? ;)

More to the point, I still don't get why 64b is exactly needed. I don't want to be overly picky (despite I maybe am a bit), but while I understand your reply to 2.2, I don't get it where those 64b come from.

In the meantime a bit more architectural question/comments/remarks/angle. Basically what I wonder is the overlap factor with another existing spec (also implemented already I think) that intends to deal with similar functionality, specifically Ad Click Attribution that defines the following:

_<a adCampaignId="[6-bit ad campaign id]" adDestination="[ad click destination URL]">_

In Conversion Measurement API defines:

_<a addestination=”[eTLD+1]” impressiondata=”[string]” impressionexpiry=[unsigned long long] reportingdomain=”[eTLD+1]”>_

Of course we may end up with sites using the following in practice:

_<a addestination=”[eTLD+1]” adCampaignId="[6-bit ad campaign id]" impressiondata=”[string]” impressionexpiry=[unsigned long long] reportingdomain=”[eTLD+1]”>_

...with some implementations selectively ignoring parts of the attributes. Though here I must thank you for clearly defining what _adDestination_ is (which is apparently not the case with [ad click attribution](https://wicg.github.io/ad-click-attribution/index.html); yes I realise that based on spec text explains that _adDestination_ in both specs translates to same thing).

But I wonder if you could not discuss/agree on any convergence in particular. Because at the moment it seems we're exploring two different specs that deal with indeed pretty similar tasks. I am not sure if this kind of enrichment makes web platform a better place.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/418#issuecomment-550035815