Below, you will find an overview of where the AdServer-Placement-ID (also known as Mercury UUID) must be entered so that Mercury can recognize the data from the various technical systems and assign it to your campaigns accordingly.
Note: The automated and daily import of data into Mercury requires that the technical systems listed below are set up as data pipelines.
When storing the ID, it does not matter where this is done in the name or in the field. It also doesn't matter whether you insert it with or without some kind of separator. In this way, any name taxonomies can usually be retained and the ID can be placed flexibly.
Examples:
- GCM as PlacementExternal ID
= mrc-PpNbqxt2vHH - LinkedIn within the CreativeName
= "Motiv1_mrc-PpNbqxt2vHH" or "Motiv1mrc-PpNbqxt2vHH" or "mrc-PpNbqxt2vHH-Motiv1" or similar - Facebook within the AdName
= "Text_mrc-PpNbqxt2vHH" or "Text_mrc-PpNbqxt2vHH-Text" or similar
Please insert the AdServer-placement-ID as follows:
| System | Option 1 | Option 2 |
| Adform Adserver/DSP | in the field AdGapId | - |
| GCM | in the field PlacementExternalId | - |
| Flashtalking | in the field ThirdPartyPlacementId | - |
| in the AdName | in the Campaign AdLabels | |
| Google Ads | in the Campaign Labels | - |
| DV360 | in the LineItemIntegrationCode | in the InsertionOrderIntegrationCode |
| in the CreativeName | - | |
| Outbrain | in the CampaignName | - |
| in the AdName | - | |
| Snapchat | in the AdName | - |
| TikTok | in the AdName | - |
| in the AdName | - |