Skip to main content
Upstack Data

Lasso Commerce to Meta Conversions API

Forward every Lasso Commerce event to Meta Conversions API server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.

What changes

What changes when Lasso Commerce feeds Meta Conversions API.

Higher Event Match Quality

More hashed identifiers on every event — email, phone, external ID, click ID — so EMQ rises and Meta matches more of what you send.

Pixel and CAPI, one install

One source of truth for both, with browser and server events deduplicated on event_id so purchases are never double-counted.

Every event, server-side

Storefront and checkout events are captured from Lasso Commerce on the server, independent of the browser.

One setup, every destination

Connect Lasso Commerce once and forward to every ad platform, email tool and warehouse you run.

What actually moves

What Lasso Commerce carries, and what Meta Conversions API needs.

Lasso Commerce and Meta Conversions API describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Lasso Commerce can put on an event, the right is what Meta Conversions API can actually use.

Lasso Commerce sends

order_id
Lasso checkout order reference
email / phone
contact captured at checkout
line_items
products and quantities on the order
total / discount
order economics after adjustments
landing_domain
the site the shopper started on, before the checkout hop
customer_type
new or returning, resolved before send

Meta Conversions API receives

em, ph (SHA-256)
raise Event Match Quality
fbclid / _fbp
credit the click that drove it
external_id
stable person across sessions
event_id
dedupe against the browser pixel
value / currency
value-based bidding

Delivery you can audit

How you know it is working.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

  • Per-event inspection

    Every conversion is inspectable from the moment it fires to the moment the platform confirms it.
  • Deduplication

    Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filtering

    Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

Where to check in Meta Conversions API

Events Manageryour datasetEvent Match Quality. Server events appear with a Conversions API badge, and the match-quality score is scored per parameter so you can see which identifiers arrived.

Get Lasso Commerce talking to Meta Conversions API.

A 15-minute walkthrough of this connector on your own account.