What to do
Submit the real form or complete the real booking, confirm the workflow entered, inspect the Meta CAPI action, and then check Meta Test Events. Do not rely on GoHighLevel's workflow test button for this test because it may not reproduce the attribution data attached to a real visitor.
1. Confirm the real trigger fired
Start in the workflow execution history. Confirm that the contact entered through the exact form, calendar, survey, pipeline stage, or Facebook lead-form trigger you intended.
A manual workflow test proves that actions can run. It does not prove that the original Meta click information, browser identifiers, or page context were captured on a real submission.
- Submit the live form from the published page.
- Use a new test contact so an old workflow state does not hide the result.
- Check workflow filters, re-entry settings, and stop conditions.
- Confirm the contact reached the Meta Conversions API action.
2. Check the Meta action and dataset
Open the Meta Conversions API action and verify the connected Facebook account, dataset, event name, and any required field mappings. A workflow may be healthy while the action points to the wrong client dataset.
Use one clear event name for the conversion. A form submission is usually Lead. A completed booking is usually Schedule. Do not send several event names for the same action unless each represents a real, separate stage.
- Correct Facebook connection and client dataset
- Correct event name
- Email and phone mapped from the contact
- FBCLID, FBC, and FBP included when available
- Event source URL and user agent preserved when your setup supports them
3. Decide whether the failure is in GHL or Meta
Open Meta Events Manager and use Test Events. If no server event appears, inspect the GoHighLevel action and its execution log. If the event appears but attribution or match quality is weak, the delivery worked and the missing information is the real problem.
That distinction matters. Rebuilding the workflow will not restore a click ID that disappeared before the contact was created.
- No event in Meta: check action execution and dataset connection.
- Event received with weak details: check captured fields and mappings.
- Duplicate event: check Pixel and CAPI event IDs.
- Wrong event name: check workflow branches and overlapping actions.
GoHighLevel Meta CAPI check
01Run a real submission, not only a workflow test
02Confirm the contact entered the correct workflow
03Confirm the CAPI action executed successfully
04Verify the selected dataset and event name
05Inspect Meta Test Events before changing the setup
Common questions about this setup
Why does the workflow test pass but Meta receives nothing from the live form?+
The test may bypass the real page visit, attribution fields, or trigger conditions. Test with the published page and a new contact.
Can a GoHighLevel CAPI event be received without attribution?+
Yes. Delivery only proves that Meta received an event. Attribution depends on the available click, browser, identity, and source information.
Should I reconnect Facebook immediately?+
Only after confirming the workflow action is failing because of the connection. Reconnecting does not fix missing page data or incorrect field mapping.
Where should I look first?+
Workflow execution history, then the Meta action, then Meta Test Events. That order shows where the event stopped.
Official references
Use these official references when checking the current Meta setup and account screens.