Delivering Customer Match Audiences to Google DV360 via the API

This guide shows you how to build an unattended integration that uploads an audience to Narrative and delivers it into a Customer Match audience in one Google Display & Video 360 (DV360) account. You can create a new audience or add to one that already exists. Before you start, complete the prerequisites and set up API access. You need the ID of an enabled DV360 profile.

1. Create the dataset

The dataset must carry at least one identifier column that Google DV360 can match on. Required columns lists them.

curl -X POST https://api.narrative.io/datasets \
  -H "Authorization: Bearer $NIO_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "loyalty_members_dv360",
    "display_name": "Loyalty Members (DV360)",
    "description": "Audience for DV360 Customer Match",
    "write_mode": "append",
    "schema": {
      "file_config": { "type": "json", "normalize_field_names": false },
      "type": "object",
      "properties": {
        "sha256_hashed_email": {
          "type": "object",
          "properties": { "value": { "type": "string" } }
        }
      }
    }
  }'
# → {"id": 12345, "company_id": <COMPANY_ID>, "display_name": "Loyalty Members (DV360)",
#    "status": "pending", ...}

Record the id in the response.

Required columns

Both interfaces take the same schema. The dataset needs at least one of these identifier columns:

Column	Shape of each value
`sha256_hashed_email`	`{"value": ...}`
`hashed_email`	`{"value": ..., "type": "..."}`
`unique_id`	`{"value": ..., "type": "..."}`
`raw_email`	A string
`e164_phone_number`	A string
`telephone_number`	A string
`narrative_id`	`{"context": "...", "value": ...}`
`person_name`, `iso_3166_1_country`, and `postal_address`, together	`person_name` is `{"given_name": "...", "family_name": "..."}`, `iso_3166_1_country` is a string, and `postal_address` is `{"postal_code": "..."}`

Each identifier column is named after its Rosetta Stone attribute, and the connector matches on that column name. A column holds either a plain string or an object. In the dataset schema, declare a string column with "type": "string", and declare an object column with "type": "object" and its properties:

{
  "type": "object",
  "properties": {
    "<string_attribute>": { "type": "string" },
    "<object_attribute>": {
      "type": "object",
      "properties": { "<property>": { "type": "<type>" } }
    }
  }
}

Send an object column as an object in each row:

{"<string_attribute>": "...", "<object_attribute>": {"<property>": "..."}}

See your connector’s reference page for the attributes it accepts and their exact shapes. A row with one identifier looks like this:

{"sha256_hashed_email": {"value": "<SHA-256 of the trimmed, lowercased email>"}}

See Supported identifiers for how the destination matches each identifier.

2. Activate the dataset

curl -X POST https://api.narrative.io/datasets/{dataset_id}/activate \
  -H "Authorization: Bearer $NIO_API_TOKEN"

The response is 201 with the dataset, now "status": "active". Activation locks the schema, so activate only once the shape is settled.

3. Upload and ingest your file

Each line of the file is one row that matches the schema you declared in step 1. For the columns DV360 accepts and their shapes, see Supported identifiers and Required columns. You can load a file into a dataset over the API in two ways:

Signed-URL upload. Your integration uploads one file of up to 3 GB, then asks Narrative to ingest it.
Managed S3 bucket. You write files to an S3 bucket that Narrative manages, and Narrative ingests each batch on its own. Use a managed bucket for files larger than 3 GB, or for files that another system delivers on a schedule.

Choose a file format

The dataset’s file_config.type sets the format of every file you load into it. Parquet and JSON Lines both hold object columns, which nest properties inside one column:

Parquet (parquet) is the most compatible format for connector datasets. It stores nested struct columns and their types natively, and Narrative matches columns to the schema by name at every level.
JSON Lines (json) holds one JSON object per line. Narrative matches each nested object to the schema by name.

CSV datasets (flat) hold only scalar columns, so they can’t carry object columns.

Upload a file with a signed URL

Request an upload URL, then send the file straight to storage:

curl -X POST https://api.narrative.io/uploads/my-file.jsonl \
  -H "Authorization: Bearer $NIO_API_TOKEN"
# → {"path": "<UPLOAD_PATH>", "url": "https://...", "expiry": "..."}

curl -X PUT "<url from the response>" --upload-file ./my-file.jsonl

The upload URL is valid for 30 minutes and carries its own signature, so send no authorization header with the PUT.

Keep the path from the response. Narrative assigns its own storage path, which does not match the name you requested, and the ingest request needs Narrative’s path rather than yours.

Then ingest the file into the dataset, passing that path as source_file:

