What is the Audience Manager Container ID and where to find it?
This article discusses how to find a container ID when a container other than the default (0) is needed for an Audience Manager implementation, regardless of an AppMeasurement + Visitor.js or AEP Web SDK implementation. This article will help you understand what a Container ID is and where to find it.
Description description
Environment
Audience Manager with either an AppMeasurement + Visitor.js or AEP Web SDK implementation
Issue/Symptoms
When a container ID other than the default (0) is needed for an AAM implementation via AppMesurement + Visitor.js or with the AEP Web SDK, how does one know what container ID to use? Is it the container ID in the AAM UI?
Resolution resolution
When an AAM implementation needs to use a different container ID instead of the standard/default container (0), then the value to put into ID service (Visitor.js) or in the AEP datastream config is the container number based on when the container was created, NOT the container ID in the AAM UI. To get the proper value, take the following steps:
- Log in to Audience Manager, and click Tools, then Tags. (If you don’t see the Tools or Tags menu items, reach out to an AAM Administrator of the organization to complete these steps)
- When the Tags page loads, click on the container in question.
- In the right rail, locate the Container Code box.
- Locate the akamai.net or cdn.demdex.net request. The number in the path just after the tenant ID is the numeric value to use in the code. Do not use the container ID. In the example/screenshot below, the value to use is 1.
Note: The code in the Container Code box is not code that you should place on any web properties. It’s here only for the sake of getting the Container ID value needed for the idSyncContainerID configuration of ID Service (Visitor.js) or the Third Party Id Sync Container ID field in a datastream configuration when anything other than the default ID sync container is needed. If you aren’t an AAM customer or you’ve never needed the container ID field before now, then you’ll likely just leave these values as 0.
It’s also important to note that this same Container ID is used for id syncing with RT-CDP destinations that still support 3rd Party cookie syncs. If there has never been an Audience Manager Implementation, then this value for RT-CDP destinations will always be 0. Additionally, the vast majority of Audience Manager implementations only ever had a default Container ID of 0. Only rarely did an Audience Manager implementations have more than one Container ID. If in doubt, start with the default of 0 (or just leave these fields blank).