Type of issue

enhancement

Description

While updating the ORTB native docs, generated a list of proposed changes/enhancements:

1. Validate Asset IDs

ORTB requires asset IDs, but this is mainly for linking response assets to the request assets. At one point we discussed having PBJS fill in missing asset IDs, but this has been considered problematic. Instead, PBJs should validate the asset ID:

If the asset ID doesn't exist or the assetID is negative, console log an error and remove this adunit from the auction.

2. Remove the sendTargetingKeys flag

This is the old option that tells Prebid to send all the hb_native KVPs to the adserver. That shouldn't happen anymore now that we have better ways to transmit the asset data at render time.

Proposal:

1. if both sendTargetingKeys and ortb are specified in adunit.mediatypes.native, it's a major error. (do we cancel the whole auction or just the adunit when there's an error like this?)
2. when ortb is specified, treat sendTargetingKeys as false.

3. Error if Native "types" are specified

'Type' is a sort of 'macro' introduced in an early version of PBJS that expands to a set of assets. This is Prebid-only behavior meant to be friendly, but doesn't fit well with the ORTB approach. A “type” is like a macro that defines a group of assets. The only value supported is ‘image’, which implies the following assets: image, title, sponsoredBy, clickUrl, body, icon, and cta. The first 4 are required attributes.

Proposal:
if both 'types' and 'ortb' are specified in adunit.mediatypes.native, console log an error and remove this adunit from the auction.

Heads up @muuki88 , @patmmccann , @dgirardi