DATALYR

HubSpot to Meta Conversions API.

Send HubSpot qualified leads and won deals to Meta so ads optimize on the pipeline that closes. Each stage reaches your Meta Pixel with the ad click attached.

What gets sent.

What DATALYR sends from HubSpot to Meta Conversions API
DATALYR eventWhen it firesSent to Meta asWhat it carries
lead_qualifiedA deal moves to your qualified stageLeadA fixed value you enter, the contact email and the ad click when the email matches a visit
deal_wonA deal moves to Closed wonPurchaseThe deal amount as the value, with the deal ID as the order ID. Never counted as revenue

How it's matched.

DATALYR checks these in order and stops at the first one that finds the ad click.

  1. The contact email. HubSpot events match by email alone, to a visit DATALYR already knows from an identify call on your form, a booking or a payment

Meta gets the click ID (fbc, built from the _fbc cookie or fbclid) and browser ID (fbp), plus email, phone and name hashed with SHA-256 when known. DATALYR sends the same event ID the browser pixel uses, so Meta merges the pair into one conversion.

How it works.

  1. 01

    Connect HubSpot.

    HubSpot has no one-click connection. Send each stage to DATALYR from Zapier or a HubSpot workflow with your write key, using the request bodies on the HubSpot card in Sources. Put the tracking script on your landing pages.

  2. 02

    Connect Meta.

    Open Sources, select connect on Meta Ads and sign in with Facebook Login for Business. Set the primary ad account. In Conversions, select manage rules, then new rule: trigger event lead_qualified, target platform Meta, your pixel, platform event Lead. Set a fixed value: what a qualified lead is worth to you.

  3. 03

    Check one conversion.

    Move one test deal for a contact who filled in your form from a Meta ad click. Find lead_qualified in Events, then open the newest row in Conversions and read the reply from Meta.

Check it worked.

  • In Events, the lead_qualified row has source hubspot, and in Users the pageview and the lead_qualified sit on one user. If rules never fire, the request body is missing "source": "hubspot", and events arrive with source api.
  • Set a Test Events code on the rule, then select send test event. The event shows in Events Manager under Test events with the name, value and currency you mapped. Without a code, a test is a real conversion.
  • Open the newest row in Conversions. Its status reads sent, and the response body carries Meta's own acceptance field.

View docsHubSpotMeta AdsConversion delivery

Questions, answered.

Contact us
  • No. deal_won carries the deal amount, but its cash_role is non_cash_fact, so no DATALYR revenue report counts it. Cash comes from a payment source such as Stripe or Commas.

  • lead_qualified. Most deals close after Meta's 7 day window, so a qualified lead is the stage Meta can learn from. deal_won goes to Meta as a Purchase with the deal amount.

  • A DATALYR write key from Settings, API, plus either a Zapier plan with multi-step Zaps and Webhooks by Zapier, or HubSpot Data Hub Professional or above for the Send a webhook action.

See what really drives revenue.

Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.

Get started