Destinations
Overview:
Follow this guide to understand what Destinations are, why they are a foundational part of Elevar’s server-side tracking, and what integrations Elevar currently supports.
In Elevar, a Destination is any endpoint or external platform where tracking data is sent once it has been collected and processed by Elevar’s server-side infrastructure. Destinations are typically marketing pixels, analytics platforms, advertising services, affiliate networks, email or SMS platforms, and data forwarding services.
Once Elevar ingests events from your data sources (such as browser events or webhooks), it processes that data and routes it to your connected Destinations according to your configuration in the dashboard.
What is a Destination?
A Destination in Elevar is essentially a remote endpoint where your enriched event data is sent. This usually corresponds with external integrations such as ad platforms, analytics tools, CRM/email tools, affiliate partners, and other marketing or BI systems.
For example:
- Sending purchase, pageview, and custom event data to Google Analytics 4
- Forwarding conversion events to Meta (Facebook), TikTok, Pinterest, and other advertising platforms
- Sending order and subscriber events to email/SMS platforms like Klaviyo and Postscript
- Routing structured server-side data to affiliate networks like Impact or Awin
Each Destination gives you control over the event mapping and configuration so you can tailor how Elevar’s server-side events appear and behave within your downstream tools. For billing and plan limits, destinations are counted by channel rather than by the total number of destination instances configured within your account.
Important: Your ability to add new or additional Destinations in Elevar may depend on your usage-based billing plan or subscription tier.
How Destinations Work:
Elevar receives tracking data from your sources (e.g., browser data layer, Shopify webhooks, API sources) and performs server-side enhancements such as session enrichment, deduplication, and identity stitching. After processing, Elevar then dispatches this normalized event stream to your enabled Destinations.
When you add a destination in the Elevar dashboard, Elevar handles:
- Mapping event properties to the destination’s expected schema
- Authenticating requests using API keys or tokens
- Managing retries, batching, and error handling
- Respecting consent signals and privacy requirements
This server-side delivery improves data fidelity and reliability compared to client-only event firing.
What is a destination instance?
A destination instance is an individual configuration of a destination. You may have multiple instances of the same destination type configured within your account. While these instances provide additional flexibility for data routing and account management, they do not increase the number of destinations counted against your plan limit.
Why does my destination count look different than my total destination cards?
Destination counts are based on unique marketing channels rather than the total number of destination instances. For example, three Meta destination cards count as:
- One destination
- Three destination instances
Your plan limit applies to destinations, not destination instances.
Elevar Supported Server-Side Destinations
Live Server-Side Integrations:
Analytics:
Advertising:
Affiliate:
Email and SMS:
Attribution and BI:
Integrations available in Beta:
These destinations are available for public use, however we are still learning and making modifications as we finalize the integrations for these.
Advertising:
Affiliate:
Email and SMS:
Updated 4 days ago