Data Collaboration Platform (DCP) - Add connections

At a glance: Set up DCP connections to connect your data sources, enrich your data, and export audiences to cloud storage and media partners.

About DCP connections

Connections determine how DCP ingests your data and exports your audiences. After setting up your cloud services, connect them to DCP using the Manage connections modal. The following connection types are available:

DCP supports different cloud services for different connection directions. Use the table below to see which services you can use for each connection type:

Cloud service Source (inbound) Cloud storage export (outbound)
Amazon S3
Google Cloud Storage (GCS)
BigQuery -
Snowflake -
Salesforce Cloud/CRM -

For Amazon S3 and Google Cloud Storage, a single connection serves as both a source (inbound) and a cloud storage export (outbound) destination. Creating a source connection to S3 or GCS automatically creates a matching cloud storage (export) connection, and vice versa. 

Create source connections

Create source connections to bring first-party data into DCP.

To create a source connection:

  1. In AppsFlyer, go to Collaborate > Data Clean Room.
  2. Click Manage connections in the top-right corner.
  3. Go to the Source tab and click + New connection.
    2026-07-27_13-30-46.png
  4. Continue with the Cloud service connections for source data instructions below.

You can also create a source connection directly when setting up a source. See Create and manage sources for instructions.

Note

Creating an incoming Source connection to Amazon S3 or GCS automatically creates a matching outgoing Cloud storage connection (and vice versa). Deleting Amazon S3 or GCS connection also automatically deletes the other. Since it's really one underlying connection, removing it from either tab removes it everywhere it's used.

Cloud service connections for source data

Source connections are for connecting your data sources securely to DCP. From the New connection dialog, select your cloud service and complete the details for your provider:

BigQuery: In the New connection dialog, enter the BigQuery project ID for the project that contains your source data. You can find this on the BigQuery page of your Google Cloud Console.

Snowflake: In the New connection dialog, enter the Snowflake account ID and region for the account that contains your source data. To find this, click the account name at the bottom-left of your Snowflake console:

ACCOUNTADMIN > Account > hover over the relevant account > Copy account identifier. See the Snowflake documentation for details.

Important!

Look for the ID labeled Locator. This is not the same ID used to create outbound Snowflake connections.

Amazon S3 and GCS: In the New connection dialog, enter the name of the bucket you created for the exclusive use of the AppsFlyer Data Clean Room (DCR).

Salesforce Cloud/CRM: See how to set up a Salesforce connection.

Local file connection

Local file system connections let you upload data files directly from your computer into DCP. This option is typically used for testing only and isn't recommended for ongoing or large-scale data ingestion.

Set up a local file connection

A local file connection is used to test the platform using a sample file. It lets you get familiar with DCP functionality before starting to share data. Keep in mind that it isn't recommended for sharing data, has a data retention limit of 14 days, and doesn't support automation processes.

A local file connection can be set up during source creation.

Create cloud storage connections

Cloud storage connections let you automatically export your DCP audiences to your Amazon S3 or Google Cloud Storage (GCS) bucket after each audience update.

To create a cloud storage connection:

  1. In AppsFlyer, go to Collaborate > Data Clean Room.
  2. Click Manage connections in the top-right corner.
  3. Go to the Cloud storage tab and click + New connection.
    2026-07-27_13-30-34.png
  4. The New cloud storage connection modal opens. 
  5. In the New cloud storage connection modal, select your cloud provider: Google Cloud Storage or Amazon Simple Storage.
  6. Enter your bucket name:
    • GCS: Enter the GCS bucket name in the format gs://my-bucket.
    • S3: Enter the S3 bucket name. 

  7. Click Test connection to verify that DCP can connect to your bucket. 

  8. Click Save. The new connection appears under Your cloud storage connections in the Cloud storage tab.

You can also create a cloud storage connection directly from the audience builder. See Build and activate audiences for instructions.

Understand the export path

