GHL’s Meta CAPI Integration Now Supports Purchase Tracking

Let’s break down what’s actually changed inside GoHighLevel’s workflows.

Previously, when using the CAPI (Conversions API) action to send a Lead Event to Meta—and setting that event to the “Purchase” stage—you had no way to pass a purchase value or currency. Those fields didn’t exist in the interface. And without them? Meta often rejected the event or marked it incomplete, throwing off your whole tracking system.

Now that’s fixed. This improvement gives your Meta CAPI Integration the data it needs to fire clean, validated purchase events every time.

Here’s what’s new:

• When you choose Event Type: Lead Event and set Stage Name: Purchase, you’ll now see two additional fields:
  • Value: You can use a static number (like 99.99) or insert a custom field (like {{opportunity.value}}).
  • Currency: This is a dropdown with preset options (just like in Funnel Events), defaulting to USD.

These two fields only appear when the stage is set to Purchase—which keeps your workflow clean and uncluttered.

And the backend logic? GHL made it airtight:

• If Value and Currency are set, they’re passed correctly to Meta.
• If the stage isn’t “Purchase,” those fields are ignored—even if they’re filled in.

It’s all designed to match Meta’s requirements exactly and give you bulletproof tracking, no extra effort needed.

If you’ve been running Facebook or Instagram ads and feeding those leads into GoHighLevel workflows, you know the headache when Meta throws back errors for missing event parameters. It’s not just annoying—it screws with your campaign reporting, ROI tracking, and client results.

This update is a fix to that pain. It directly improves your Meta CAPI Integration by ensuring every Purchase event meets Meta’s strict tracking requirements.

Here’s how it helps:

• Stops Tracking Failures: No more rejected “Purchase” events in Meta’s Events Manager. You’re sending exactly what Meta needs—value and currency—every time.
• Improves Ad Attribution: By passing the right purchase data, Meta can more accurately tie conversions to your ad campaigns. That means better optimization and reporting.
• Saves You Time: No more back-and-forth trying to debug CAPI errors or explain to clients why their events didn’t track.
• Works for All Users: Whether you’re running ads through native GHL integration or via the Ad Manager option inside the CAPI action, this update applies.

It brings Lead Event Purchases in line with your Funnel Events setup—tightening the flow of your Meta CAPI Integration across the board.

Best Use Cases:

• Agencies running CAPI automations for multiple clients
• Local businesses using workflows to track sales from ad campaigns
• Anyone using dynamic values (like from opportunities or form data) to personalize purchase tracking

If your Lead Event says “Purchase,” this update ensures Meta knows exactly what was bought—and how much it was worth.

Adding this update to your workflows is easy—but only if you know where to look. This section shows you exactly how to find, enable, and configure the new Value and Currency fields inside your CAPI action. These steps ensure your workflow is fully aligned with the latest Meta CAPI Integration standards.

Follow these steps to make sure your Lead Purchase events send the correct data to Meta:

1.1 Click on the Automation menu item.

• This takes you to the Workflows section where you’ll manage automations.

1.2 Open an existing Workflow or create a new one.

• Make sure the workflow includes Meta conversion tracking.

2.1 Click Add Trigger at the top of your workflow.

• This defines when the automation should start.

2.2 In the search bar, type Contact Changed.

• Select the Contact Changed trigger from the list.

2.3 Click Save Trigger to apply it to the workflow.

3.1 Add a new action and search for Conversion API.

• Facebook Conversion API will appear in the result. Select it.

3.2 Under Event Type, select Lead Event.

• This is where the update kicks in. Selecting the correct event type is essential for a functional Meta CAPI Integration.

3.3 Enter your Access Token from Meta.

• This is required to authorize the CAPI event with Meta.
• You can find it in your Meta Events Manager under Settings > Access Tokens.

3.4 Enter your Pixel ID.

• This tells Meta which Pixel should receive the event data.
• Pixel IDs are also located in your Meta Events Manager dashboard.

3.5 Set the Stage Name dropdown to Purchase.

• Once selected, you’ll see two new required fields appear.

3.6 In the Value field, enter either:

• A static number (e.g. 149.99)
• Or a dynamic custom field (e.g. {{opportunity.value}})

3.7 In the Currency field, choose your preferred currency from the dropdown.

• Default is USD, but this matches the options from Funnel Events for consistency. Both fields are critical for complete and compliant Meta CAPI Integration.

3.8 Save the Action

3.9 Click Save in your workflow editor.

• Always save after modifying a CAPI action.

That’s it. No custom code. No workarounds. Just a clean fix that finally makes Lead Event purchases trackable the right way.

Getting the Value and Currency fields into your workflow is the first step. But using them smartly? That’s how you squeeze every drop of value from this update. Solid execution is what turns a basic setup into a high-performing Meta CAPI Integration.

Here’s how to make it work even better:

If you’re pulling lead data from form submissions or pipeline values, use custom fields like {{opportunity.value}}. This automates the process and ensures accurate numbers without manual entry. Dynamic inputs make your Meta CAPI Integration scalable and precise at the same time.

Make sure the selected currency matches what your Meta ad account is set to. Mismatches can cause data issues or lead to events being misclassified in Meta’s dashboard.

These fields only show up when the Stage is “Purchase.” If you try to use them on other stages, GHL ignores them—which keeps your automations clean and error-free.

To stay organized, include “Purchase” in the event name when setting up the CAPI action. This helps when scanning logs or debugging event reports.

If you’re using custom values, make sure they’re populated before triggering the event. Blank fields = failed events. A little QA goes a long way toward keeping your Meta CAPI Integration error-free and consistent.

By following these tips, you’ll keep your Meta tracking crisp, consistent, and conversion-accurate across the board.

If you’re running paid traffic, every lost or misfired conversion event is a missed opportunity—and a dent in your ROI. This update ensures that GoHighLevel users can finally close the loop between what’s happening in your workflows and what’s reported in Meta.

Here’s why it matters to your bottom line:

Now, when someone becomes a paying customer through a workflow-triggered Lead Event, Meta gets the full picture. This means your ad sets are properly credited—and your data-driven optimization gets a major upgrade.

If you’re an agency, you can now confidently report “Purchase” conversions coming from Lead Events. That’s a huge win when you’re justifying ad budgets or pitching renewals.

Meta thrives on clean data. With Value and Currency included, Meta’s algorithm has what it needs to optimize your campaigns toward real purchases—not just leads.

Meta often requires a monetary value for Purchase events. Before this update, Lead Event workflows didn’t support that—leading to delivery errors. Now, you’re aligned with Meta’s standards by default.In short: more reliable results, better decisions, and one less technical fire to put out during launch week.

Meta ad tracking just got a whole lot smoother inside GoHighLevel. With the new Value and Currency fields now available in Lead Event Purchases, you can finally eliminate the data gap that’s been messing with your reporting and ROI. This upgrade closes a key loop in your Meta CAPI Integration, making your lead-to-purchase journey airtight.

Here’s what this means in plain English:

You tell Meta someone made a purchase → Meta gets the full story → Meta optimizes your campaigns better → You get better results. Simple as that.

If you’re using workflows with CAPI actions and haven’t updated them yet, now’s the time. Set the event to “Purchase,” fill in the new fields, and let GHL handle the heavy lifting.

And if you’ve been frustrated by incomplete tracking or cryptic Meta errors in the past? This fix is for you.

Check out your workflows, make the update, and get your conversion tracking dialed in.Have you tried out the Lead Purchase tracking update yet? Let us know how it’s working for you—or if you’ve run into any surprises.