Treasure AI (formerly Treasure Data) integrations

SFTP (export v1). Sends Treasure Data workflow job results as CSV or TSV files to an SFTP server with the original SFTP export, signing in with a password or key pair.

SFTP (export v2). Uploads Treasure Data job results to an SFTP server with the SFTP_V2 connector, which supports multiple file formats, compression and server handshake algorithms.

SFTP (import). Imports files stored on an SFTP server into Treasure Data with the SFTP_V2 connector, signing in with a password or an RSA, DSS, ECDSA or Ed25519 key.

SFTP (Parquet import). Imports Parquet files stored on an SFTP server into Treasure Data, with no support for other file formats.

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

Azure Blob Storage (import). 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.

PostgreSQL (export). Writes Treasure Data job results to tables in an existing PostgreSQL instance, connecting without mutual TLS, which only the import supports.

PostgreSQL (import). Imports data from a PostgreSQL database, such as one on RDS, into Treasure Data with password or mutual TLS client certificate authentication.

MySQL (export). Writes Treasure Data job results to tables on an existing MySQL instance, which needs to grant Treasure Data the privileges to create, change and drop tables.

MySQL (import). Imports a MySQL table into Treasure Data with optional SSL settings, loading only data added since the last run when the transfer repeats.

Kafka (Fluentd consumer). Sends JSON messages from Kafka topics into Treasure Data through the Fluentd consumer for Kafka and a write-only API key, a setup the page describes as beta.

Kafka (HTTP Sink Connector). Pushes records from Kafka topics on Confluent Cloud, Confluent Platform or Apache Kafka into Treasure Data in near real time through an HTTP Sink Connector calling the Ingestion API.

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

Microsoft SQL Server (export). Writes Treasure Data job results to Microsoft SQL Server tables, including Azure instances, in insert, truncate-insert, replace or merge mode.

Microsoft SQL Server (import). Imports Microsoft SQL Server tables or custom SELECT query results into Treasure Data, appending or replacing data, with incremental loading by chosen columns.

MongoDB (export). Writes Treasure Data job results into collections on an existing MongoDB instance or MongoDB cloud cluster, for uses such as top-N lists and metrics dashboards.

MongoDB (import). Imports documents from a MongoDB server or MongoDB cloud cluster into Treasure Data as a one-time or recurring transfer.

Google Drive (export). Exports Treasure Data job results as files to a Google Drive folder over an OAuth2 connection, so the data can be shared and analyzed further in Drive.

Google Drive (import). Imports CSV or TSV files, or gzip copies of them, from Google Drive into Treasure Data over OAuth2, loading only new or modified files on scheduled runs.

Elasticsearch. Writes Treasure Data job results as documents into an index on an Elastic Cloud instance, connecting with basic authentication, including Elastic Security, on port 9200 by default.

Azure Data Lake Storage (Parquet export). 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.

Azure Data Lake Storage (Parquet import). 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.

Box (export). Exports Treasure Data job results as files to a Box folder connected over OAuth, with optional compression and public-key encryption before upload.

Box (import). Imports CSV or TSV files from a Box file or folder into Treasure Data over OAuth, once or on a recurring schedule, with an optional file name prefix filter.

FTP (export). Sends Treasure Data job results as CSV or TSV files to an FTP server over FTPS or FTPES, with optional gzip, bzip2 or PGP encoding.

FTP (import). Imports files from an FTP or FTPS server into Treasure Data over a passive-mode connection, with incremental loading for repeated transfers.

Teradata (export). Exports Treasure Data job results to a Teradata server over JDBC, converting data types that the two systems share.

Teradata (import). Imports Teradata tables, views or SQL query results into Treasure Data over JDBC, with incremental loading by increasing unique columns such as IDs or timestamps.

Dropbox. Exports Treasure Data job results as files to a Dropbox account connected over OAuth2, with optional gzip or bzip2 compression or PGP encryption.

MariaDB. Imports MariaDB tables into Treasure Data from the command line, using a guess step to detect the format and a schedule for repeat imports.

