Destinations Overview
Destinations are external analytics services that receive a copy of your events via server-side forwarding.
Destinations are external analytics services that receive a copy of your events. Forwarding happens server-side — from the platform's backend, not from the user's browser. This means:
- Ad blockers don't affect delivery
- You control all destinations from one place
- No additional client-side scripts needed
Available destinations
| Destination | Status | Mechanism |
|---|---|---|
| Google Analytics 4 | ✅ MVP | GA4 Measurement Protocol |
| Facebook Pixel | ✅ MVP | Conversions API (CAPI) |
| Webhook (custom HTTP endpoint) | 🔜 Post-MVP | HTTP POST |
| Amplitude | 🔜 Post-MVP | HTTP API |
| Mixpanel | 🔜 Post-MVP | HTTP API |
| Segment | 🔜 Post-MVP | Segment HTTP API |
How to connect a destination
- Open your project and go to Destinations
- Click Add Destination and select a service
- Enter the required credentials (API keys, tokens — see each destination's guide)
- Configure event mapping (see below)
- Click Save & Activate
Event mapping
By default, the platform forwards events using the same name they were sent with. purchase_completed arrives at the destination as purchase_completed.
To override the name for a specific destination:
- Click Edit Mapping on the destination card
- Search for an event from your project's schema
- Set the name to use when forwarding to this destination
- Save
Mappings are per-destination — changing the name for GA4 does not affect Facebook Pixel.
You can also choose to forward only a subset of events to each destination. Events not included in the mapping are not forwarded.
Error handling
If a destination is unavailable or returns an error:
- The event is always saved in the platform regardless
- The error is logged and visible in the destination's activity log in the UI
- Failed deliveries are retried with exponential backoff for transient failures
Important limitations
Facebook Conversions API requires user_data parameters (email, phone) for accurate attribution. Since the platform does not store PII, only external_id (your user_id) is forwarded. For full attribution you'll need to pass hashed user data through a separate server-side setup.
Google Analytics 4 via Measurement Protocol does not support all GA4 features available through the gtag.js client-side tag. Session and engagement metrics may differ.