The beta environment is for testing your Audience Manager implementation. Changes made in beta do not affect production data. Contact your Audience Manager Partner Solutions representative if you’re interested in using the beta environment.
The functionality in the bveta environment is an exact replica of the production environment, without any experimental or unreleased features. Your login credentials from the production environment are valid in the beta environment.
Update Schedule
The beta environment is updated at the end of each month during off-peak hours.
Note that your customer data (signals, traits, and segments) is not synced between the production and beta environments.
The beta environment supports inbound traffic only for file name and content syntax validation purposes. Since there is no ID mapping taking place on the beta environment, customers will not see any segment populations.
Consequently, the Onboarding Status page will always report No matching AAM ID upon file ingestion on the beta environment.
We advise all customers to perform any inbound testing on their production environment.
Outbound traffic is not enabled for the beta environment.
Service | URL/Hostname | How to obtain access |
---|---|---|
S3 | Contact your Audience Manager Partner Solutions representative or Customer Care | Contact your Audience Manager Partner Solutions representative or Customer Care to set up an Amazon S3 bucket for your beta instance. Read about the advantages of using Amazon S3. |
DCS | https://dcs-beta.demdex.net/... |
See Accessing the DCS in the Beta Environment. |
UI | https://bank-beta.demdex.com |
Your production environment credentials are valid for the beta environment. |
API | https://api-beta.demdex.com/... |
Your production environment credentials are valid for the beta environment. We recommend that you create a generic API user, see details. |
Make a DCS call, using the curl command. Curl is a tool to transfer data from or to a server, using one of many supported protocols.
For example:
curl -v https://dcs-beta.demdex.net/event
Verify that your request was served by the beta DCS by looking for “sandbox” in the DCS response header.
For example:
curl -v http://dcs-beta.demdex.net/?event
[...]
< DCS: va6-sandbox-dcs-3.sandbox.demdex.com <release_number>
[...]