Each time an audience is exported, DCP writes it to your bucket using a fixed, predictable path:

<bucket>/dcp-output/audiences/<collaboration-id>/t=<audience_name>_<id>/dt=<YYYY-MM-DD>/v=<version>/<file>.csv

Example folder contents for one delivery:

s3://af-dcr-example-bucket/dcp-output/audiences/8f3a1c02-44b1-4e9a-9c7d-2b6e1a0f5d3e/t=example_audience_6148a3/dt=2026-07-18/v=1/
  ├── part-00000-a1b2c3d4-e5f6-47a8-9b0c-1d2e3f4a5b6c-c000.csv
  ├── part-00001-a1b2c3d4-e5f6-47a8-9b0c-1d2e3f4a5b6c-c000.csv
  └── _SUCCESS
Path segment What it means
<bucket> Your connected S3 or GCS bucket.
dcp-output/audiences/ Fixed folder that DCP creates automatically for all audience exports.
<collaboration-id> The unique ID of the collaboration this audience belongs to. You can find it in the collaboration's URL in DCP.
t=<audience_name>_<id> The audience name (spaces and special characters replaced with underscores), plus a unique ID. This ensures a deleted-and-recreated audience with the same name never overwrites or collides with older files.
dt=<YYYY-MM-DD> The delivery date.
v=<version> A version number for this audience's exports. It increases with each new delivery.
part-NNNNN-<job-id>-c000.csv One of the output files for this delivery — see File format and splitting below.
_SUCCESS An empty marker file written once the export finishes writing all part files.

Note

This folder structure is created and managed automatically. Don't rename or restructure it manually — any automated process reading these files should be built to follow this path pattern, and should wait for _SUCCESS to appear before processing the part files, to avoid reading a partial delivery.

File format and splitting

  • Audiences are always exported as CSV files, uncompressed, with two columns: value (the identifier) and taxonomy (the identifier type).
  • Larger audiences may be delivered as multiple files rather than a single file, numbered part-00000, part-00001, and so on. By default, each file contains up to approximately 500,000 rows.
  • A single file can contain a mix of identifier types in the same rows — filter using the taxonomy column for the identifiers you need. Common taxonomy values include customer_id, mobile_ad_id, hashed_email, and hashed_phone_number_without_plus_sha256.

Example:

value,taxonomy
6f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c,customer_id
1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d,mobile_ad_id
b7e2c9a1f4d6e8b0a2c4d6e8f0a1b3c5d7e9f1a3b5c7d9e0f2a4b6c8d0e2f4a6,hashed_email
c1d3e5f7a9b1c3d5e7f9a1b3c5d7e9f1a3b5c7d9e1f3a5b7c9d1e3f5a7b9c1d3,hashed_phone_number_without_plus_sha256

Create media partner connections

Outbound media partner connections let you securely connect your DCP audiences to supported media partners, so you can activate tailored campaigns on their platforms. Media partners are the main destination for audience activation. Learn how to set up specific media partner connections.

To create a media partner connection:

  1. In AppsFlyer, go to Collaborate > Data Clean Room.
  2. Click Manage connections in the top-right corner.
  3. Go to the Media partners tab and click + New connection. If you already have existing connections, you'll see them listed under Media partners.
  4. From the New media partner connection dialog, select the relevant media partner.
  5. Enter a connection name.
  6. Log in to the media partner account with your credentials and follow their instructions to enable AppsFlyer access.
  7. Click Select account ID and select the relevant account for this connection.
  8. Click Save. The new connection is added to the list of partners.

You can also create a media partner connection directly from the audience builder. See Build and activate audiences for instructions.

Create Data & Identity connections

Data & Identity connections unify fragmented user data to improve match rates with activation partners. This enables larger partner-side audiences and more impact from your campaigns.

ID5

Enrich your first-party data with ID5 identifiers to unify fragmented user data, improve match rates with activation partners, and increase partner-side audience size.