Destinations in Converge let you forward data to other platforms and services. They help streamline your data flow and make your marketing setup more efficient.


Available destinations

Converge supports destinations across your marketing stack, including:

  • Ad platforms: Meta Ads (Facebook Ads), Google Ads, Pinterest Ads, TikTok Ads
  • Analytics: Google Analytics 4
  • Other tools: BigQuery, Klaviyo, Postscript

See the full list of supported destinations here.


Event mapping

Converge automatically maps your tracked events to the expected format for each destination. For example:

  • Placed OrderPurchase in Meta Ads
  • Placed Orderpurchase in GA4
  • Placed OrderPURCHASE in Snapchat

Each destination has a default mapping, which automatically translates events that follow the Event Spec to the right format for your destination.

You can also send custom events and map them manually to destination-specific events.

Default event mapping for the Meta Ads destination


Client-side and Server-side

Each destination can forward events either client-side, server-side or both, depending on what the destination integration supports. You’ll find this info when adding a new destination or in the docs for each destination.

Forwarding modes for the Meta Ads destination

How a event can be forward depends on how the event was tracked:

Event sourceForwarding modeSupported
Client-sideClient-side
Client-sideServer-side
Server-sideClient-side
Server-sideServer-side

Event enrichment

Converge enriches server-side forwarded events with data from the user’s profile.

For example, if the event itself doesn’t include an email address, but the profile of user identified by Converge does, Converge will add the email before forwarding the event.

You can control whether an event is forwarded to your destination based on user consent.

Each destination is categorized as either Analytics or Marketing. You can configure how to forward events in different scenario’s.

Consent settings for a destination

Consent in Converge is different from Google Consent Mode or Microsoft Consent Mode. If you need to use those, you’ll need to implement them separately. Learn more here.

Monitoring destinations

Use Event Quality to inspect the properties being forwarded with your events and Logs to review individual events sent to each destination.

Event Quality report for a Meta Ads destination

Finding Destinations

You can find your destinations by going to Event streams under Destinations in the main menu.

Where to find your destinations

Further reading