Q1

A

A data mismatch occurs when the data visible in your source platform (e.g., an advertising or seller dashboard) does not match the data that has been synced and stored in your warehouse via Daton.

Common symptoms include:

• Missing records in Daton
• Delayed or incomplete data sync
• Partial data availability for a given period
• Inconsistent or mismatched records
• Unexpected differences in key metrics or totals

Q2

A

Data mismatches typically arise from one or more of the following root causes:

• Mismatched date ranges between the source report and warehouse query
• Integration being inactive or in an error state
• Incorrect accounts, profiles, or ad accounts selected in integration settings
• Expired, revoked, or insufficient API credentials
• API processing or attribution delays on the source platform side
• Comparing different metrics, dimensions, or filter logic between source and warehouse

Q3

A

Both OAuth-based connectors (e.g., Seller and Ads connectors) and API Key / Access Token-based connectors can experience mismatches, but for different reasons:

Q4

A

Always start by verifying the date range. Ensure you are comparing the exact same date range across all three of the following:

• The source platform UI report
• The warehouse data for the corresponding table
• The columns or metrics being validated

Q5

A

Navigate to your integration settings in Daton and confirm the following:

• The integration status is Active
• No authentication errors are displayed
• Recent syncs have completed successfully
• If authentication errors are present, re-authenticate the integration. Re-authentication applies primarily to OAuth-based integrations such as Seller and Ads connectors.

Q6

A

In your integration settings, verify that the following entities are correctly selected and match your source platform configuration:

• Accounts
• Profiles
• Properties
• Ad Accounts

Q7

A

For integrations that use an API Key or Access Token, verify all of the following:

• The API Key or Access Token in Daton matches the one generated in the source platform
• The credentials are active and have not expired or been revoked
• The credentials carry the required permissions and scopes for the data being validated
• If credentials were recently rotated in the source platform, the updated values have been entered in Daton integration settings

Invalid, expired, or insufficiently permissioned credentials can result in missing data, incomplete syncs, or data mismatches.

Q8

A

Before concluding that a sync issue exists, confirm that the following are consistent between your source platform report and your warehouse query:

• Metrics (e.g., impressions, clicks, spend, revenue)
• Dimensions (e.g., date, campaign, ad group)
• Applied filters
• Validation or aggregation logic

Q9

A

Some source platforms introduce delays in API data availability due to processing pipelines or attribution windows. If data appears incomplete:

• Allow sufficient time for the sync window to complete
• Do not compare data immediately after a sync — wait for the platform to finalize its reporting
• Re-check the data after the expected delay period for your specific connector

Q10

A

If the discrepancy persists after completing all troubleshooting steps, escalate to the Daton support team with the following details:

Providing all of the above details upfront will significantly reduce investigation time and help the support team identify the root cause faster.

Q11

A

After completing the validation steps described in this guide, one of the following outcomes should occur:

• The data discrepancy is self-resolved — a configuration fix (e.g., re-authentication, credential update, or account selection correction) closes the gap
• The shared details provide sufficient context for the Daton support team to investigate and recommend the appropriate resolution