Send conversions back to Meta and Google Ads

Conversion export sends what happened after the click, such as a paid order, back to Meta and Google Ads, so their bidding optimizes for real sales instead of form fills. It is not in the tab strip: press Ctrl+K (or ⌘K) and search for Conversions.

Each connected ad account has its own section on the page.

Set it up

1. Pixel (Meta) or Conversion action (Google Ads) — choose where conversions go. On Meta, pick the Pixel your campaigns already optimize against. On Google, pick an offline conversion action that is set up for purchases.
2. Events to export — tick the events to send. Nothing is exported until you choose. Only down-funnel events are offered, because sending a platform its own leads back would count them twice.
3. Test event code (Meta, optional) — while this is set, events appear only in Meta's Test Events tool and never reach your campaigns.
4. Click Save.

Queued events are sent automatically about every 15 minutes. Send … queued sends the waiting events straight away.

If you already run the Meta Pixel

Meta only removes duplicates between a browser event and a server event. Brainito sends the order ID as the event ID, which the standard Pixel setup also uses, so the two normally merge into one conversion. If your Pixel sends a different event ID, Meta counts the purchase twice. Check with a test event code before you turn this on.

The status column

Recent events are listed with Event, Occurred, Value and Status:

• Queued — waiting for the next send.
• Sending — in progress.
• Sent — accepted by the platform.
• Not sent — skipped on purpose, with the reason beside it.
• Failed — the platform refused it. Hover for the reason.

If you see Conversion export is turned off for this connection, events keep queueing but nothing is sent until it is switched back on. Contact support.

Next: press Ctrl+K, open Conversions, choose your Pixel, add a test event code, and Save.