Use separate measurements for public interest, verified setup, queue acceptance and later delivery. This guide keeps the funnel useful without sending secrets or customer content to analytics.
Name each stage of the integration funnel
Track documentation views, setup actions, verified events, validation results and later delivery observations as separate stages. A page visit cannot prove that a customer configured an account or that a message reached a destination.
Use account setup and delivery records for activation evidence; use public analytics for bounded, consented interaction signals.
Keep event payloads bounded
Send only allowlisted event names, the query-free page path and small destination values. Do not send email addresses, API keys, message bodies, payment data, reset tokens, URL fragments or arbitrary form fields.
Public pages and the dashboard use the same consent choice. If consent is absent or denied, the analytics tag and product funnel events remain off.
Read queue and delivery separately
A successful API response can mean queued. Inspect the returned message ID and later delivery logs or signed webhooks for provider and destination outcomes. A missing observation remains unavailable rather than a zero.
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.