curl -X POST https://api.narrative.io/datasets/{dataset_id}/upload \
  -H "Authorization: Bearer $NIO_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"source_file": "<UPLOAD_PATH>"}'

Ingestion runs in the background. Watch the record count on the dataset to know when it has finished:

curl -s https://api.narrative.io/datasets/{dataset_id} \
  -H "Authorization: Bearer $NIO_API_TOKEN"
# → .stats.active_dataset_stored_records

The count moves from zero to your row count, typically within a couple of minutes. Each ingested file adds a new snapshot to the dataset, and every active connection on the dataset delivers that snapshot.

Write files to a managed S3 bucket

A managed bucket is an S3 bucket that Narrative creates for your company. You write each batch of files into its own folder under the dataset’s path in the bucket, then write an empty _NIO_COMMIT file into that batch folder. Narrative ingests every file in the batch folder when the commit file appears, so you make no upload or ingest request. A file can be as large as S3 accepts. See Ingesting Files from a Managed S3 Bucket to create the bucket, grant your AWS account access, and lay out the folders.

4. Confirm DV360 accepts the dataset

Before you create a connection, ask Narrative which connector interfaces the dataset satisfies:

curl -s https://api.narrative.io/datasets/{dataset_id}/interfaces \
  -H "Authorization: Bearer $NIO_API_TOKEN"
# → {"dataset_id": 12345,
#    "accepted": [{"app_id": <APP_ID>, "interface_id": "<INTERFACE_ID>"}, ...],
#    "errors": [{"app_id": <APP_ID>, "interface_id": "<INTERFACE_ID>", "details": {...}}, ...]}

The response checks the dataset’s schema against every interface of the connectors your company has installed, and sorts the results into two lists:

accepted lists each interface you can connect the dataset to, by the connector’s app_id and the interface_id.
errors lists each interface the schema does not satisfy. Its details hold the reason, such as "required property '<column>' not found".

Add ?tags=<tag> to check only the interfaces that carry that tag. When the interface you want is under errors, the dataset’s schema doesn’t meet what the interface needs, for example a missing column or property. Activation locks the schema, so create a new dataset that fixes what the error names. For Google DV360, look for the Google DV360 Connector ("app_id": 15) in accepted. Add ?tags=google-dv360-cmu to check only the Google DV360 interfaces.

{"app_id": 15, "interface_id": "audience_first_party_new"},
{"app_id": 15, "interface_id": "audience_first_party_existing"}

audience_first_party_new creates a new Customer Match audience, and audience_first_party_existing adds to one you already have.

5. Deliver to a new audience

Create a connection. The connector creates the Customer Match audience in the profile’s DV360 advertiser before it answers, so the audience exists in DV360 once you get 201.

curl -X POST https://api.narrative.io/v2/connections \
  -H "Authorization: Bearer $NIO_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "connections_dataset",
    "dataset_id": 12345,
    "profile_id": "<PROFILE_ID>",
    "quick_settings": {
      "type": "audience_first_party_new",
      "name": "Loyalty Members",
      "description": "Active loyalty program members",
      "membership_duration_days": 30,
      "historical_data_enabled": true
    }
  }'
# → 201 {"type": "connections_dataset", "id": "<CONNECTION_ID>",
#        "app": {"id": 15, "name": "Google Display & Video 360 (Customer Match) Connector"},
#        "dataset_id": 12345, "installation_id": <INSTALLATION_ID>,
#        "quick_settings": {"type": "audience_first_party_new", "name": "Loyalty Members",
#                           "description": "Active loyalty program members",
#                           "membership_duration_days": 30, "historical_data_enabled": true},
#        "profile_id": "<PROFILE_ID>", "profile": {"id": "<PROFILE_ID>", "name": "Example Brand DV360"},
#        "status": "active", ...}

Both type fields are required. The outer one identifies what you are connecting, and the one inside quick_settings selects the delivery interface. What the connection does describes every field, its allowed values, and its default. Record the connection id. You need it to stop the delivery.

6. Confirm the connection

curl -s https://api.narrative.io/v2/connections/{connection_id} \
  -H "Authorization: Bearer $NIO_API_TOKEN"
# → {"type": "connections_dataset", "id": "<CONNECTION_ID>", ..., "status": "active"}

To list every connection on a dataset, or every DV360 connection in your company:

curl -s "https://api.narrative.io/v2/connections?dataset_id=12345" \
  -H "Authorization: Bearer $NIO_API_TOKEN"

curl -s "https://api.narrative.io/v2/connections?app_id=15" \
  -H "Authorization: Bearer $NIO_API_TOKEN"
