LogoLogo
  • 🦩Overview
  • 💾Datasets
    • Overview
    • Core Concepts
      • Columns & Annotations
      • Type & Property Mappings
      • Relationships
    • Basic Datasets
      • dbt Integration
      • Sigma Integration
      • Looker Integration
    • SaaS Datasets
    • CSV Datasets
    • Streaming Datasets
    • Entity Resolution
    • AI Columns
      • AI Prompts Recipe Book
    • Enrichment Columns
      • Quick Start
      • HTTP Request Enrichments
    • Computed Columns
    • Version Control
  • 📫Syncs
    • Overview
    • Triggering & Scheduling
    • Retry Handling
    • Live Syncs
    • Audience Syncs
    • Observability
      • Current Sync Run Overview
      • Sync History
      • Sync Tracking
      • API Inspector
      • Sync Alerts
      • Observability Lake
      • Datadog Integration
      • Warehouse Writeback
      • Sync Lifecycle Webhooks
      • Sync Dry Runs
    • Structuring Data
      • Liquid Templates
      • Event Syncs
      • Arrays and Nested Objects
  • 👥Audience Hub
    • Overview
    • Creating Segments
      • Segment Priorities
      • Warehouse-Managed Audiences
    • Experiments and Analysis
      • Audience Match Rates
    • Activating Segments
    • Calculated Columns
    • Data Preparation
      • Profile Explorer
      • Exclusion Lists
  • 🧮Data Sources
    • Overview
    • Available Sources
      • Amazon Athena
      • Amazon Redshift
      • Amazon S3
      • Azure Synapse
      • ClickHouse
      • Confluent Cloud
      • Databricks
      • Elasticsearch
      • Kafka
      • Google AlloyDB
      • Google BigQuery
      • Google Cloud SQL for PostgreSQL
      • Google Pub/Sub
      • Google Sheets
      • Greenplum
      • HTTP Request
      • HubSpot
      • Materialize
      • Microsoft Fabric
      • MotherDuck
      • MySQL
      • PostgreSQL
      • Rockset
      • Salesforce
      • SingleStore
      • Snowflake
      • SQL Server
      • Trino
  • 🛫Destinations
    • Overview
    • Available Destinations
      • Accredible
      • ActiveCampaign
      • Adobe Target
      • Aha
      • Airship
      • Airtable
      • Algolia
      • Amazon Ads DSP (AMC)
      • Amazon DynamoDB
      • Amazon EventBridge
      • Amazon Pinpoint
      • Amazon Redshift
      • Amazon S3
      • Amplitude
      • Anaplan
      • Antavo
      • Appcues
      • Apollo
      • Asana
      • AskNicely
      • Attentive
      • Attio
      • Autopilot Journeys
      • Azure Blob Storage
      • Box
      • Bloomreach
      • Blackhawk
      • Braze
      • Brevo (formerly Sendinblue)
      • Campaign Monitor
      • Canny
      • Channable
      • Chargebee
      • Chargify
      • ChartMogul
      • ChatGPT Retrieval Plugin
      • Chattermill
      • ChurnZero
      • CJ Affiliate
      • CleverTap
      • ClickUp
      • Constant Contact
      • Courier
      • Criteo
      • Crowd.dev
      • Customer.io
      • Databricks
      • Delighted
      • Discord
      • Drift
      • Drip
      • Eagle Eye
      • Emarsys
      • Enterpret
      • Elasticsearch
      • Facebook Ads
      • Facebook Product Catalog
      • Freshdesk
      • Freshsales
      • Front
      • FullStory
      • Gainsight
      • GitHub
      • GitLab
      • Gladly
      • Google Ads
        • Customer Match Lists (Audiences)
        • Offline Conversions
      • Google AlloyDB
      • Google Analytics 4
      • Google BigQuery
      • Google Campaign Manager 360
      • Google Cloud Storage
      • Google Datastore
      • Google Display & Video 360
      • Google Drive
      • Google Search Ads 360
      • Google Sheets
      • Heap.io
      • Help Scout
      • HTTP Request
      • HubSpot
      • Impact
      • Insider
      • Insightly
      • Intercom
      • Iterable
      • Jira
      • Kafka
      • Kevel
      • Klaviyo
      • Kustomer
      • Labelbox
      • LaunchDarkly
      • LinkedIn
      • LiveIntent
      • Loops
      • Mailchimp
      • Mailchimp Transactional (Mandrill)
      • Mailgun
      • Marketo
      • Meilisearch
      • Microsoft Advertising
      • Microsoft Dynamics
      • Microsoft SQL Server
      • Microsoft Teams
      • Mixpanel
      • MoEngage
      • Mongo DB
      • mParticle
      • MySQL
      • NetSuite
      • Notion
      • OneSignal
      • Optimizely
      • Oracle Database
      • Oracle Eloqua
      • Oracle Fusion
      • Oracle Responsys
      • Orbit
      • Ortto
      • Outreach
      • Pardot
      • Partnerstack
      • Pendo
      • Pinterest
      • Pipedrive
      • Planhat
      • PostgreSQL
      • PostHog
      • Postscript
      • Productboard
      • Qualtrics
      • Radar
      • Reddit Ads
      • Rokt
      • RollWorks
      • Sailthru
      • Salesforce
      • Salesforce Commerce Cloud
      • Salesforce Marketing Cloud
      • Salesloft
      • Segment
      • SendGrid
      • Sense
      • SFTP
      • Shopify
      • Singular
      • Slack
      • Snapchat
      • Snowflake
      • Split
      • Sprig
      • Statsig
      • Stripe
      • The Trade Desk
      • TikTok
      • Totango
      • Userflow
      • Userpilot
      • Vero Cloud
      • Vitally
      • Webhooks
      • Webflow
      • X Ads (formerly Twitter Ads)
      • Yahoo Ads (DSP)
      • Zendesk
      • Zoho CRM
      • Zuora
    • Custom & Partner Destinations
  • 📎Misc
    • Credits
    • Census Embedded
    • Data Storage
      • Census Store
        • Query Census Store from Snowflake
        • Query Census Store locally using DuckDB
      • General Object Storage
      • Bring Your Own Bucket
        • Bring your own S3 Bucket
        • Bring your own GCS Bucket
        • Bring your own Azure Bucket
    • Developers
      • GitLink
      • Dataset API
      • Custom Destination API
      • Management API
    • Security & Privacy
      • Login & SSO Settings
      • Workspaces
      • Role-based Access Controls
      • Network Access Controls
      • SIEM Log Forwarding
      • Secure Storage of Customer Credentials
      • Digital Markets Act (DMA) Consent for Ad Platforms
    • Health and Usage Reporting
      • Workspace Homepage
      • Product Usage Dashboard
      • Observability Toolkit
      • Alerts
    • FAQs
