logo
Conversions•

Send your conversions to Meta Ads

Forward the leads CodeQR records to Meta Ads through the Conversions API, so campaigns optimize on conversions the browser pixel never sees.

Avatar for undefined
CodeQR Team
Content Team

A Meta pixel sees what happens in the browser. It does not see the sign-up your server confirmed an hour later, or the sale that closed on another device. The Conversions API exists for that, and CodeQR can send it the leads it already records.

Availability

  • Plan: Pro and above, or the 14-day trial, since it depends on conversion tracking.
  • Where: Settings → Integrations → Meta Ads, under Analytics.

Before you start

  • Conversion tracking on for the links you advertise, and leads reaching CodeQR — Send lead and sale events from your server. CodeQR can only forward what it has.
  • A Meta business account with access to the ad account and the dataset you want events in.

Steps

  1. Open Settings → Integrations.
  2. Under Analytics, select Meta Ads and connect the account.
  3. Choose the ad account and the dataset that should receive the events.
  4. Advertise your CodeQR links as usual. Each lead CodeQR records is forwarded.

Meta owns the permission screens that appear in step 2, so their exact wording follows your business account and the access it already grants. What CodeQR asks for is the ad account and the dataset.

Pixel or Conversions API

They are not alternatives, they are two paths for the same event, and Meta expects both.

  • The pixel fires in the browser and is blocked by ad blockers, by tracking prevention and by anyone who declines cookies.
  • The Conversions API is a server-to-server call and survives all three.

Sending both is the recommended setup. Meta deduplicates using the event name together with the event id, so the same conversion counted twice by two paths is still one conversion — as long as both carry the same identifiers.

TikTok Ads

The same integration pattern exists for TikTok Ads, also under Analytics, and it forwards both leads and sales. Connect it the same way.

What Meta does with it

Conversion events are what campaign optimization runs on. An ad set optimizing for "Lead" needs leads it can see; if the only signal is a browser pixel that half the audience blocks, the optimizer learns from half the data.

Verify it works

Open Meta Events Manager, select the dataset, and look at the recent activity for events arriving through the server. A lead you record in CodeQR should show up there within minutes, marked as coming from the API rather than the browser.

In CodeQR, the same lead appears in Customers — if it is not there, nothing was forwarded, and the problem is upstream of Meta.

Troubleshooting

No events arrive in Meta

Check CodeQR first. Open Customers and confirm the lead exists. Nothing is forwarded that CodeQR has not recorded.

Your Meta pixel is not active

That message is about the browser pixel on your site, not about the Conversions API. They are configured separately, and the API keeps working while the pixel is misconfigured.

The numbers in Meta do not match CodeQR

They never will exactly. Meta attributes to the ad using its own window and model; CodeQR attributes to the click on your link. See How CodeQR decides which click gets the sale.

Events look duplicated

Deduplication needs the same event id on both paths. If your pixel sends an event id CodeQR does not know, Meta sees two distinct events.

Related articles