What to do
Open Meta Test Events, add the temporary test code if your integration requires it, submit the published form or complete the booking, inspect the event details, and remove the test code before normal traffic continues.
Prepare one controlled test
Use a new email address or phone number so contact deduplication and workflow re-entry do not confuse the result. Open the workflow execution view and Meta Test Events side by side.
Keep the test focused on one event. Testing Lead, Schedule, Purchase, and three pipeline stages at once turns troubleshooting into archaeology.
- One published page
- One fresh test contact
- One selected event
- Meta Test Events open
- Workflow history ready
Run the real visitor path
Visit the live page with the test campaign parameters you need, then submit the form or finish the booking. Confirm the workflow starts from the intended trigger.
HighLevel specifically warns that the workflow test button is not the correct way to validate the Facebook CAPI workflow trigger. A real submission carries the real contact and attribution context.
- Do not use only the workflow test button.
- Do not reuse an old contact that cannot re-enter.
- Do not refresh a confirmation page repeatedly.
- Do not leave several test integrations enabled.
Inspect more than the green received status
Open the event details and review event name, source, time, event ID, user data, browser identifiers, and source URL. A received event can still be incomplete or duplicated.
After testing, remove the temporary test-event code. Leaving it in production can keep normal events in the test view instead of the reporting flow you expect.
- Correct event name and dataset
- Server source present
- Expected identity fields
- FBC and FBP when available
- Correct event source URL
- Matching event ID when Pixel also fires
GoHighLevel Meta CAPI check
01Use a new test contact
02Submit the published form or booking
03Confirm the workflow execution
04Inspect the full event details
05Remove the test code after validation
Common questions about this setup
Why does Meta Test Events show nothing?+
Check whether the workflow action executed, whether the correct dataset is selected, and whether the test code was added in the correct place.
Why should I avoid the workflow test button?+
It may not reproduce the real trigger and visitor attribution data used by the live form or booking.
Can I test without a Meta ad click?+
Yes, but you should not expect real ad-click identifiers from a direct visit. Test delivery first, then test attribution with a controlled ad-click path.
When do I remove the test code?+
Immediately after the setup is validated and before relying on normal production reporting.
Official references
Use these official references when checking the current Meta setup and account screens.