CDP Integration Directory

Exports audience definitions and member lists from Treasure Data to Adform DMP as files in an Adform-owned S3 bucket, adding users to audiences or removing them.

Receives Adjust mobile app events such as installs, sessions, clicks and custom events in Treasure Data through postback callbacks added in Adjust's partner setup.

Loads Adobe Analytics data feed hit files and lookup files from an Amazon S3 bucket into Treasure Data, picking up new feeds incrementally by report suite.

Imports gzip files that Adobe Analytics places on Adobe's SFTP server into Treasure Data tables, using version 1 of a connector that also has a cloud storage version.

Publishes user segments built in Treasure Data to Adobe Audience Manager, with setup details available from Treasure Data's support team.

Loads the Treasure Data JavaScript SDK through an Adobe Launch rule with custom code on page load, so Launch manages Treasure Data tags, triggers and captured data elements.

Adds Treasure Data's Tracking Pixel extension to Adobe Launch so rules fire a pixel that records user actions in a chosen Treasure Data database and table.

Uploads customer profile attributes from Treasure Data to Adobe Target through its bulk profile update API, creating missing profiles with the default v2 API.

Brings AdRoll impressions, clicks and conversions into Treasure Data by having AdRoll SQL load a Postgres or Redshift warehouse that Treasure Data's database connectors read.

Creates CRM, custom and other audience types and uploads audience data from Treasure Data to NextRoll, with an API key from a NextRoll developer app and a personal access token from AdRoll.

Writes Treasure Data query results to Airship as static audience lists, text, number, date or JSON attributes, and custom events, with lists overwritten rather than appended.

Imports Airship reports, named users, static lists and channels into Treasure Data, with incremental loading and parallel threads for downloading large channel lists.

Creates audiences on Amazon Marketing Cloud and Amazon DSP and adds hashed customer records to them from Treasure Data queries or Audience Studio activations over OAuth.

Sends conversion events such as purchases, sign-ups and leads from Treasure Data to the Amazon Ads Conversion API for Amazon DSP and Sponsored Ads attribution.

Sends hashed emails, cookie IDs and mobile ad IDs from Treasure Data segments to Amazon DSP as a data provider, adding users to external audiences or removing them.

Runs reports that are already set up in Amazon Ads and imports their contents into Treasure Data tables, from the console or the TD Toolbelt.

Uploads pseudonymized audience datasets from Treasure Data to Amazon Marketing Cloud through an S3 bucket, hashing PII with SHA-256, and can delete identities from datasets.

Imports enrichment data from an Amazon Marketing Cloud instance into Treasure Data tables after Amazon Ads API onboarding and an OAuth sign-in.

Lets Spark jobs on Amazon EMR read Treasure Data tables as DataFrames in Scala or PySpark through Treasure Data's td-spark driver, with no TD query needed.

Streams records from an Amazon Kinesis stream into Treasure Data through an AWS Lambda function, using a sample handler script from Treasure Boxes.

Writes Treasure Data job results to tables in an existing Amazon Redshift cluster over JDBC, with no support for timestamp or date columns, which you must first convert to strings or Unix time.

Imports a table from Amazon Redshift into Treasure Data with an optional WHERE condition, and can load only rows added since the last scheduled run.

Runs federated Trino queries from Treasure Data against Amazon Redshift tables through a Live Connect zero-copy source, once enabled, keeping results seven days unless saved.

Writes Treasure Data job results to an Amazon S3 bucket as CSV or TSV files of up to 100 GB per query, with optional AES-256 server-side encryption.

Exports Treasure Data query results to Amazon S3 through a separate v2 connector that adds quote policy settings and session or Assume Role authentication.

Imports CSV files from an Amazon S3 bucket into Treasure Data and can save each source file's name in an extra column of the imported records.

Imports JSON, TSV and CSV files from an Amazon S3 bucket into Treasure Data with the original S3 connector, which accepts basic, anonymous or session credentials.

Loads JSON, TSV and CSV files from S3 buckets into Treasure Data with version 2 of the S3 connector, whose key difference from v1 is support for Assume Role authentication.

Generates Parquet files from Treasure Data job results and uploads them to Amazon S3 in multipart uploads, with row groups of up to 512 MB.

Imports Parquet files stored in Amazon S3 buckets into Treasure Data tables, connecting with basic, session or Assume Role credentials.

Creates Amplitude events or Identify updates from Treasure Data query results using a project API key, with operations such as set, add, append and unset.

Imports the data Amplitude collects into Treasure Data with a project's API and secret keys, loading everything at first and only newly added files on later runs.

Captures AppsFlyer mobile attribution events in Treasure Data through postback URLs set up in AppsFlyer's Push API with a Treasure Data write key.

Imports Apptopia data source objects, such as product usage and product sales data, into Treasure Data with a client ID and secret and adjustable API rate limits.

Sends user lists that target Treasure Data segments to DAC's AudienceOne with an API key, for use in AudienceOne advertising campaigns.

Writes Treasure Data job results as files to a Microsoft Azure Blob Storage container, with optional gzip or bzip2 compression.

Imports CSV and TSV files from an Azure Blob Storage container into Treasure Data with an account key or SAS token, matching files by path prefix or regex.

Turns Treasure Data job results into Parquet files and uploads them to Azure Data Lake Storage with a hierarchical namespace, signing in with an access key or SAS token.

Imports Parquet files from Azure Data Lake Storage (v2) into Treasure Data, either copying all existing files for a migration or ingesting new data directly.

Streams events published to Azure Event Grid topics into Treasure Data in near real time through a webhook secured with rotatable security identifiers and a write-only key.

Sends Treasure Data query results to Batch through its REST API, either updating profiles with native and custom attributes and events or filling Batch audiences.

Imports Batch profile attributes, events or reachability data into Treasure Data using a Batch REST API key plus a project key, optionally filtered to one segment.

Sets up Composable Audience Studio on BigQuery with a GCP service account key and a zero-copy catalog, so Treasure Data segments are built on BigQuery data without copying it.

Writes Treasure Data job results into a BigQuery table that matches a predefined schema, in append, replace, replace backup or delete mode, with server-to-server API authentication.

Uploads large Treasure Data result sets to BigQuery as Parquet files through BigQuery load jobs, with append, replace, replace backup or truncate modes and JSON key or WIF sign-in.

Imports BigQuery tables or query results into Treasure Data with the original BigQuery connector, whose connections can also serve exports unless they use OAuth.

Imports BigQuery tables or query results into Treasure Data with version 2 of the connector, which signs in with a service account JSON key or Workload Identity Federation, not OAuth.

Queries BigQuery tables in place from Treasure Data's Trino engine as Live Connect zero-copy federated queries, with no ETL, after the feature is enabled for the account.