Informatica. Pulls Treasure Data table records into a target of choice through an Informatica Cloud data synchronization task over the Treasure Data JDBC driver, which the page marks deprecated.

OneDrive. Sends Treasure Data job results as files to a OneDrive account over OAuth2, with direct user sign-in or admin pre-approval depending on the Microsoft tenant.

OneDrive (import). Imports files from OneDrive personal or business accounts and SharePoint documents into Treasure Data over OAuth2, loading only files modified since the last run.

Amazon EMR. 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.

Azure Event Grid. 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.

Delta Sharing. Imports tables shared through a Delta Sharing server into Treasure Data using its API endpoint and a bearer token, in a connector the page labels beta.

Logstash. Sends data collected by Logstash to Treasure Data through the Treasure Data output plugin for Logstash, which buffers up to five minutes of data in memory.

Pentaho. Connects Pentaho Data Integration (Kettle) to Treasure Data through the Treasure Data JDBC driver, which the page calls deprecated, so Pentaho jobs can process large data volumes.

Riak CS. Imports CSV and TSV files from a Riak CS bucket into Treasure Data, once or on a schedule.

Criteo. Adds users to Criteo audience segments or removes them through the Criteo Marketing API from Treasure Data job results, matching on email, mobile ad ID, GUM or identityLink IDs.

Pinterest (audiences). Adds users to Pinterest audiences or removes them from Treasure Data job results, creating missing audiences and sending SHA-256 hashed identifiers.

Pinterest (Conversions API). Sends web, in-app and offline conversion events, with user and custom attributes, from Treasure Data to the Pinterest Conversions API for optimization and reporting.

The Trade Desk (CRM data). Uploads customer lists such as emails and phone numbers from Treasure Data to The Trade Desk's CRM Data API to build segments, using a CRM data token and advertiser ID.

The Trade Desk (DMP segments). Syncs The Trade Desk IDs into a Treasure Data table through a cookie-syncing tag, then sends segments keyed on those IDs to The Trade Desk DMP for DSP targeting, without PII.

The Trade Desk (import). Imports The Trade Desk advertisers, campaigns, data groups and tracking tags into Treasure Data, with a retry limit for each API call.

LiveRamp (activation partners). Sends Treasure Data segments to LiveRamp and triggers activations with six LiveRamp partners, such as Beeswax, Twitter and Snapchat, through the LiveRamp API.

LiveRamp (SFTP export). Publishes Treasure Data user segments, including PII that LiveRamp anonymizes, to its SFTP server as gzip CSV files for DSPs, DMPs and data providers, with cookie syncing via LiveRamp's pixel tag.

X Ads. Writes Treasure Data job results to Twitter Custom Audiences for targeting, exclusion and lookalike expansion, uploading one identifier type such as emails over OAuth.

Amazon Ads (audiences). 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.

Amazon Ads (Conversions API). 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.

Amazon Ads (DSP Data Provider). 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.

Amazon Ads (Marketing Cloud export). 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.

Amazon Ads (DSP reports). 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.

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

Reddit. Adds users to Reddit Ads custom audiences or removes them from Treasure Data query results, once you acknowledge Reddit's rule that shared data be traceable and deletable.

Google Display & Video 360 (cookie and mobile ID audiences). Moves cookies and mobile ad IDs from Treasure Data into new or existing Display & Video 360 audience lists, adding or removing them, once Google grants Treasure Data access.

Google Display & Video 360 (Customer Match audiences). Creates customer-match audiences in Google Display & Video 360 from first-party data such as emails, phone numbers and mobile device IDs in Treasure Data, and updates their members over OAuth.

Meta Conversions API (export). Sends conversion events such as purchases and registrations from Treasure Data job results to Facebook through the Conversions API, including in-store offline events and web server logs.

Meta Conversions API (dataset quality import). Imports Meta Conversions API quality metrics, such as event match quality, event coverage, deduplication and additional conversions reported, for website or offline datasets into Treasure Data.

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

Branch. Forwards Branch mobile events such as clicks, opens, installs and purchases to Treasure Data in real time through Branch webhooks posting to the Treasure Data Ingest API.

Adjust. 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.

