Skip to content

Destinations

A destination is a platform Signals delivers data to over its server-side API: conversion events to Conversions API (CAPI) endpoints, membership changes to audience APIs, and offline outcomes to upload endpoints. Signals handles normalization, hashing, deduplication keys, and consent parameters per destination, so every platform receives data in the exact format it expects.

  1. Events from your connected sources are validated and processed once, centrally.
  2. For each destination connection, Signals maps the canonical event onto the platform’s API format: event names, identifier fields, dedup keys, and consent parameters.
  3. Delivery is server-to-server with retries. Failures surface in monitoring with the destination’s error message. See Monitoring & alerts.
  • Web Conversions: website events delivered to CAPI-style endpoints for attribution and optimization.
  • Offline Conversions: in-store and other offline outcomes uploaded for campaign measurement.
  • Lead Conversions: CRM funnel milestones delivered so platforms optimize for lead quality.
  • Custom Audience: customer list membership synced for targeting, suppression, and lookalikes.
  • App Conversions: app install and in-app events delivered server-side.

Each category maps to a use case, and the compatibility matrix on every page derives from that mapping.