Troubleshooting

The chain

A conversion crosses five stages. Fix the earliest broken one, because a later stage can’t repair an earlier one.

Stage	It works when	It fails as
1. Collection	The row exists in Events	No events
2. Revenue capture	The purchase row exists in Events	Missing revenue
3. Attribution	The conversion carries `utm_` or a click ID	Missing attribution
4. Rule match	A row exists in Conversions	Conversion not delivered
5. Delivery	Conversions shows a success status	Conversion not delivered

Two problems sit outside the chain.

Symptom	Page
A source card reads `action required`, `error`, or `not connected`	Integration errors
Both systems have data, and the totals disagree	Different numbers

Find the first broken stage

Question	Answer is no	Answer is yes
Does any event reach Live?	Go to stage 1	Continue
Does the purchase reach Events?	Go to stage 2	Continue
Does the row carry `utm_source` or a click ID?	Go to stage 3	Continue
Does a row exist in Conversions?	Go to stage 4	Continue
Does that row show a success status?	Go to stage 5	The chain works

Test with one record

Do not reconnect a source, rotate a key, or reinstall an SDK before you find the failing stage. Reconnecting Meta, Google, or TikTok deletes that source’s synced platform data.

Change one thing per test, and record these six values before you start.

Field	Example
Workspace public ID	`ws_abc123`
Environment	production
Event name or transaction ID	`purchase`, `pi_3Ox…`
Source	Stripe
Timestamp with timezone	`2026-07-25 14:03 UTC`
Expected result	A row in Conversions with a success status

Get started

Installation

Revenue

Using Datalyr

Advanced

Integrations

Account & billing

Troubleshooting

The chain

Find the first broken stage

Test with one record

What to send support

​The chain

​Find the first broken stage

​Test with one record

​What to send support

The chain

Find the first broken stage

Test with one record

What to send support