| Scenario | Reason | Next Steps |
|---|---|---|
| No data | Triggers when no file is dropped and the uploader fails to pull data | In this case, first confirm that the file was generated or dropped as expected. Then, verify the connection and access to the source. If the issue persists, reach out to the Zeotap support team for assistance. |
| Pull fail scenario | Triggers if there is no file received as per the sync frequency configured for the source. | This scenario is similar to the “No Data” scenario, but in this case, the file itself is not generated. If this source (BigQuery, platforms, or CRM) is configured to pull data on a scheduled basis, then verify whether data was generated on your end for the specified date and confirm if this is an expected behaviour. If no data was generated, then the issue might relate to the source connection or access. In such cases, reach out to the Zeotap support team. |
| Ingestion failure scenario | Triggers if more than 20% of the received records of a file or a streaming source fail within 24 hours. | • Refer to the error log in GCS under <source id>/error log. • Fix the error mentioned in the report to ingest all the data successfully. |
| Delayed ingestion scenario | Triggers if the ingested file remains in progress for more than 48 hours. | This notification is not activated by default. To receive this error, reach out to the Zeotap support team. |
Sources
Source Alerts
Source alerts are email notifications that inform Zeotap CDP customers about failures in their created sources on Zeotap CDP. The report includes a list of failed sources and the causes of failure. This report is shared only with subscribed customers. Therefore, to subscribe to these email alerts, send a list of all email addresses that intend to receive these alerts.
The following are the error scenarios notified in the report:
Last modified on February 26, 2026