Powered by GitBook
On this page
  • Getting Started
  • Supported Objects and Sync Behaviors
  • Conversion Events
  • DSP Audiences
  • Digital Markets Act (DMA)
  • Need help connecting to Amazon Ads DSP?

Was this helpful?

  1. Destinations
  2. Available Destinations

Amazon Ads DSP (AMC)

This page describes how to use Census with Amazon Ads DSP.

PreviousAlgoliaNextAmazon DynamoDB

Last updated 2 months ago

Was this helpful?

Amazon Ads DSP is a demand-side platform that allows advertisers to programmatically buy display, video, and audio ads. Census can sync your customer data to Amazon Ads DSP to help you create and manage audiences for your ad campaigns.

Getting Started

Connecting to your Amazon Ads account is straightforward.

  1. From the page, click New Destination and select Amazon Ads from the menu.

  2. You'll first need to specify your desired Region by providing one of the following values:

    • North America: www.amazon.com

    • European Union: eu.account.amazon.com

    • Asian Pacific: apac.account.amazon.com

  3. Complete the OAuth flow. Make sure your are signed into a user account that has permissions to both view all of your accounts, as well as submit data to them (read only accounts will not work).

  4. Select the Ads account you wish to use with Census. If you'd like to sync to multiple accounts, you will need to add each as its own destination.

Supported Objects and Sync Behaviors

Object Name

Supported?

Sync Keys