Rokt. Uploads custom audience lists and conversion events such as purchases and sign-ups from Treasure Data to Rokt as files over SFTP, with credentials from a Rokt account manager.

Google Ad Manager (audience export). Moves cookies and mobile ad IDs from Treasure Data into new or existing Google Ad Manager audience segments through the Audience Partner API, adding or removing users.

Google Ad Manager (Data Transfer reports import). Imports Data Transfer report files of event-level ad server log data from Google Cloud Storage into Treasure Data with a pre-built connector, once Google enables the transfers.

Google Ad Manager (DFP objects import). Imports Google Ad Manager (DFP) companies, creatives, ad units, line items, orders, placements and saved report queries into Treasure Data through a Google service account.

AdRoll (audience export). 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.

AdRoll (AdRoll SQL import). 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.

Google Campaign Manager 360. Uploads or updates conversions for Floodlight activities in Google Campaign Manager 360 from Treasure Data through the CM360 API, with email, phone or address identifiers for enhanced conversions.

Singular. Forwards in-app and custom events tracked by Singular (formerly Apsalar) into Treasure Data through a postback template that Apsalar Support sets up on request, with the fields you choose.

Taboola. Creates Taboola first-party audiences from device IDs or emails and adds users to them or removes them from Treasure Data through the Taboola Backstage API over OAuth.

Yahoo. Syncs Treasure Data segments and user or audience attributes to Yahoo through the DataX and Partner Match APIs, adding or removing users in Yahoo segments for ad targeting.

Instagram (custom audiences). Writes Treasure Data job results to Instagram Custom Audiences following Facebook's specifications, normalizing values such as emails before they are matched.

Kochava. Receives Kochava mobile install campaign events in Treasure Data through a Kochava certified postback to Treasure Data's endpoint, set up in the Kochava UI.

Adform. 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.

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

Google Customer Match. Uploads emails or phone numbers from Treasure Data to Customer Match in Google Ads or Display & Video 360 over OAuth, with Google limiting new Customer Match API users from April 2026.

Google Marketing Platform. Imports the status of Audience Partner API uploads from the Google Marketing Platform (formerly DoubleClick Data Platform) SFTP server into Treasure Data, using SFTP credentials Google provides.

MediaMath. Adds Treasure Data users to MediaMath segments, removes them or updates segments from the data, through files on MediaMath's SFTP server, as a data provider or with your own credentials.

Yahoo! JAPAN Ads. Creates audience lists on Yahoo! JAPAN Ads and uploads first-party emails, IDFAs or AAIDs from Treasure Data user segments into them as files.

Yahoo! JAPAN Ads (Audience Discovery). Uploads user emails, IDFAs or AAIDs with up to 79 extra attributes from Treasure Data to Yahoo! JAPAN Audience Discovery as TSV files, for display ad segments.

Yahoo! JAPAN Ads (Conversions API). Writes conversion events from Treasure Data job results to Yahoo!'s Ads Conversion API v2, which authenticates with a tracking tag access token rather than an application ID.

Intimate Merger. Connects Treasure Data with Intimate Merger's DMP so data held in Treasure Data can drive digital marketing campaigns, with details available on request.

Yelp. Sends offline conversion events such as purchases and leads from Treasure Data to the Yelp Conversions API for Yelp Ads measurement, hashing user identifiers with SHA-256.

Dynalyst. Exports Treasure Data query results to Dynalyst as files in the AWS S3 storage Dynalyst uses, much like an S3 export, with results of up to 100 GB.

Dynalyst (import). Imports JSON, TSV and CSV files from the AWS S3 bucket Dynalyst uses into Treasure Data, picking files by path prefix or regular expression.

Google Data Manager. Sends audience members such as Google account emails, phone numbers or mobile IDs from Treasure Data to Google Ads and Display & Video 360 in one call, adding or removing them.

Google Data Manager (conversions). Uploads offline, online or store sales conversions from Treasure Data to Google Ads through the Google Data Manager API, matched on hashed user identifiers.

CyberAgent Ameba. Sends user lists keyed by td_global_id from Treasure Data segments to CyberAgent's Ameba ads for infeed and video ad targeting, arranged through a Treasure Data sales rep.

