Meta Conversions API (CAPI) & Events - B2B SaaS
Best practices for sending conversion data to Meta via the Conversions API: event hierarchy, CRM vs middleware, deduplication, and Event Match Quality. Use this when setting up or auditing CAPI, choosing between HubSpot native and n8n, or improving event match quality.
Best Option for B2B SaaS: CRM to CAPI (with Pixel)
- Source of truth: Your CRM (HubSpot, Salesforce, etc.).
- Conversion events: CRM lifecycle stages (Lead, MQL, Opportunity, Customer), not only a single "Lead" from the site.
- Sending: Server-side via Conversions API from the CRM (or from a system that has the same CRM data).
- Redundancy: Use both the Meta Pixel (browser) and CAPI (server) for the same conversion where possible, with deduplication so Meta counts it once.
This gives optimization on real pipeline (opportunity/customer), resilience to iOS/ad blockers, and a proper offline conversion loop: Meta lead to CRM to stage changes to CAPI back to Meta.
Recommended Event Hierarchy (B2B SaaS)
| Event (example) |
When to send |
Why |
| Lead (or initial_lead) |
Contact enters "Lead" / first form or demo |
Top-of-funnel volume |
| marketingqualifiedlead |
Contact becomes MQL |
Qualified intent |
| opportunity |
Deal/opportunity created |
Pipeline; strong optimization target |
| customer |
Closed-won |
Revenue; best for value optimization |
Send one CAPI event per lifecycle stage you care about. Set conversion event priority in Events Manager so the event you optimize for (e.g. Lead or Opportunity) ranks above PageView and other events.
Where to Send From: Best vs Second Best
| Option |
When it's best |
| CRM native (e.g. HubSpot to Meta) |
You want one place to manage sync. Data sharing (Email, Phone, Click ID) is on for all lifecycle events and Event Match Quality is acceptable (e.g. 6+/10). You only need Meta (and maybe other native integrations). No custom logic required. |
| n8n (or similar) between CRM and Meta |
Event Match Quality stays low despite HubSpot data sharing. You need normalize + hash per Meta's spec (SHA-256, E.164 phone, etc.). You need to send to multiple destinations (Meta + LinkedIn, Google, Segment). You need custom logic (e.g. only send when deal value > X, or only for paid-source contacts). You want one event_id for pixel + CAPI and full control over deduplication. Compliance: you want to hash in middleware and never send plain PII. |
Order of preference: (1) Native HubSpot to Meta with Data sharing on for all events. (2) If match quality stays low or you need custom logic/multi-destination/hashing control, add n8n (or Segment, or custom backend): CRM to n8n to normalize + hash to CAPI.
When n8n Is Better Than HubSpot Native
- Low Event Match Quality even with HubSpot data sharing on - n8n lets you normalize and hash exactly per Meta's spec.
- Multiple destinations - One workflow: HubSpot to n8n to Meta CAPI + LinkedIn, Google, etc.
- Custom event mapping or filtering - e.g. only send when deal value > X, or only contacts from paid campaigns.
- Same event_id for pixel + CAPI - Full control for deduplication when the pixel fires with a known event_id and you want CAPI to send the same one.
- Compliance / data control - Hash in n8n, filter by consent, suppress segments before sending.
Deduplication: Where It Happens
- Where: In Meta's systems. You don't configure dedup in HubSpot or n8n; you send the right identifiers.
- How: Send the same
event_id (and same event_name) from both the pixel (e.g. on thank-you page) and CAPI (from CRM or n8n when that conversion is recorded). Meta merges them into one conversion.
- If the conversion only exists in the CRM (e.g. "became Opportunity" days later), you only send CAPI - no pixel event to dedupe with.
Event Match Quality (EMQ)
- Send user_data with every CAPI event: at least email and phone (normalized, then hashed per Meta's rules). Optionally: first name, last name, city, state, zip, country, external_id (your CRM ID, hashed).
- HubSpot: Use "Data sharing" and select Email, Phone, Click ID (and any other recommended fields) for all lifecycle events.
- n8n: Use normalize + hash (Crypto node or Code node with
crypto.createHash('sha256').update(str).digest('hex')) so every event includes hashed em, ph, etc. Meta expects hex (lowercase).
- Check Event Match Quality in Events Manager; aim for 6+/10 or "Good." Low scores (e.g. 3.2-3.8) mean Meta can't match well - improve user_data or add hashing via n8n.
Meta CAPI Best Practices (Summary)
- Pixel + CAPI for the same events (redundant setup).
- Deduplication: same
event_name + event_id (or external_id + fbp) from pixel and CAPI.
- Parameters: Send required (e.g.
action_source, event_source_url, client_user_agent for web) and recommended customer information (em, ph, fn, ln, etc.) - hashed where required.
- Real time: Send events as soon as the stage changes (or at least daily).
- Test: Use Meta's Test Events tool and Payload Helper to validate.
- Post-setup: Check Event Match Quality; avoid changing pixels or campaign structure unnecessarily during learning.
Related Files
- meta-setup-and-tracking.md - Pixel, events, domain verification, first campaign
- audience-strategy.md - Prospecting audiences, data hierarchy
- campaign-structure.md - Remarketing vs prospecting, ABO/CBO/Advantage+
- optimization-playbook.md - Decision trees, weekly cadence, scaling protocol
1---2name: meta-capi-and-events3description: Use this skill when wiring the Conversions API and funnel events — feeding MQL/SQL signal back so Meta optimizes for qualified pipeline, not form-fills.4---56# Meta Conversions API (CAPI) & Events - B2B SaaS78Best practices for sending conversion data to Meta via the Conversions API: event hierarchy, CRM vs middleware, deduplication, and Event Match Quality. Use this when setting up or auditing CAPI, choosing between HubSpot native and n8n, or improving event match quality.910---1112## Best Option for B2B SaaS: CRM to CAPI (with Pixel)1314- **Source of truth:** Your CRM (HubSpot, Salesforce, etc.).15- **Conversion events:** CRM **lifecycle stages** (Lead, MQL, Opportunity, Customer), not only a single "Lead" from the site.16- **Sending:** **Server-side** via Conversions API from the CRM (or from a system that has the same CRM data).17- **Redundancy:** Use **both** the Meta Pixel (browser) and CAPI (server) for the same conversion where possible, with **deduplication** so Meta counts it once.1819This gives optimization on real pipeline (opportunity/customer), resilience to iOS/ad blockers, and a proper offline conversion loop: Meta lead to CRM to stage changes to CAPI back to Meta.2021---2223## Recommended Event Hierarchy (B2B SaaS)2425| Event (example) | When to send | Why |26|-----------------|--------------|-----|27| Lead (or initial_lead) | Contact enters "Lead" / first form or demo | Top-of-funnel volume |28| marketingqualifiedlead | Contact becomes MQL | Qualified intent |29| opportunity | Deal/opportunity created | Pipeline; strong optimization target |30| customer | Closed-won | Revenue; best for value optimization |3132Send **one CAPI event per lifecycle stage** you care about. Set **conversion event priority** in Events Manager so the event you optimize for (e.g. Lead or Opportunity) ranks above PageView and other events.3334---3536## Where to Send From: Best vs Second Best3738| Option | When it's best |39|--------|-----------------|40| **CRM native (e.g. HubSpot to Meta)** | You want one place to manage sync. Data sharing (Email, Phone, Click ID) is on for all lifecycle events and Event Match Quality is acceptable (e.g. 6+/10). You only need Meta (and maybe other native integrations). No custom logic required. |41| **n8n (or similar) between CRM and Meta** | Event Match Quality stays low despite HubSpot data sharing. You need **normalize + hash per Meta's spec** (SHA-256, E.164 phone, etc.). You need to send to **multiple destinations** (Meta + LinkedIn, Google, Segment). You need **custom logic** (e.g. only send when deal value > X, or only for paid-source contacts). You want **one event_id** for pixel + CAPI and full control over deduplication. **Compliance:** you want to hash in middleware and never send plain PII. |4243**Order of preference:** (1) Native HubSpot to Meta with Data sharing on for all events. (2) If match quality stays low or you need custom logic/multi-destination/hashing control, add **n8n** (or Segment, or custom backend): CRM to n8n to normalize + hash to CAPI.4445---4647## When n8n Is Better Than HubSpot Native4849- **Low Event Match Quality** even with HubSpot data sharing on - n8n lets you normalize and hash exactly per Meta's spec.50- **Multiple destinations** - One workflow: HubSpot to n8n to Meta CAPI + LinkedIn, Google, etc.51- **Custom event mapping or filtering** - e.g. only send when deal value > X, or only contacts from paid campaigns.52- **Same event_id for pixel + CAPI** - Full control for deduplication when the pixel fires with a known event_id and you want CAPI to send the same one.53- **Compliance / data control** - Hash in n8n, filter by consent, suppress segments before sending.5455---5657## Deduplication: Where It Happens5859- **Where:** In **Meta's systems**. You don't configure dedup in HubSpot or n8n; you send the right identifiers.60- **How:** Send the **same `event_id`** (and same `event_name`) from both the **pixel** (e.g. on thank-you page) and **CAPI** (from CRM or n8n when that conversion is recorded). Meta merges them into one conversion.61- If the conversion **only** exists in the CRM (e.g. "became Opportunity" days later), you only send CAPI - no pixel event to dedupe with.6263---6465## Event Match Quality (EMQ)6667- Send **user_data** with every CAPI event: at least **email** and **phone** (normalized, then hashed per Meta's rules). Optionally: first name, last name, city, state, zip, country, **external_id** (your CRM ID, hashed).68- **HubSpot:** Use "Data sharing" and select Email, Phone, Click ID (and any other recommended fields) for **all** lifecycle events.69- **n8n:** Use normalize + hash (Crypto node or Code node with `crypto.createHash('sha256').update(str).digest('hex')`) so every event includes hashed `em`, `ph`, etc. Meta expects **hex** (lowercase).70- Check **Event Match Quality** in Events Manager; aim for 6+/10 or "Good." Low scores (e.g. 3.2-3.8) mean Meta can't match well - improve user_data or add hashing via n8n.7172---7374## Meta CAPI Best Practices (Summary)7576- **Pixel + CAPI** for the same events (redundant setup).77- **Deduplication:** same `event_name` + `event_id` (or `external_id` + `fbp`) from pixel and CAPI.78- **Parameters:** Send required (e.g. `action_source`, `event_source_url`, `client_user_agent` for web) and recommended **customer information** (em, ph, fn, ln, etc.) - hashed where required.79- **Real time:** Send events as soon as the stage changes (or at least daily).80- **Test:** Use Meta's Test Events tool and Payload Helper to validate.81- **Post-setup:** Check Event Match Quality; avoid changing pixels or campaign structure unnecessarily during learning.8283---8485## Related Files8687- **meta-setup-and-tracking.md** - Pixel, events, domain verification, first campaign88- **audience-strategy.md** - Prospecting audiences, data hierarchy89- **campaign-structure.md** - Remarketing vs prospecting, ABO/CBO/Advantage+90- **optimization-playbook.md** - Decision trees, weekly cadence, scaling protocol
swan-gtm