Behaviors

Conversion Event

✅

Event Unique ID

Send

Hashed Records

✅

ID

Update or Create

DSP Audience

✅

ID

Update or Create

Learn more about all of our sync behaviors in our documentation.

Conversion Events

Before you can sync conversion events, you need to first define them within the Amazon DSP Ui.

  • Within Campaign Manager, select your desired Advertiser, then Events manager, then Conversions tab, and click Next under Conversion API.

  • Once you've created your conversion, you'll need to copy the Conversion Definition ID to provide to Census.

Other than the Conversion Definition ID, you'll need a few more fields:

  • Like other event syncs, Amazon requires an Event Name and a Timestamp.

  • Match Key - This is the user identifier of the user that triggered the event. Census currently only supports Email as a match key but will support additional options in the future. If you are going to provide Census with a pre-hashed value, it must follow this format:

    • Lowercase

    • Remove all non-alphanumeric characters [a-zA-Z0-9] and [.@-]

    • Remove any leading or trailing whitespace

    • Then apply SHA-256

There are also several optional fields available.

  • Data Processing Options - Currently, the only accepted value is LIMITED_DATA_USE which will cause Amazon to ignore this event. Typically, you can leave this field unmapped.

  • Units Sold - This only applies to Off Amazon Purchase conversion definition type and represents the number of items purchased. If not provided on the conversion event, a default of 1 will be applied.

  • Value - This has two modes depending on the conversion definition type.

    • For Off Amazon Purchase, this represents a monetary value. Must be a minimum of 0 and must not exceed 2 decimal points. If not provided, the static value provided on the conversion definition will be used.

    • For any other type, this represents a non-monetary value based on a scale of your choosing. Can be negative and must not exceed 2 decimal points. If not provided, the static value provided on the conversion definition will be used.

Census will send the Sync Key you specify as the unique identifier for your event sync to Amazon using the Client Dedupe Id property which allows Amazon to avoid capturing the same conversion event multiple times. In case of multiple events containing the same value, only the first will be kept.

DSP Audiences

Advanced Configuration

Description

Data Source Country

List of countries where user data in audience was collected for DMA support

Amazon DSP Audiences are a pecular object in that they are actually two separate objects that are linked together through the use of a unique ID. Amazon DSP Audiences need to be managed in two phases:

  1. First upload the PII about your audience members, where each record is identified by a unique ID you've assigned them. This is the Hashed Records (Part 1) object.

  2. Wait for Amazon to process the data. Amazon's guidance is that this process can take up to 48hrs.

  3. Then "assign" those records to an audience. This is the DSP Audience Members (Part 2) object.

This means using Amazon DSP Audiences requires at least two separate Census syncs. The first sync will upload the PII about your audience members and the second sync will assign those records to an audience. If you plan to create multiple audiences, we recommend that your Hashed Records sync uploads all of the records you plan to use in any of your audiences. Then you can create a separate DSP Audience Members sync for each audience you want to create.

Digital Markets Act (DMA)

Need help connecting to Amazon Ads DSP?

if you want Census to support more Amazon Ads objects and/or behaviors.

Conversion Events are an Event Syncs though they have some unique terminology and requirements. Visit for more details.

Country Code - Must be the two-letter country code described in .

Currency Code - This only applies to Off Amazon Purchase conversion definition type. This is the three letter currency code associated with the value of the event in . If not provided, the currency setting on the conversion definition will be used.

Like Conversion Events, you can optionally provide pre-hashed values for your records. Amazon documents the requirements for this . They are nearly identical to the requirements for Conversion Events, though notice that country and state identifiers are lower case if provided.

Finally, to support upcoming Digital Markets Act (DMA) requirements, Amazon now accepts a Data Source Country field on the DSP Audience Members object. This field should be a comma separated list of two-letter country code using format. This list will be used by any segments created from this sync. This is required in order to create a new audience.

You can send our at support@getcensus.com or start a conversation from the in-app chat.

🛫
Destinations
Syncs
Contact us
their documentation
ISO 3166-1 alpha-2
ISO-4217 format
here
ISO 3166-1 alpha-2
support team an email