A GoHighLevel contact becoming a qualified lead or customer can be a useful advertising signal. Sending it requires more than a workflow trigger: the event needs a defined stage, matching data, a timestamp, and a rule that prevents retries from counting the same outcome twice.
Why ad platforms optimize for the wrong event
The booked call, qualified lead, and won deal happen later inside the CRM. Unless those events are sent through a supported integration, the ad platform’s reporting may only include the form fill.
The reporting side of that gap is covered in GoHighLevel attribution reporting. This post covers the send side. If the idea is new, start with the basics of offline conversions and how they reach ad platforms.
Capture the match keys when the lead arrives
Offline conversions only match when the upload carries something the platform can tie back to a click or a signed-in user. If the lead is saved without those values, no later workflow can recover them. Add hidden fields to the GoHighLevel form, calendar, or landing page, and map them to contact custom fields so they persist on the record:
- Google click IDs: gclid, gbraid, and wbraid, stored separately so each can be sent for the right upload.
- Meta click and cookie values: fbclid, plus the _fbc and _fbp cookie values read from the page at form submit.
- Customer identifiers: email and phone, normalized and hashed before any value leaves your systems.
- Campaign context: UTMs and the landing page, kept for reporting. A clean UTM setup is covered in dynamic UTM parameters.
- Stage timestamps and the GoHighLevel opportunity ID, used later as the deduplication key.
If the form submits on a different domain or inside an iframe, the cookie values may not be readable from the page that gets the submission. Test that path on purpose. The GoHighLevel and GA4 mismatch guide covers why iframe and separate-domain setups lose tracking, and GoHighLevel server-side tracking covers sending the browser events from your own tracking domain.
Trigger on the stages that matter
A workflow can trigger when an opportunity status or pipeline stage changes, then filter for the Won stage. If you also send booked or qualified stages, define separate conversion actions so each event has one meaning.
GoHighLevel workflow actions and conversion features change over time, so confirm the current options before planning a custom endpoint. If no native action fits, a webhook can post to an endpoint or integration you control, which can then call the platform API.

Map each field to the platform that needs it
The same contact record feeds two different upload formats. The table shows where each GoHighLevel value goes. Field names follow each platform’s upload documentation, so confirm them against the current reference before you build.
| GoHighLevel field | Google Ads upload field | Meta CAPI field |
|---|---|---|
| gclid, gbraid, wbraid | Click identifier on the conversion upload (match to the click) | Not used by Meta; keep for Google only |
| _fbc cookie value (or fbclid, formatted the way Meta specifies for fbc) | Not used by Google | user_data.fbc |
| _fbp cookie value | Not used by Google | user_data.fbp |
| Email (hashed) | User-provided identifier, for enhanced conversions for leads | user_data.em |
| Phone (hashed) | User-provided identifier, for enhanced conversions for leads | user_data.ph |
| Won stage timestamp and timezone | Conversion date and time, with timezone offset | event_time |
| Deal value and currency | Conversion value and currency code | custom_data.value and custom_data.currency |
| Unique outcome ID | order_id (unique per conversion action) | event_id (follow current event deduplication rules) |
| Pipeline stage name | Conversion action name (define one meaning per action) | event_name from the currently supported event set |
Google Ads: upload the outcome against the click
Google Ads supports importing outcomes through a configured conversion action and data source. Depending on the import method, supported match fields can include click identifiers or user-provided data.
The upload also requires conversion details such as time, and may use value and currency. Check the current limits for the configured import method in Google’s offline conversion import guide before scheduling older deals.
If your sender calls the Google Ads API directly, check it against Google’s June 15, 2026 change: developer tokens that sent no offline conversion uploads between December 17, 2025 and June 15, 2026 are blocked from those uploads in the Google Ads API and need to use the Data Manager API instead.
Meta: send a system-generated CRM event
Meta’s Conversions API uses action_source to describe where an event originated. The CRM workflow and its event mapping should follow the current Meta documentation.
Event payloads can include event name, time, user data, and custom data fields where supported. Normalize and hash identifiers as required, and include browser matching values only when captured and permitted.
Meta’s CRM integration for conversion leads optimization focuses on lead-stage events. Confirm the currently supported event names and required fields in Meta’s Conversions API for CRM documentation.
Send value, and never count a deal twice
Include a deal value when the conversion definition and platform support it. Keep each outcome’s meaning clear, and avoid sending multiple stages into one conversion action if the platform would count each send separately.
Use a stable outcome identifier where the integration supports one. Google documents order_id as a unique ID per conversion action; for Meta, follow its current event deduplication requirements rather than assuming the same field or rule applies.
Privacy, consent, and regulated businesses
Send only fields the platform supports and your organization is permitted to use. Apply the relevant consent and privacy rules, and avoid sending appointment details, notes, or free-text content as event parameters.
Healthcare and other regulated businesses need review of what leaves the CRM. See healthcare marketing tracking without PHI for a public-surface discussion.
QA with one won deal before you turn it on
- Submit a test lead with a known click ID, move it through the stages, and mark one deal Won.
- Confirm the upload appears in Google Ads conversion diagnostics or upload status, with the expected value and time.
- Confirm the Meta event appears in Events Manager with the expected event name and value.
- Watch the match rate for a week, and investigate any drop against the capture form.
- Keep a send log with the opportunity ID, platform, event name, value, timestamp, and response status for every event.
Where Maven fits
Maven’s tracking audit checks the website side: broken, degraded and stalled pixels and events, and tags with no trigger, in each client’s GTM container, with daily health checks after. Start with dynamic UTM parameters for campaign context.
Want it done for you? MetricMaven can review capture, stage mapping, the send path, and the send log, then compare CRM outcomes with platform records.
Part of: Offline conversions
Also in By CRM: HubSpot offline conversions: how to send lifecycle stages and closed-won deals to Google Ads and Meta
Frequently asked questions
How do I send GoHighLevel won deals to Google Ads?
Capture the gclid, gbraid, or wbraid when the lead arrives and store it on the GoHighLevel contact. When the opportunity reaches Won, upload an offline conversion to a Google Ads conversion action that carries that click ID, the conversion time with its timezone, the deal value, and the currency. Check Google’s current import requirements before you build the sender.
Does GoHighLevel send conversions to Meta automatically?
Do not assume it does. Confirm which workflow actions and integrations your GoHighLevel account offers today, since they change over time. If none covers the stages you need, a custom endpoint can send system-generated events to the Meta Conversions API using hashed identifiers and the fbc and fbp values captured at lead time.
Why do my offline conversion uploads show no matches?
Possible causes include a missing match identifier, inconsistent normalization, an unsupported field, or an outcome outside the platform’s current import limits. Read each platform’s diagnostics and verify capture before changing the sender.
Can Maven help with GoHighLevel offline conversions?
Maven helps with the website side. Its tracking audit checks each client’s Google Tag Manager for broken, degraded and stalled pixels and events, and tracking health checks run daily, with alerts when a pixel, event or tag stops working. Container changes go live only after you approve them.
