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
This is an idea for one way that cross-publisher measurement could potentially be done.
We could consider the introduction of an additional API, measureConversionWithDelegation() which would accept all the same arguments as measureConversion() except for aggregator and histogramSize. This function would return an object that could be explicitly delegated to ad-tech scripts corresponding to all the channels where the advertiser purchased ads.
let delegation_object = measureConversionWithDelegation(
epsilon: 1,
logic: "last-touch",
value: 3,
maxValue: 5,
lookbackDays: 30,
filterData: 2,
intermediarySites: ["ad-tech-1.example", "ad-tech-2.example"],
);
// iframe from "ad-tech-1.example"
let report1 = delegation_object.measureConversion(
aggregator: "aggregator-1.example",
histogramSize: 3,
);
// report1 would be a histogram contribution 3 wide
// iframe from "ad-tech-2.example"
let report2 = delegation_object.measureConversion(
aggregator: "aggregator-2.example",
histogramSize: 5,
);
// report2 would be a histogram contribution 5 wide
The idea is that measureConversionWithDelegation would attempt to attribute the conversion to an impression from one of multiple ad-tech vendors. At most one ad-tech's ads would receive attribution. Only the ad-tech who received attribution (if any) would receive a non-zero histogram contribution from their call to measureConversion.
This would be an improvement over the de-facto approach to delegation as it would only involve a single deduction from the privacy budget, not multiple. Furthermore, it would avoid double-counting as any given conversion could not be attributed to multiple ad-tech vendors.
This would ease the coordination challenge described in #34 as each ad-tech would be able to independently select their own histogramSize and the values they set for histogramIndex would not need to be coordinated.
This would also allow each ad-tech to select a different aggregation service.
Each of these per-ad-tech histogram results could be combined into a unified user-interface by the advertiser, who would then have a unified view of results broken down by ad-tech, then by campaign or whatever they wanted to use the histogram bins to represent.
The text was updated successfully, but these errors were encountered:
This is an idea for one way that cross-publisher measurement could potentially be done.
We could consider the introduction of an additional API,
measureConversionWithDelegation()
which would accept all the same arguments asmeasureConversion()
except foraggregator
andhistogramSize
. This function would return an object that could be explicitly delegated to ad-tech scripts corresponding to all the channels where the advertiser purchased ads.The idea is that
measureConversionWithDelegation
would attempt to attribute the conversion to an impression from one of multiple ad-tech vendors. At most one ad-tech's ads would receive attribution. Only the ad-tech who received attribution (if any) would receive a non-zero histogram contribution from their call tomeasureConversion
.This would be an improvement over the de-facto approach to delegation as it would only involve a single deduction from the privacy budget, not multiple. Furthermore, it would avoid double-counting as any given conversion could not be attributed to multiple ad-tech vendors.
This would ease the coordination challenge described in #34 as each ad-tech would be able to independently select their own
histogramSize
and the values they set forhistogramIndex
would not need to be coordinated.This would also allow each ad-tech to select a different aggregation service.
Each of these per-ad-tech histogram results could be combined into a unified user-interface by the advertiser, who would then have a unified view of results broken down by ad-tech, then by campaign or whatever they wanted to use the histogram bins to represent.
The text was updated successfully, but these errors were encountered: