Amazon S3 integrations across CDPs

Writes 6sense Data Packs and audit logs into your Amazon S3 bucket through a 6sense IAM role, for long-term retention and SIEM monitoring, once your CSM enables it.

Amazon S3

Destination. Exports Real-Time CDP audiences on a recurring schedule as CSV data files into the customer's own Amazon S3 buckets, set up in the UI or through the Flow Service API.

Source. Brings files from Amazon S3 into Experience Platform in batches, accepting delimited, XDM JSON or XDM Parquet data without manual download or upload.

Destination. Sends Parquet, CSV, JSON and other files from Amperity to any Amazon S3 bucket, for storage or for other systems to pick up.

Source. Pulls files of any supported format from Amazon S3 buckets into Amperity using cross-account roles, and it is the most used Amperity data source.

Imports CSV or XML files from an Amazon S3 bucket into Bloomreach and exports CSV, JSON or JSON lines files to it, with regex file matching, new-file triggers and dynamic file names.

Imports CSV files from Amazon S3 buckets into BlueConic profiles, groups and timeline events and exports segment profiles and events as CSV on a schedule, with optional PGP encryption.

Email CSV. Writes Blueshift campaign emails as CSV files to your Amazon S3 bucket instead of sending them, every 30 minutes for triggered campaigns, for bulk sending through another system.

Push CSV. Saves push notifications from Blueshift campaign triggers as CSV files in an Amazon S3 bucket you own, avoiding provider rate limits by sending them in bulk elsewhere.

SMS CSV. Exports SMS and MMS messages from Blueshift campaigns into CSV files in your S3 bucket rather than delivering them, so a messaging provider can send them in bulk.

Import and export. Connects your own Amazon S3 location to Blueshift for importing customers, events and catalogs and for storing files Blueshift generates, such as customer data syndication exports.

Currents. Writes Braze Currents event streams and dashboard exports, such as CSV files and engagement reports, to your Amazon S3 bucket using a secret key or role ARN.

Cloud Data Ingestion. Ingests JSON, CSV or Parquet files into Braze as soon as they land in an Amazon S3 bucket, with an SQS queue telling Braze about each new file.

Export. Exports data from Chord's Snowflake warehouse into a brand's own S3 bucket, ideally one kept for this purpose, through an IAM role with write access and a Chord external ID.

Import. Lets Chord's Snowflake warehouse read data files from a brand's S3 bucket through an IAM role that trusts Chord's user ARN and external ID, so the files can be ingested.

Exports CleverTap event data in bulk to an Amazon S3 bucket set up with an access key or IAM policy, available on Enterprise, Advanced and Cutting Edge plans.

Exports DinMo models or segments to an Amazon S3 bucket as CSV, JSON, XML or Parquet files, with folder paths, timestamped file names and snapshot, upsert or insert modes.

Destination. Exports warehouse data from Fivetran Activations to files in an Amazon S3 bucket, sending the full dataset and then only changes, or replacing a file on each run.

Source. Indexes CSV files in an Amazon S3 bucket so Fivetran Activations can sync them like tables, connecting through a read-only IAM role in your AWS account.

Destination. Exports user and product data from your warehouse to Amazon S3 as CSV files, with custom field names and paths.

Source. Reads CSV or JSON files from Amazon S3 buckets as a Hightouch source, for syncing to other tools.

Export. Writes selected Insider One events, their parameters and extra user attributes to your Amazon S3 bucket as CSV files at the sync frequency you pick, starting from activation.

Import. Imports CSV or JSONL files of user attributes, events and purchases from your Amazon S3 bucket into Insider One, picking up each new file as SQS notifications report it.

Writes Klaviyo profiles and events as files to an Amazon S3 bucket, ready to load into whichever data warehouse or platform you use.

Moves data files between your Amazon S3 buckets and Lexer through bucket-to-bucket transfers set up with an AWS IAM role and access keys, for loading customer data and activating segments.

Imports CSV or JSON files from Amazon S3 buckets into Lytics on a schedule and writes Lytics user profiles or raw events back to S3 as CSV or JSON files.

Audiences. Delivers a daily file of each audience's members from mParticle to an Amazon S3 bucket you own.

Events. Writes mParticle event batches to an Amazon S3 bucket for archiving or processing in your own data stack.

Stores NICE CXone recordings and other Cloud Storage Services files in your own Amazon S3 bucket instead of the default one, preferably set up with NICE's CloudFormation template.

Reads data files from an Amazon S3 bucket into Totango with access keys or an AWS role trusting Totango's account, granted object get and bucket list permissions.

Delivers customized Ometria data exports to an Amazon S3 bucket with put and list permissions, using your AWS access and secret keys, with export errors emailed to you.

Export. Writes Oracle Unity data objects and segments into an Amazon S3 bucket path as comma-separated, gzip-compressed files, through an AWS destination used by export jobs and segment deliveries.

Import. Pulls files from a path in an Amazon S3 bucket into Oracle Unity with a recurring or on-demand ingest job, once an AWS source holds the bucket's endpoint, storage key and secret.

Content provider. Connects an S3 bucket to Redpoint Interaction as an external content provider for hosted assets and file exports, with optional CloudFront delivery and KMS encryption.

Data Management. Gives Redpoint Data Management access to Amazon S3 buckets through bucket policies or account credentials set site-wide or per user, including cross-account access.

Data lake. Loads RudderStack events into an S3 data lake as structured files, optionally registering the schema in AWS Glue for querying with AWS tools.

Object storage. Writes RudderStack events to an Amazon S3 bucket as batched files, for archiving or processing in your own data stack.

Source. Reads Parquet files from Amazon S3 with RudderStack Reverse ETL using S3 Select, which AWS has closed to new customers.

Reads structured and unstructured files from Amazon S3 buckets into Data 360 on a schedule, and S3 can also receive Data 360 segment activations.

Moves data both ways between Amazon S3 buckets and SAS Customer Intelligence 360 through a community connector whose terms an admin accepts, without SAS technical support.

Storage destination. Stores raw Segment event data as files in an Amazon S3 bucket you own, for later loading or analysis.

Source via Lambda. Sends records from files dropped in an Amazon S3 bucket into Segment through an AWS Lambda function you deploy.

Exports flow audiences from Simon Data as CSV, TSV or JSONL files to the Amazon S3 bucket set up in your account, optionally dating file names with Jinja so later runs don't overwrite earlier files.

Archives enriched or failed Snowplow event streams from Kinesis into Amazon S3 as Gzip files with the S3 Loader, passing records it can't write to a separate Kinesis stream.

Writes full or custom event, visitor and log data to your Amazon S3 bucket from AudienceStream or EventStream.

File import. Imports files placed in your own Amazon S3 bucket through Tealium's File Import, using access keys and a bucket policy that lets Tealium reach the bucket in the profile's region.

Export v1. 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.

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

Parquet export. 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.

Filename metadata import. 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.

Import v1. 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.

Import v2. 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.

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

Destination. Exports Zeotap audiences to a folder in your Amazon S3 bucket as CSV files, with MAIDs, hashed emails or phones and CRM IDs, or any identifiers and attributes.

Source. Imports customer data kept in your own Amazon S3 account into Zeotap, with an automatic sync at the frequency you set keeping it up to date.

Reads files from Amazon S3 into Zeta Data Flows for cleaning and routing, and exports audience CSV or JSON files and report builder reports back to S3, with IAM access keys.