Troubleshooting delivery and deduplication

Most delivery issues come from five places: missing consent, incomplete payloads, blocked connector requests, unstable event IDs, or destination credentials. Start there before escalating.

Missing or delayed delivery

• Confirm consent was granted before the server-side event fired
• Check destination credentials and platform configuration
• Review required order, customer, value, and currency fields
• Confirm the connector endpoint is not blocked by a firewall or Cloudflare rule
• Check retry queues for plugin or module events that could not be sent immediately

Duplicate reporting

• Confirm the same purchase uses one stable event ID
• Review how browser and server events are paired
• Remove extra purchase triggers introduced by theme or app changes
• Check whether the destination pixel and server event share the exact same event_id

Weak signal quality

• Confirm email and phone are captured and hashed correctly
• Confirm fbc, fbp, gclid, ttclid, and msclkid are persisted where available
• Confirm IP and user agent are passed to server-side destinations where allowed
• Confirm currency and value are not defaulting to USD when the store uses another currency

When to escalate

Open support when delivery health remains degraded after the initial validation pass or when the issue affects live revenue reporting.