# → {"records": [{"type": "connections_dataset", "id": "<CONNECTION_ID>", ...}]}

In DV360, the audience appears in the linked account under the name you gave it. Its ID is shown with it. You use that ID in the next step.

7. Deliver to an existing audience

To send another dataset into a Customer Match audience in the profile’s DV360 advertiser, connect with the audience’s numeric ID from DV360. The example uses 12346, an example ID for an existing dataset. Create and load that dataset with steps 1 to 4 before you connect it:

curl -X POST https://api.narrative.io/v2/connections \
  -H "Authorization: Bearer $NIO_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "connections_dataset",
    "dataset_id": 12346,
    "profile_id": "<PROFILE_ID>",
    "quick_settings": {
      "type": "audience_first_party_existing",
      "user_list_id": <USER_LIST_ID>,
      "historical_data_enabled": true
    }
  }'
# → 201 {"type": "connections_dataset", "id": "<CONNECTION_ID>",
#        "app": {"id": 15, "name": "Google Display & Video 360 (Customer Match) Connector"},
#        "dataset_id": 12346, "installation_id": <INSTALLATION_ID>,
#        "quick_settings": {"type": "audience_first_party_existing",
#                           "user_list_id": <USER_LIST_ID>, "historical_data_enabled": true},
#        "profile_id": "<PROFILE_ID>", "profile": {"id": "<PROFILE_ID>", "name": "Example Brand DV360"},
#        "status": "active", ...}

user_list_id is a number. The connector looks the audience up in the profile’s DV360 advertiser before it accepts the connection. The audience keeps the membership duration it was created with.

Keeping the audience current

Write new rows to the dataset with the same upload calls from step 3. The connection keeps running, so the new rows reach the same DV360 audience without another connection. A member stays in the audience for the audience’s membership duration after the last delivery that included them, so re-upload each member you want to keep at least once within that period. To hear when each delivery finishes, subscribe to delivery notifications.

Stopping delivery

curl -X DELETE https://api.narrative.io/v2/connections/{connection_id} \
  -H "Authorization: Bearer $NIO_API_TOKEN"
# → 200 {}

Deleting the connection stops further deliveries. After that, GET /v2/connections/{connection_id} returns 404. The audience stays in DV360 with the members it already has. To delete the dataset when you no longer need it:

curl -X DELETE https://api.narrative.io/datasets/{dataset_id} \
  -H "Authorization: Bearer $NIO_API_TOKEN"

Getting help

Contact your Narrative relationship manager with your company ID, the dataset ID, the connection ID, and the request and response you have a question about.

Google DV360 Connector API

Prerequisites, API access, profiles, and delivery notifications

Google DV360 Connector

Supported identifiers for DV360

Connector Interfaces

Why a dataset connects to an interface rather than a connector

API Keys

Create and rotate keys for programmatic access

Overview

Platform

Data Ingestion

Data Planes

Querying with NQL

Data Collaboration

Identity Resolution

Data Activation

Audience Studio

Connectors

Connector APIs

Compliance

Rosetta Stone

Account Settings

Workflows

Webhooks

Data Collaboration MCP Server

Tools

SDKs

Delivering Customer Match Audiences to Google DV360 via the API

1. Create the dataset

Required columns

2. Activate the dataset

3. Upload and ingest your file

Choose a file format

Upload a file with a signed URL

Write files to a managed S3 bucket

4. Confirm DV360 accepts the dataset

5. Deliver to a new audience

6. Confirm the connection

7. Deliver to an existing audience

Keeping the audience current

Stopping delivery

Getting help

Google DV360 Connector API

Google DV360 Connector

Connector Interfaces

API Keys

​1. Create the dataset

​Required columns

​2. Activate the dataset

​3. Upload and ingest your file

​Choose a file format

​Upload a file with a signed URL

​Write files to a managed S3 bucket

​4. Confirm DV360 accepts the dataset

​5. Deliver to a new audience

​6. Confirm the connection

​7. Deliver to an existing audience

​Keeping the audience current

​Stopping delivery

​Getting help

​Related content

Google DV360 Connector API

Google DV360 Connector

Connector Interfaces

API Keys

1. Create the dataset

Required columns

2. Activate the dataset

3. Upload and ingest your file

Choose a file format

Upload a file with a signed URL

Write files to a managed S3 bucket

4. Confirm DV360 accepts the dataset

5. Deliver to a new audience

6. Confirm the connection

7. Deliver to an existing audience

Keeping the audience current

Stopping delivery

Getting help

Related content