Skip to main content
Website analytics and delivery to another tool are separate. A received website event does not prove that Meta, Google, or another destination accepted it.

​
Configure the destination

  1. Open Websites, choose the site, then open Destinations.
  2. Read the controls for the specific provider. A website owner or editor can manage supported connections; viewers have read-only access.
  3. Select the intended account and destination, or enter the credentials requested by that supported flow. Check its IDs and any event mappings.
  4. Save in the offered test mode before creating your test event.
  5. Follow the provider-specific test steps and read the returned result. A validation result and a delivered event mean different things; use the checks below for that provider.
  6. Enable the supported live-delivery control only after a successful test, then confirm the production environment and monitoring state.

​
Test the Meta destination

For Meta, use the connected account or supported manual-token setup. Supply the correct Pixel or dataset and its Test event code, then choose Save in test mode. Use a test page with the website script set to the test environment. Grant analytics and marketing consent through your website’s consent manager. The test requires a real Meta Pixel cookie or Facebook ad click identifier; anonymous analytics identifiers cannot replace them. Perform a mapped action once, then choose Check test delivery. This checks events already received; it does not generate a visit. Confirm the accepted event in Meta Events Manager’s Test events view. After the product records a successful test, Enable live delivery becomes available.

​
Match the event honestly

Map a confirmed successful lead submission to Lead. A booking-button click should not be described as a confirmed booking. This Meta destination does not forward purchases or refunds; use the supported commerce/outcome workflow for those sources.

​
Check other providers

Google Analytics 4 requires a Measurement ID and a Measurement Protocol API secret. Its debug test validates the eligible event and configuration; the validation event does not enter GA4 reports. Do not wait for a test conversion to appear in those reports as proof of setup. TikTok Events API requires a Pixel code, access token, and Test Event Code. Inspect the result and the destination’s isolated test events for the eligible action before enabling live delivery. Google Ads conversions requires a connected Google account with the requested Data Manager access, the conversion action ID, its operating customer ID, and currency. A manager login customer ID is optional. The test also needs a Google click identifier. Validation creates no conversion; a successful check is not a recorded result in Google Ads.
Google Ads live forwarding can remain unavailable after validation or saving Live mode. If the status says live delivery is awaiting availability, contact support and confirm it is enabled before relying on conversion delivery. A validation success does not establish that production conversions were sent.
For these providers, use Save in test mode, collect one eligible action, then choose Check test delivery. Changing the configuration requires a new successful check before Enable live delivery can be used. After enabling it, verify actual production deliveries separately from test validation.

​
If events are skipped or rejected

Check consent, identifiers, environment, event mapping, destination IDs, and provider permissions. A test event does not later become a live event. If configuration changes, repeat the relevant test rather than relying on an earlier success. Pause delivery stops destination delivery without proving that website analytics stopped. Disconnect removes this destination’s saved connection details and history as explained by its confirmation; inspect dependent work before choosing it. Next: Verify website events or contact support.