csharrison / aggregate-reporting-api

Aggregate Reporting API
41 stars 10 forks source link

About Brand and Ad Safety #7

Open nchrys opened 4 years ago

nchrys commented 4 years ago

Hello,

Brand Safety is paramount in advertising. Even running campaigns for performance, you don't want to hurt your overall brand. This is true on the publisher and on the advertiser side and both are very sensitive to it:

Advertisers and/or Publishers want to have strict control over it and be able to audit it. Approximation is not an option in this case since a few instances can damage your brand. Aggregated reporting would only work if there is enough identical reports. This seems to be a clear flaw in the reporting capabilities.

What could be done to ensure Brand Safety in the framework of this proposal?

michaelkleber commented 4 years ago

Hi Nicolas: Can you explain how this API fits into your Brand Safety story? From both the publisher and advertiser points of view, I would expect brand safety questions to be of great importance before rendering an ad, which isn't this API's domain at all.

nchrys commented 4 years ago

Hi Michael,

Thank you for your response.

Hi Nicolas: Can you explain how this API fits into your Brand Safety story? From both the publisher and advertiser points of view, I would expect brand safety questions to be of great importance before rendering an ad, which isn't this API's domain at all.

The Brand Safety story is two-fold. The central piece is indeed at bidding/rendering time. However, reporting is key for auditing purposes. How can you be sure that your brand was kept safe at rendering time if you don't have access to the right reporting? The question I raised was related to this second point.

For the Brand/Ad Safety use case, the reporting requirement would be the following: