Amazon Redshift integrations across CDPs

Connects ActionIQ to Amazon Redshift with HybridCompute, pushing generated SQL down to the warehouse and returning only the needed results, usually customer IDs, without copying the data.

Brings Amazon Redshift data into Experience Platform for Real-Time CDP Ultimate customers.

Gets Amperity data into Amazon Redshift by sending it to Amazon S3 first, then loading it with tools such as AWS Glue or a Lambda function.

Pulls customer, event, catalog and voucher data from Amazon Redshift into Bloomreach through the shared PostgreSQL / Redshift connector, whose health checks can stop Redshift Serverless from pausing.

Imports Amazon Redshift tables or SQL query results into BlueConic profiles, orders, events and groups, and exports profiles in sync, replace or append mode staged through Amazon S3.

Loads Amazon Redshift data into Blueshift by unloading customer, event or catalog tables to Amazon S3 for import, or by syncing customers and events through Census or RudderStack.

Loads new rows from Amazon Redshift tables or views into Braze profiles, events and catalogs on a schedule, with Braze connecting to Redshift over the internet.

Reads data straight from your Amazon Redshift instance into CaliberMind instead of standard connectors, with a possible setup fee for schema mapping and monthly fees tied to data volume.

Imports data from an Amazon Redshift cluster into CleverTap using the cluster endpoint, port, database credentials and an optional schema that defaults to public.

Connects Amazon Redshift, provisioned or Serverless, to DinMo as the source for models, segments and activations, reached directly or through AWS PrivateLink, an SSH tunnel or SSM.

Destination. Writes warehouse data into Amazon Redshift tables from Fivetran Activations, matched on primary keys or unique key columns, with upsert, update and insert options.

Source. Extracts Amazon Redshift tables and views for Fivetran Activations syncs with the UNLOAD command, which in a VPC deployment needs an S3 VPC endpoint.

Events storage. Stores events collected by Hightouch Events in Amazon Redshift, where Hightouch creates the event tables and adds columns as new fields arrive.

Source. Connects Amazon Redshift to Hightouch as a source, so SQL, dbt or table-based models built there can sync to any destination.

Export. Exports Insider One user or event data to an Amazon S3 bucket you own, from which your Amazon Redshift pipeline, for example the COPY command, loads it into tables.

Import. Brings Amazon Redshift tables or query results into Insider One by unloading them as CSV files to your S3 bucket and mapping those files through the S3 import.

Exports Klaviyo profiles and events to an Amazon Redshift instance, with the option to leave out events from integrations that already feed Redshift.

Data warehouse import. Imports profile data from Amazon Redshift into Klaviyo on a schedule through a Klaviyo-only service user with the fewest rights it needs, with an Advanced KDP subscription.

Imports user tables from Amazon Redshift into Lytics over a PostgreSQL connection and keeps a Redshift table of a Lytics audience updated by loading files staged in S3.

Loads all incoming mParticle data into an Amazon Redshift cluster, so you can query events and user data with SQL.

Warehouse Sync. Brings user and event data from Amazon Redshift or Redshift Serverless into mParticle, with access through an IAM role that mParticle assumes.

Retrieves Amazon Redshift schema tables into Totango with SQL, signing in as a user in a read-only group that has select rights on the schema.

Export. Places Oracle Unity segments or data objects on an SFTP server as files, to be copied into an S3 bucket and loaded from there into Amazon Redshift.

Import. Takes Amazon Redshift data into Oracle Unity from files on an SFTP server, using a Secure FTP source with an RSA key and an ingest job, with optional decryption.

Connects a Redpoint Interaction tenant to Amazon Redshift as its data warehouse by picking the AWSRedshift provider and entering host, database and login details.

Destination. Batch-loads RudderStack events into Amazon Redshift tables, following RudderStack's warehouse schema for users, pages, tracks and custom events.

Source. Reads tables or SQL models from Amazon Redshift with RudderStack Reverse ETL and syncs the rows to downstream tools on a schedule.

Connects Data 360 and Amazon Redshift through Zero Copy, querying Redshift tables in place and sharing Data 360 data back to Redshift.

Queries Amazon Redshift tables in place from SAP Emarsys Relational Data for segments and personalization tokens, with no CA certificate required and a 15-second connection timeout.

Loads Segment event data into Amazon Redshift on a schedule as a storage destination, ready for SQL analysis.

Data Graph. Connects a Redshift cluster to Segment's Data Graph through its own role and user, so Linked Audiences and Linked Events can use warehouse entity tables next to Profiles Sync data.

Reverse ETL source. Lets Segment Reverse ETL query an Amazon Redshift cluster as a dedicated database user and send the results to destinations, keeping sync state in its own schema.

Lets Simon Data extract tables from Amazon Redshift through a dedicated user granted select privileges, after Simon's public IP addresses are allowed through any firewall.

Loads enriched Snowplow events from AWS pipelines into Amazon Redshift, Redshift Serverless included, as an events table plus a joinable table for each custom event or entity.

Loads full or custom event and visitor data into Amazon Redshift tables in micro-batches or batches, from AudienceStream or EventStream.

Cloud data source. Reads a table or view from an Amazon Redshift cluster into Tealium attributes over JDBC, using the cluster's hostname, port, database, schema and credentials.

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

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

Live Connect zero-copy. 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.

Queries Amazon Redshift provisioned clusters from Zeta Data Flows to ingest selected data, connecting with host, port and database plus optional IAM authentication.