Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Key Value Analytics report shows you the information associated with your network's defined targeting keys and values.
Impressions with key/value targeting will serve and be reported only for those impressions that were logged by a placement tag containing the kw_ prefix on the key name. For example, a placement tag containing keyname=value1 will not serve and therefore not be logged, whereas a placement tag containing kw_keyname=value1 will serve and be logged. This applies to GET-based query-string ad calls with the following tag types: /tt, /ttj, /fpt, /jpt, /pt, /ptv, /ssptv, /mtj, /map, /mob, /prebid/amp, /vmap, /ssvmap.
Note
AppNexus Seller Tags
When using Seller Tag, omit the kw_ prefix. AST has the keyword object in the body of the (ut/v3) request, so the prefix is not needed. The same holds true for other POST-based request body ad calls from Prebid (ut/v3/prebid, openrtb2/prebid, prebid/lfv) and OpenRTB (openrtb2).
Not all impressions from key/value targets will be included in reports. To be included, the targets must meet the following criteria:
- Key must be pre-defined. For more information, see the Pre-Defining Targeting Keys and Values page in the UI.
- Value must be pre-defined OR Value must be targeted by at least one line item or campaign.
- Value is not a numeric range (greater than or less than).
- Value does not include a wildcard.