> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/data-integrations/integration-troubleshooting.md).

# Integration Troubleshooting

### Common Causes of Integration Issues

1. Authentication Errors
   * API credentials have expired or been revoked.
   * User permissions in the source platform have changed.
2. Schema or Feed Changes
   * Source platforms (e.g., Shopify, Meta Ads, Nielsen) update their field structures.
   * Retail partners change POS or inventory export formats (affecting URS) .
   * Syndicated providers (URMS) adjust category definitions or ACV/TDP logic .
3. Data Volume or API Limits
   * Large historical pulls may exceed API rate limits.
   * Daily syncs may be throttled or partially complete.
4. Manual Upload Errors (CSV-based BSDs)
   * Incorrect file naming conventions.
   * Misaligned date formats or missing required fields.

### Manual Upload Errors (CSVs & Google Sheets)

* Incorrect file naming conventions.
* Misaligned date formats or missing required fields.
* Invalid formatted files (look for missing, misplaced, or non-quoted field separators, incomplete lines, or incorrect data types - eg: a string in a numeric field) 

### If issues persist after these steps, open a ticket with Daasity support and Include:

* The affected integration(s).
* The time frame of missing or inconsistent data.
* Screenshots from both the source system and Daasity dashboards.
* If the affected integration is an email webhook, attach the file you intended to submit originally

### Troubleshooting Workflow

1. Check the Account Health Dashboard

   Confirm whether the integration is failing globally (affects all accounts) or only in your workspace.
2. Validate in Source System

   Log into the original platform (e.g., Shopify, Google Ads, Nielsen portal) to confirm that the data is available and matches what Daasity attempted to ingest.
3. Re-run or Re-upload
   * If the error appears to be a mismatch between the raw data and the reporting tables, work with [Daasity support](mailto:support@daasity.com) to trigger a re-run of the sync.
   * For CSV-based uploads, reformat and re-upload the file, ensuring it matches the documented schema.
4. Escalate to Support

   If issues persist after these steps, open a ticket with [Daasity support](mailto:support@daasity.com) and Include:

   * The affected integration(s).
   * The time frame of missing or inconsistent data.
   * Screenshots from both the source system and Daasity dashboards.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.daasity.com/core-concepts/data-integrations/integration-troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.