What to do
Open Meta Events Manager and its Test Events view, then complete the real conversion on the published website. Confirm the server event appears with the correct name, time, source URL, event ID, and matching fields. When the Pixel also sends the event, confirm the browser and server events are connected rather than counted twice.
Run a real conversion test
Use the public page, a fresh contact, and the real form or calendar. Workflow test buttons and editor previews may skip the attribution values attached to a normal visitor.
For GoHighLevel, confirm the contact entered the intended workflow and that the CAPI action or server request ran after the conversion.
- Use the published URL
- Open a clean browser session
- Use a new email or phone
- Complete the real form or booking
- Check the workflow execution
Inspect the event Meta received
Confirm the event name and source. Then inspect event time, event ID, source URL, action source, and the matching information that was available.
An event appearing in Test Events proves delivery. It does not automatically prove good attribution, strong matching, or correct deduplication.
- Correct dataset
- Correct event name
- Server event received
- Correct source URL
- Expected matching fields
- Shared event ID when the Pixel also fires
Troubleshoot based on where the event stopped
If the website did not send a request, inspect the installation and form selector. If the server received the request but Meta did not, inspect the access token, dataset ID, event payload, and API response.
If Meta received the event but reporting is weak, inspect click identifiers, browser identifiers, identity data, event source, and whether the event occurred inside the attribution window.
- No browser request: installation problem
- Server error: endpoint or authentication problem
- No event in Meta: dataset, token, or payload problem
- Event received with weak data: capture or mapping problem
- Two conversions: deduplication problem
Meta CAPI test checklist
01Open Meta Test Events
02Use the published conversion page
03Complete a real form or booking
04Confirm the server event appears
05Inspect event name, source, ID, and matching fields
06Confirm browser and server deduplication
07Check Diagnostics after launch
Common questions about this setup
How to test Meta CAPI?+
Complete a real conversion on the published website while Meta Test Events is open, then inspect the server event and its details.
Why does my workflow test not show a useful Meta event?+
A workflow test may bypass the real website visit, form attribution, browser identifiers, or normal trigger path.
What does a successful Meta CAPI test prove?+
It proves that Meta received the server event. You must still check event quality, source data, deduplication, and production diagnostics.
Why do I see two Lead events?+
The Pixel and server event may be using different event IDs, or several tools may be reporting the same conversion.
Official references
Use these official references when checking the current Meta setup and account screens.