What to do
Confirm the correct dataset, choose one owner for each event, capture attribution before the conversion, share event IDs between matching browser and server events, test the real visitor path, and monitor diagnostics after launch.
Account and event ownership
Each client should use the Meta dataset and access credentials they control. The workflow, script, and endpoint should clearly state which client and event they serve.
Assign one system to own each server event. A second integration should not quietly send the same Lead because someone forgot the first one existed.
- Correct client dataset
- Correct access token or partner connection
- One named owner for Lead
- One named owner for Schedule
- No shared credentials in public page code
Landing-page and contact capture
Capture the original page and campaign information before redirects or embedded forms can remove it. Then verify that the values reach the GoHighLevel contact and the final event.
Do not confuse fields that exist in the browser with fields that actually arrived in the workflow.
- Landing page and referrer
- FBCLID, FBC, and FBP when available
- UTM source, campaign, ad set, and ad
- User agent and source URL
- Normalized email and phone
Event naming, timing, and deduplication
Fire each event at the action it describes. Lead belongs on the meaningful form submission. Schedule belongs after the appointment is created. Qualified events belong after a documented rule is met.
When the Pixel and CAPI both report the same action, keep the event name and event ID identical.
- Correct event name
- Correct trigger timing
- Unique ID for each conversion
- Shared ID for matching browser and server copies
- Retry uses the original ID
Testing and monitoring
Test the published page with a new contact. Confirm the workflow execution and inspect the full event in Meta Test Events. After launch, review Diagnostics and event-source counts rather than assuming the first successful test settles everything forever.
Remove test codes, document the final setup, and repeat the check after major funnel or workflow changes.
- Live form or booking test
- Workflow execution confirmed
- Meta event details inspected
- Test code removed
- Diagnostics reviewed after production traffic
GoHighLevel Meta CAPI check
01Client owns the correct dataset
02Each event has one server-side owner
03The exact form or calendar is selected
04Attribution is captured before conversion
05Email and phone are normalized
06Lead and Schedule fire at the correct moment
07Browser and server copies share an event ID
08Retries reuse the same event ID
09Embedded forms are tested in their real page context
10A new contact can enter the workflow
11Meta Test Events shows the expected details
12No overlapping integration sends an extra event
13Temporary test codes are removed
14The setup is documented
15Diagnostics are reviewed after launch
Common questions about this setup
What result should this checklist produce?+
It follows the same launch method used across more than 25 client implementations that reached at least 9.3 Meta Event Match Quality.
How often should I repeat the checklist?+
After major funnel, domain, form, calendar, workflow, dataset, or tracking changes, and during regular account audits.
What should I check first when results suddenly change?+
Look for recent page or workflow changes, connection changes, duplicate integrations, and missing attribution fields.
Should every event have browser and server copies?+
No. Use both where they add value. CRM-only lower-funnel events may be server-only and therefore do not need browser deduplication.
Official references
Use these official references when checking the current Meta setup and account screens.