Skip to main content
Two dashboards can be internally correct while answering different questions. Compare definitions before totals.

​
Make the reports comparable

Match all of these:
  1. date range and timezone
  2. currency
  3. gross versus net revenue
  4. refunds, chargebacks, tax, and shipping treatment
  5. event date versus click or processing date
  6. attribution model and lookback window
  7. included accounts, campaigns, and environments
Ad platforms may each claim the same conversion inside their own attribution windows. Datalyr follows the journey and reporting rules configured in Datalyr, so its attributed total should not be expected to equal the sum of every platform’s claims.

​
Narrow the comparison

Start with one transaction, one campaign, and one day.
  • Transaction differs: compare amount, currency, refund state, and timestamp.
  • Spend differs: confirm the connected ad account and wait for finalized campaign data.
  • Conversion count differs: compare event definitions, deduplication IDs, attribution windows, and view-through inclusion.
  • Today differs but older dates match: allow for source sync and platform processing delay.

​
Check time boundaries

A purchase near midnight can land on different days when systems use different timezones. A platform may also report a conversion on the ad interaction date while Datalyr shows it on the event date.

​
Document the remaining gap

Record both report names, account IDs, filters, timezone, date range, metric definition, and one example record. A percentage difference without these inputs is not actionable.
Do not reconnect a healthy source to force two reports to agree. Reconnection cannot align different attribution or revenue definitions.