HTTP API for Measure Conversion #280
Conversation
api.bs
Outdated
| <div class=example id=ex-measure-conversion-header> | ||
| This is the HTTP equivalent of <a href=#ex-measure-conversion>the JavaScript `measureConversion` example</a>: | ||
| <xmp highlight=http> | ||
| Measure-Conversion: aggregation-service="https://aggregator.example/tee", histogram-size=20, epsilon=1.0, lookback-days=14, impression-sites=("publisher.example" "other.example"), impression-callers=("ad-tech.example"), match-values=(2), credit=(0.25 0.25 0.5), value=3, max-value=7 |
There was a problem hiding this comment.
The value of aggregation-service is not something that can be looked up through this API. That makes this far less reliable than the JS API, which at least can adapt.
Another thing that needs to be noted clearly is that this doesn't let you have multiple Measure-Conversion fields. If there are multiple conversions, then maybe a redirect chain will allow those to be logged.
There was a problem hiding this comment.
The value of
aggregation-serviceis not something that can be looked up through this API. That makes this far less reliable than the JS API, which at least can adapt.
If we thought it important, we could advertise the set of aggregation services in a Client-Hints-like request header.
Another thing that needs to be noted clearly is that this doesn't let you have multiple
Measure-Conversionfields. If there are multiple conversions, then maybe a redirect chain will allow those to be logged.
True, though that caveat also applies to the existing Save-Impression header. We have an example use case for recording multiple impressions simultaneously in #222.
apasel422
force-pushed
the
conv-http
branch
from
41307b2 to
c8a91ed
Compare
|
Discussed in the Oct 14 call - let's wait to merge until we have support for sending the report. |
3 participants
Preliminary work for #31; still need to specify when this header is processed (#189) and how the report destination is configured.
Preview | Diff