How do I send conversions back to Meta, Google, and TikTok?

Add a pixel under Sidebar → Attribution → Pixels with its Conversions API token — each pixel is a destination Decisa forwards your verified conversions to, server-side.

Before you start

• A workspace with the Attribution module active and the Decisa pixel installed on your site.
• The platform credentials: for Meta, the Pixel ID and a Conversions API token; for TikTok, the pixel code and token; for Google, your Google Ads customer ID.
• Conversions already arriving in Decisa (from a checkout webhook or triggers) — pushback forwards what Decisa has verified.

Steps

1. Open Pixels and click Add pixel

   Go to Sidebar → Attribution → Pixels and click Add pixel. Each pixel is one destination — a workspace can hold many, one per site or platform.

2. Fill in the destination details

   Give it a Name, pick the Platform (Meta, TikTok, or Google), and enter the platform identifier: Pixel ID for Meta, Pixel code for TikTok, or Customer ID for Google. Paste the Conversions API token — it is stored encrypted and never shown again. Click Add pixel.

3. Check Delivery readiness

   Open the pixel and look at the Delivery readiness card on the Overview tab. You want "Ready to deliver conversions." Google pixels also need their events mapped to conversion actions in the Events tab — unmapped events will not deliver.

4. Add a trigger (optional)

   On the Triggers tab, click New trigger to fire a conversion without code: pick the Event (Purchase, Lead, and so on), choose Match on (CSS selector, Visible text, Page URL, or CSS class), enter the Match value — like /thank-you — set a Conversion value if you have one, and click Create trigger.

   Already built your triggers on another pixel? Click Copy from pixel, pick the source pixel, and review the preview — it shows exactly which triggers will be copied and which will be skipped because this pixel already has an identical one. Copies are independent (editing one later never changes the other) and running the copy again is safe.

What happens next

• Every verified conversion is forwarded server-side to each enabled pixel — including sales the browser pixel misses because of ad blockers or strict privacy settings.
• The platforms feed those conversions back into ad delivery: more complete purchase data means better-optimized campaigns and steadier reported results.
• Decisa sends each event with an event ID, so when your browser pixel reports the same conversion, the platform keeps one copy — no double counting.
• The Overview tab shows recent events live, so you can watch deliveries arrive.

Gotchas