Custom Identifiers
Managing custom identifiers
Last updated
Managing custom identifiers
Last updated
Custom identifiers enable you to load alternative identifier types into your DCN that aren't natively supported when using the tabular data schema to format your files and tables.
Examples of such IDs are Publisher Provided IDs (PPIDs), DMP specific IDs or other types of internal ID types that you want to use when building query audiences for audience sync & real time targeting via the Opable SDKs.
There are twenty custom identifiers that you can point specific ID types to, they are represented by the IDs c to c19 which you will reference as headers when loading data into your DCN.
You can also assign each custom ID a "display name" which you can use to identify which custom ID is for which purpose. For example, if you have a PPID that you want to load into your DCN, you can use the custom ID c with the display name My PPID
In addition to setting the name of a custom identifier, you can also set the scope to indicate if it's either Person or Household level identifier.
For example, to load a custom PPID into your DCN, you would then associate your PPID to the custom ID you chose, for example c by formatting your file or Snowflake table based on the tabular data schema with the header id_c in column one.
| id_c |
|---|
your custom PPID |
Once this data is loaded, your custom PPIDs will then be available in your DCN for use in real time targeting and audience syncing.
