Meta CAPI for CRM

Learn how to connect your CRM (HubSpot, GoHighLevel) to Meta Conversion API for CRM with AnyTrack. Sync lifecycle events like Qualified Lead, Meeting Booked, and Customer back to Meta for campaign optimization, improved Event Match Quality, and full-funnel attribution across web and CRM touchpoints.

AnyTrack connects your CRM (HubSpot, GoHighLevel, and others) to Meta Conversion API (CAPI) for CRM, so lifecycle events from your sales pipeline feed directly into Meta for campaign optimization. As an official Meta Business Partner, AnyTrack handles data formatting, identifier enrichment, and deduplication automatically.

Conversion API for CRM is one of three tracking methods AnyTrack orchestrates for Meta. To understand how it fits alongside the Meta Pixel and the standard Conversion API, see Meta Pixel vs CAPI vs CAPI for CRM.

Before you begin

  • You have admin access to Meta Business Manager and your ad account
  • You have admin access to your CRM (HubSpot or GoHighLevel)
  • You have an active AnyTrack account with a paid subscription
  • You have a Meta Dataset configured for CRM events in Events Manager

What This Integration Does

Without AnyTrack, Meta has no visibility into what happens after a lead submits an Instant Form. Your CRM tracks lifecycle changes (qualified, meeting booked, customer), but that data never reaches Meta.

With AnyTrack in place, the data flow works like this:

  1. A lead submits a Facebook or Instagram Instant Form.
  2. Meta sends the lead data to your CRM and to AnyTrack simultaneously.
  3. As your sales team qualifies leads and updates lifecycle stages, the CRM sends those updates to AnyTrack.
  4. AnyTrack matches the CRM update to the original lead, enriches it with Meta identifiers (fbc, fbp, external_id), and pushes the event to Meta via Conversion API for CRM.
  5. Meta uses these server-side funnel events to optimize ad delivery and build better audiences.
📘

Note

AnyTrack stores the original Meta identifiers captured at lead submission and appends them to every subsequent CRM event. This is what enables proper attribution even when the conversion happens days or weeks later.

Unified Conversion API for Web and CRM

AnyTrack runs Conversion API for Web and Conversion API for CRM in parallel, giving Meta a complete picture of the customer journey. This enables two campaign strategies:

  • Top-of-funnel optimization — Run Lead Ads campaigns optimized for downstream CRM events like Qualified Lead or Customer. AnyTrack routes the CRM event to Meta with the correct match keys so Meta learns which leads actually convert.
  • Bottom-of-funnel retargeting . Run retargeting campaigns where users return to your site and complete a purchase. AnyTrack combines first-party web events (via Conversion API for Web) with CRM lifecycle events (via Conversion API for CRM), so Meta optimizes based on the full journey.

📘

Note

You do not need to choose between Conversion API for Web and Conversion API for CRM. AnyTrack orchestrates both pipelines, handling event source categorization, deduplication, and identifier enrichment across all touchpoints.

Step-by-Step Integration

Step 1: Connect Meta in AnyTrack

  1. Log in to AnyTrack Dashboard.
  2. Go to Integrations and select Meta Ads.
  3. Authorize the connection using Meta Business Login and approve the relevant assets (Business Manager, ad account, Dataset).
  4. Connect the Facebook Page associated with your Lead Ads.
  5. Enable the Conversion API integration.

Step 2: Connect Your CRM

  1. In AnyTrack, go to Integrations and select your CRM (HubSpot or GoHighLevel).
  2. Approve permissions via the official CRM app connection.
  3. Once authentication completes, you will be redirected to the AnyTrack dashboard.

  1. Select the CRM lifecycle events you want to track and map them to AnyTrack event names.
⚠️

Warning

Event mapping follows a three-layer structure. First you map CRM events to AnyTrack events, then you map AnyTrack events to Meta Ads events. Both layers must be configured for data to flow correctly.

CRM Event (HubSpot example)AnyTrack EventMeta Ads Event
Contact CreatedCRM_Leadcrm_lead
Meeting BookedScheduleSchedule
Contact Sales QualifiedCRM_SQLcrm_sql
Deal createdDealCreatedDealCreated
Deal WonPurchasePurchase

Step 3: Map AnyTrack Events to Meta Conversion API for CRM

This step defines which sales funnel stages AnyTrack sends to Meta Conversion API for CRM.

  1. Return to the Meta Integration settings and scroll down to the Event Mapping section.
  2. The CRM events you configured in Step 2 now appear and can be mapped to Meta Conversion API events.
  3. Set the mapping based on your funnel stages.
  4. Save your settings.
