Placement ID methodology in Data Library
Overview
The ad_performance
report combines (1) ad-level data from DSPs on which customer serves media, and (2) placement-level data from CM360 using a join on cm_placement_id
and date
.
This guide walks through where Placement ID comes from and how it is parsed from the respective DSPs.
Methodology by platform
The following SQL examples are for Redshift.
To see the BigQuery version, (1) replace the function regexp_substr
with regexp_extract
, and (2) add an r
before the opening quotation mark in the 2nd argument, e.g.: regexp_substr(arg1, 'arg2')
→ regexp_extract(arg1, r'arg2')
Platform | PID Source (in order of priority) | Example SQL |
---|---|---|
Amazon DSP | Creative Name |
SQL
|
Bidtellect | Creative Name |
SQL
|
DV360 | CM360 Placement ID |
SQL
|
DV360 Trueview (Youtube) | Trueview Ad Group Name |
SQL
|
Google Ads | Ad Group Name |
SQL
|
Ad Name |
SQL
| |
Ad Tracking URL Template |
SQL
| |
Microsoft Bing | Ad Group Name |
SQL
|
The Trade Desk | Ad Server Creative Placement ID |
SQL
|
Vistar DSP | Creative Name |
SQL
|
Yahoo DSP | Creative Custom ID |
SQL
|
Creative Name |
SQL
|