Workflow
Find the broken link before changing the budget.
Investigate tracking, identity and conversion delivery health in DATALYR when marketing data changes unexpectedly. Separate capture problems from revenue-source issues and downstream delivery failures.
Compare plans and usage
A sudden performance drop may be a measurement problem.
A changed checkout, expired connection or missing event can look like a campaign decline. Tracking health investigation starts by locating which part of the measurement chain changed. DATALYR gives teams connected sources, event evidence and delivery context to work through the problem systematically instead of repeatedly reinstalling everything or assuming the ad platform is wrong.
In DATALYR
Conversion tracking health monitoring
Locate the failing stage
Check whether the expected event was captured, linked to a customer and delivered where intended. Each stage has different causes and requires a different corrective action.
Check source freshness
Review the integration state and timing of available data. A delayed source can explain an apparent gap without implying that the underlying business activity stopped.
Verify the repair
After a change, follow a known event through the same path. A green connection alone is not enough if the transaction still fails to appear in the expected report.
The workflow
From setup to a useful answer.
Record the symptom precisely
Write down the first affected time, platform and event type. Compare with recent site, checkout or credential changes to keep the investigation bounded.
Trace a known event
Inspect source receipt, identity association, rule selection and destination evidence as applicable. Stop at the first missing or inconsistent stage and investigate there.
Repeat the end-to-end check
After correcting the cause, send a controlled test and reconcile the result. Document what changed so a later recurrence can be diagnosed more quickly.
Verify the result
Know what good looks like.
- The first affected time and scope are recorded.
- A known event can be followed through each relevant stage.
- The repaired outcome appears in the expected destination and report.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Does a connected integration prove tracking is correct?
No. Connection status confirms only part of the setup. Check event content, identifiers, values and downstream behavior with a known transaction.
Should I resend all missing events immediately?
First identify the cause and understand the destination’s duplicate handling and time limits. Repeated bulk resends can introduce a second problem before the original one is understood.
Explore related workflows.
- First-party tracking software ↗
Capture website activity on a domain you control, then connect known visitors to the conversions and revenue in DATALYR.
- Server-side conversion tracking ↗
Connect verified business events to ad-platform conversion delivery in DATALYR. Configure rules, inspect destinations and validate results before scaling.
- Marketing analytics API ↗
Read DATALYR marketing, attribution and revenue data through the HTTP API. Build internal workflows with explicit workspace access and metric definitions.