📘

Note

AnyTrack automatically captures standard customer data from your CRM (email, phone, country, name) and maps it to Meta Conversion API event parameters. No manual parameter configuration is needed.

Step 4: Configure Your Sales Funnel in Meta Events Manager

This step tells Meta which sales funnel stages to optimize for.

Important

You must have admin access in Meta Business Manager to complete this configuration.

  1. Open Events Manager in Meta Business Suite.
  2. Go to Data Sources and select the Dataset you connected in AnyTrack.
  3. Click Configure Sales Funnel and then Continue.
  4. Add each CRM event as a funnel stage and save.
  5. Select the earliest positive lead stage you want Meta to optimize for, include any subsequent positive stages, and click Finish.

Choosing an earlier stage (like Interested) increases event volume for optimization. Choosing a later stage (like Customer) focuses on higher-quality leads but provides fewer signals.

Step 5: Validate Event Match Quality

  1. Open Meta Events Manager.
  2. Check Event Match Quality scores for incoming CRM events.
  3. Confirm that strong match keys are included: email, phone, city/zip, first name, and last name.
📘

Note

Event Match Quality reflects the customer data your CRM sends to AnyTrack. AnyTrack hashes and formats all identifiers automatically, but the data must exist in your CRM first. If you do not collect phone numbers or country for your leads, those fields cannot be included. See the EMQ Parameters reference for the full list of supported match keys.

Step 6: Test the Integration

  1. Submit a test lead via your Instant Form (or use the Meta Lead Ads Testing Tool).
  2. Confirm the lead appears in your CRM and in AnyTrack.
  3. Update the test lead lifecycle stage in your CRM (for example, change to Sales Qualified Lead).
  4. Check the AnyTrack Integration Log to verify the lifecycle event was received and queued for Meta Conversion API.
  5. After 10-20 minutes, verify the event appears in Meta Events Manager under your Dataset.

Practical Examples

HubSpot: Your sales team updates a lead to Qualified. AnyTrack forwards the update to Meta as a CompleteRegistration event, so Meta knows which Lead Ad produced a real opportunity.

GoHighLevel: When a meeting is booked in GoHighLevel, the CRM sends this event to AnyTrack. AnyTrack syncs it to Meta as a Schedule event, giving Meta a mid-funnel optimization signal.

📘

Note

Apply lead scoring in your CRM before syncing events to Meta. AnyTrack handles deduplication automatically, so sending the same lifecycle update multiple times will not create duplicate events in Meta.

Troubleshooting

AnyTrack can only send conversions to Meta Conversion API for CRM after the initial lead has been captured in AnyTrack. If the initial lead submission was not tracked, subsequent CRM events cannot be attributed.

Permission issues . The user who connects AnyTrack to Meta must have admin access to the Business Manager, ad accounts, Pages, and Datasets. Without full admin permissions, lead data will not sync correctly.

No events in Meta Events Manager . Verify that Meta is properly connected in AnyTrack, then check the Integration Log to confirm CRM events are being received. If events show in AnyTrack but not in Meta, check the Meta Ads integration logs for error responses.

Low Event Match Quality . EMQ depends on the customer data in your CRM. AnyTrack maps all standard fields automatically, but if your CRM records are missing phone numbers, country, or zip codes, those parameters cannot be sent to Meta. Adding phone number to your lead forms typically improves match rates by 15-20%. See Event Match Quality for a detailed breakdown.

Related Resources


FAQ

FAQ was last reviewed on 2026-03-23

No. Conversion API for CRM requires that AnyTrack captures the initial lead submission from a Meta Lead Ad. This is what provides the Meta identifiers (fbc, fbp) that link CRM events back to the original ad interaction.
AnyTrack sends CRM events to Meta within seconds of receiving them. However, Meta processes events in batches, so allow 10-20 minutes before events appear in Events Manager. Event Match Quality scores may take longer to stabilize.
AnyTrack sends whatever customer data your CRM provides. Missing fields like phone number reduce your Event Match Quality score but do not prevent events from being sent. Adding phone number to your lead forms is the single most effective way to improve match rates.
Yes. AnyTrack orchestrates both pipelines in parallel. Web events and CRM events are routed through separate Conversion API channels with automatic deduplication, so Meta receives a complete view of the customer journey without duplicate events.
AnyTrack currently supports HubSpot and GoHighLevel as native CRM integrations for Conversion API for CRM. See the HubSpot and GoHighLevel integration guides for platform-specific setup instructions.