Use real browser flows for DebugView checks, then keep acquisition links consistent and privacy-safe with one documented UTM contract.
Verify each funnel event with a real browser flow
Use a fresh consented browser session and confirm the event name in GA4 DebugView after the interaction. Documentation views, API reference views, pricing views and contact actions are public signals; signup and API-key creation are account actions and should be verified only in the authenticated dashboard.
Do not send email addresses, API keys, message bodies or customer identifiers as event parameters. The production contract sends only an event name, a canonical page path and small allowlisted destinations. The branded 404 signal is named `page_404_view` because GA4 event names must start with a letter. Use that valid name in DebugView and reporting. Every public code sample also has a Copy control that records `copy_code` only when a visitor clicks it. The same consent gate applies on the branded 404 document. The public docs now expose a direct integrations link for a real browser verification flow. The 404 retry keeps the same consent gate and sends no additional page parameters.
Use one UTM contract for every channel
Set utm_source to ghl, facebook, instagram, youtube or pinterest. Set utm_medium to crm, social, paid_social, video or paid_video. Set utm_campaign to emailerapi-{initiative}-{yyyyq#}, and use utm_content for the placement or creative. Use utm_term only for a paid keyword.
Keep values lowercase kebab case and free of personal data. The site preserves only these five keys and caps every value at 120 characters before it reaches GA4.
| Channel | utm_source | utm_medium | utm_content examples |
|---|---|---|---|
| GoHighLevel | ghl | crm | workflow-email; pipeline-link |
| social or paid_social | page-post; retargeting-1 | ||
| social or paid_social | bio-link; reel-demo | ||
| YouTube | youtube | video or paid_video | description-link; pre-roll-1 |
| social or paid_social | pin-guide; promoted-pin-1 |
Search discovery needs a live feedback loop
The sitemap is submitted to the verified Search Console property and changed URLs are sent through IndexNow. Request indexing for representative pages after a publication, then review coverage, Core Web Vitals and query data as Google processes the site.
Search Console does not provide instant ranking or field-performance data for a new page. Treat missing observations as pending, not as zero, and revise titles, links and content only when the accumulated query and performance data supports the change.
Continue with a related guide
Sources and next steps
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.