Hi all,

We are in the middle of our live testing with the PAAPI.

Unlike display advertising, native advertising has several parts: title, description, image URL, and sometimes also a call to action.

Publishers who utilize native advertising want to block ads based on matching text patterns. For example, publisher A does not want to show ads with the string ‘foo' in the title.

These rules use different matching text patterns within the title, description, and the image URL.

The number of blocking rules is very large. On average, one publisher can have hundreds of blocking rules, defined at the site level or for all of the sites that they manage in the native advertising platform.

We are seeking guidance on a potential implementation that takes into account situations where the native advertising platform is using 3rd party sellers in addition to being a buyer and a seller (code on page as the SSP, and DSP from its direct demand)

We thought of the following options:

Option A - per auction blocking:

• Taking all of the publisher blocking rules from the floor price auction (context)
• Build it into the ‘auctionConfig’
• Pass it to the scoreAd
• Reduce the desirability value

Pro: everything is done by the client (more privacy, I guess)
Cons: Possible latency, difficulties when using component auctions

B - Blocking using Trusted Server:

• By using the domain/publisher ID (context) - use the real-time call in directFromSellerSignals during the scoreAd process
• Match blocking rules in the Sellet trusted server, adhering to the TEE requirements
• Once we meet at least one blocking rule is met, reduce/use the desirability / allowComponentAuction values
• Report it either via reportResult() or by using the Private Reporting API

Pro: less latency/load
Con: We can update the publishers rules in the TE environment per TEE requirements only (not in real time)

Can you please advise on the above flows? Can you offer alternatives/tips for this native advertising use case?

Thank you!