Equativ. Exports segment taxonomy and user profile CSV files from Treasure Data to Google Cloud Storage buckets that Equativ provides and ingests automatically, using the GCS Export V2 connector.

F.O.X. Receives raw data events from CyberZ's F.O.X in Treasure Data, an integration whose setup details come from Treasure Data support.

Kakao Moment. Registers or edits customer files of Android and Apple advertising IDs in a Kakao Moment ad account from Treasure Data query results over OAuth.

Supership. Sends user lists that target Treasure Data segments to Supership's DSP with an API key from Supership, for use in its ad campaigns.

Klaviyo (export). Adds Treasure Data profiles to Klaviyo lists or removes them and records email or SMS marketing consent with a private API key, through a connector listed as beta.

Klaviyo (import). Imports Klaviyo metrics, events, profiles and list members into Treasure Data with a private API key, using only Klaviyo's stable API.

Airship (export). 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.

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

Oracle Eloqua (export). Adds contacts to Oracle Eloqua contact and shared lists, accounts to account groups, and records to custom data objects from Treasure Data job results.

Oracle Eloqua (import). Imports Oracle Eloqua contacts, with the fields you choose, and activity data into Treasure Data for a set time window.

Oracle Responsys. Publishes Treasure Data user segments to Oracle Cross Channel Orchestration (Responsys) for personalized email campaigns, typically through the SFTP server export.

Dotdigital (export). Sends Treasure Data job results to Dotdigital as triggered transactional emails, bulk contact uploads to address books, or unified contact uploads and deletions.

Dotdigital (import). Imports Dotdigital campaigns, address book contacts and unsubscribes since a chosen date into Treasure Data through a Dotdigital API account.

Pardot (export). Upserts prospects, optionally in parallel, and adds list memberships in Salesforce Pardot from Treasure Data job results, within Pardot's API call limits.

Pardot (import). Imports Pardot campaigns, forms, lists, prospects, visitors, visitor activities and other objects into Treasure Data, using Pardot's Export API for large data sets.

Customer.io. Pushes Treasure Data query results into Customer.io through its Tracking API to create, update or remove people and to add them to segments or take them out.

Sailthru. Sends users from Treasure Data segments to Sailthru lists and keeps them in sync, and updates Sailthru user profiles for personalized email campaigns.

CleverTap. Syncs user profiles, events and audience lists from Treasure Data to CleverTap with an account ID and passcode, for CleverTap segmentation and campaigns.

Batch (export). 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.

Batch (import). 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.

Selligent. Loads Treasure Data rows into a Selligent master list, then assigns them to one or more static segments chosen by a routing column, using a Selligent API key and secret.

Crescendo Lab. Exports Treasure Data query results to Crescendo Lab's MAAC as members or segments of a LINE official account, keyed by LINE UID, email or mobile number.

Crescendo Lab (MAAC import). Imports Crescendo Lab MAAC members and segments into Treasure Data with a MAAC API token, loading only new records on later runs when incremental loading is on.

EmberPoint MailPublisher. Uploads email delivery lists from Treasure Data segments to EmberPoint MailPublisher Smart and can book a send from a saved draft, encoding files in Shift_JIS for Japan.

EmberPoint MailPublisher (import). Imports EmberPoint MailPublisher Smart reports, such as uploaded list statuses, delivered email statuses and click counts, into Treasure Data through an API-enabled account.

SAP Marketing Cloud (export). Exports, updates or deletes data in SAP Marketing Cloud services from Treasure Data job results using the OData protocol.

SAP Marketing Cloud (import). Imports SAP Marketing Cloud data into Treasure Data, with incremental loading through $filter conditions added to the queries sent to SAP Marketing Cloud.

Cuenote. Delivers Treasure Data segments to YMIRLINK's Cuenote for personalized emails, with Treasure Data writing the files to an SFTP server for Cuenote to pick up.

WEBCAS. Publishes Treasure Data user segments to AZIA's WEBCAS for personalized email campaigns, by exporting files to an SFTP server that WEBCAS reads.