Destinations
Destinations are where DATA Reshape sends your tracking data — analytics and advertising platforms, or your own systems. Each destination receives events processed through your server-side infrastructure, ensuring accurate attribution and improved data quality.
Supported Destinations
| Destination | Type | Documentation |
|---|---|---|
| Your Endpoint | Server-to-server | Overview, Payload Reference, Changelog |
| Google Analytics 4 | Analytics | Setup, Parameters |
| Google Ads | Advertising | Coming soon |
| Meta (Facebook) | Advertising | Setup, Parameters |
| TikTok | Advertising | Setup, Parameters |
| Criteo | Advertising | Coming soon |
Documentation Structure
Most destinations have two pages:
- Setup — recommended configuration in the destination's own interface for optimal tracking with DATA Reshape
- Parameters — default and custom parameters sent by DATA Reshape, and how to use them in the destination
Your Endpoint is the exception: the destination is a URL you own, so there is nothing to configure on a third-party platform. It is documented as an Overview, a full Payload Reference, and a Changelog.
How It Works
- Events are collected via the tracking script or webhooks
- DATA Reshape processes, validates, and enriches the data
- Processed events are delivered server-side to each configured destination
- Each destination receives only the events mapped in your account configuration