Skip to main content
Fix the first failing stage. Sending more test events does not help when the event never matches a rule or the destination asset is wrong.

​
1. Was the event collected?

Open Events and find the exact source event. Check its name, source, timestamp, workspace, value, currency, and identifiers. If it is missing, stop here and fix collection or the revenue source.

​
2. Did a rule match?

Open Conversions and confirm the rule is enabled. Compare its event name and every filter with the collected event. Check whether the rule expects web, server, app, or a specific source. If no delivery attempt exists, the rule did not match or was disabled at processing time.

​
3. Is the destination correct?

  • Meta, Google, and TikTok use the primary account selected in Sources.
  • Snapchat uses the Pixel ID or App ID saved on the rule.
  • OpenAI Ads uses the connected Pixel ID and key.
Confirm the destination belongs to the campaigns you intend to optimize.

​
4. Read the delivery result

An error response usually identifies invalid credentials, missing required fields, an unsupported destination event, or an invalid asset. Correct that field, then send one new controlled event. An accepted response means the platform received the request. The platform can still deduplicate, delay, reject attribution, or omit it from a campaign report according to its own rules.

​
5. Check match quality inputs

Preserve reliable customer identifiers, click IDs, event time, transaction or event ID, value, currency, IP address, and user agent when applicable and permitted. Missing match inputs may reduce attribution even when delivery succeeds. When escalating, include the Datalyr event ID, rule, destination, delivery timestamp, status, and sanitized error. Never include full API credentials.