Conversions for Meta and Google Ads

Tell Meta and Google Ads which purchases, appointments and leads came from your ads, through the gate that decides what qualifies.

When an ad brings in someone who ends up buying, booking or leaving their details, the ad platform needs to know in order to optimize. With met.conversions you report that fact from your system —the one that knows the payment came in— and Met carries it to Meta (Conversions API) and to Google Ads.

You do not emit directly. Everything you report goes through the conversion gate, the same one the conversions proposed by the Met and by flows go through. The gate checks that there is an ad behind it, that the event is on the business's list and that the fact is backed up, and it tells you what it decided. That is what keeps a buggy integration from inflating campaign results.

There are two paths:

Before you start

• Your key needs conversions:write. It does not work with a test key (403 test_mode_restricted): every accepted conversion is a real event in the ad account.
• The business has to have conversions turned on in the panel, with its list of events. Without that, everything comes out discarded with reason: "integration_inactive".
• Both methods return 201 even when the gate discards: always read decision.

A contact's conversion

const r = await met.conversions.report({
  contact_id: 4821,
  event_name: 'Purchase',
  value: 250000,
  currency: 'COP',
  bucket: 'pedido-10293',
});

if (r.decision !== 'accepted') console.log('Not sent:', r.decision, r.reason);

r = met.conversions.report(
    contact_id=4821,
    event_name="Purchase",
    value=250000,
    currency="COP",
    bucket="pedido-10293",
)
if r["decision"] != "accepted":
    print("Not sent:", r["decision"], r.get("reason"))

curl -X POST https://api.met.meteor.com.co/api/v1/conversions \
  -H "Authorization: Bearer $METEOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contact_id":4821,"event_name":"Purchase","value":250000,"currency":"COP","bucket":"pedido-10293"}'

What the gate requires

On top of that, a contact does not accept more than 10 conversions in 24 hours (the default cap): it is the brake for a flow stuck in a loop.

A web conversion (Pixel)

If your site fires the Pixel in the browser, also report it from your server with the same event_id: Meta merges the two and does not count it twice.

// In the browser: fbq('track', 'Purchase', { value: 250000, currency: 'COP' }, { eventID: 'ord-10293' });
const r = await met.conversions.reportWeb({
  event_name: 'Purchase',
  event_id: 'ord-10293',
  fbp: req.cookies._fbp,
  fbc: req.cookies._fbc,
  email: customer.email,
  event_source_url: 'https://mystore.co/thanks',
  client_ip_address: req.ip,
  client_user_agent: req.headers['user-agent'],
  value: 250000,
  currency: 'COP',
});

r = met.conversions.report_web(
    event_name="Purchase",
    event_id="ord-10293",
    fbp=request.cookies.get("_fbp"),
    email=customer_email,
    client_ip_address=visitor_ip,
    client_user_agent=visitor_user_agent,
    value=250000,
    currency="COP",
)

curl -X POST https://api.met.meteor.com.co/api/v1/conversions/web \
  -H "Authorization: Bearer $METEOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_name":"Purchase","event_id":"ord-10293","fbp":"fb.1.1730000000.123","gclid":"Cj0KCQ…","value":250000,"currency":"COP"}'

• At least one way of recognizing the visitor is required: fbp, fbc, email, phone or external_id for Meta; gclid, gbraid, wbraid, email, phone or external_id for Google Ads. With none, it comes out no_match_key.
• email, phone and external_id travel in plain text to Met and leave Met as SHA-256 hashes; fbp, fbc and Google's click identifiers go as they are.
• client_ip_address and client_user_agent are the visitor's, not your server's: they improve matching.
• This path does not ask for evidence: the fact already happened in the browser.
• If the visitor came in through a Google ad, also pass gclid (or gbraid / wbraid), taken from the landing URL.

What it returns

{ "decision": "discarded", "reason": "uncorroborated" }

Hearing about delivery

accepted says it left the gate; delivery to Meta comes afterwards. Subscribe to the events (scope conversions:read; see Webhooks):

Common errors