Integration Troubleshooting

When issues arise with an integration, the following steps can help isolate and resolve problems quickly

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 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 and Include:

    • The affected integration(s).

    • The time frame of missing or inconsistent data.

    • Screenshots from both the source system and Daasity dashboards.

PreviousPopular SetupsNextFAQ

Last updated

Was this helpful?