Integrations / Data Warehouse
Amazon Redshift
Structured event delivery to Amazon Redshift for analytics and reporting.
Datafly Signal delivers first-party events to Amazon Redshift server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Amazon Redshift expects.
Why route Amazon Redshift through Datafly Signal
The data lands in infrastructure you own
Signal writes to your Amazon Redshift directly from your own deployment. Datafly operates no intermediary and never holds a copy of your event data.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so the table holds hashed identifiers rather than raw personal data.
Client IP and user agent are recorded as event context
Both come from the original visitor request rather than from your server, so geography and device analysis reflects the actual visitor.
One consent decision governs every destination
Amazon Redshift is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
ad_impressionadd_to_cartbegin_checkoutcontent_likedcontent_savedcontent_sharedcontent_viewedfeature_usedinvoice_paidloginnewsletter_subscribedpagepaywall_viewedpurchaserefundremove_from_cartsearchselect_promotionsign_upsubscription_cancelledsubscription_startedtrial_startedvideo_ad_completedvideo_ad_skippedvideo_ad_startedvideo_content_completedvideo_content_startedvideo_playback_completedvideo_playback_pausedvideo_playback_resumedvideo_playback_startedview_cartview_itemview_item_listVertical presets
Retail, Media & Publishing, B2B / SaaS, General. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Amazon Redshift documentation.
Frequently asked questions
Does Datafly Signal integrate with Amazon Redshift?
Yes. Datafly Signal delivers first-party events to Amazon Redshift server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Amazon Redshift expects. The integration is included in every deployment at no additional cost.
How is server-side Amazon Redshift tracking different from the Amazon Redshift tag?
The Amazon Redshift tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Amazon Redshift from your server, so delivery does not depend on browser conditions.
What personal data is sent to Amazon Redshift?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Amazon Redshift receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Amazon Redshift?
The blueprint ships with mappings for ad_impression, add_to_cart, begin_checkout, content_liked, content_saved, content_shared, content_viewed, feature_used, and more. Any event in your schema can be mapped to Amazon Redshift through pipeline configuration without a code change.
Do I need to keep the Amazon Redshift tag on my site?
No. Signal delivers to Amazon Redshift from the server, so no client-side Amazon Redshift script is required on your site.
Other data warehouse integrations
Ready to move Amazon Redshift server-side?
See how Datafly Signal delivers first-party events to Amazon Redshift from infrastructure you control, with hashed identity and consent enforcement built in.