Data License Ingestion
This page explains how to tell when a Data License delivery is fully complete and ready for ingestion.
It is the single source of truth for delivery completion signals and automation best practices across Data License delivery methods.
What you should use
For every Data License delivery, the reliable completion signal is the top-level file named:
This file is generated only after the full delivery is finished. It is the file your automation should use to start ingestion.
Why COMPLETED matters
When the COMPLETED file exists:
- ✅ All data files have been delivered
- ✅ No additional files will be added to the delivery
- ✅ It is safe to begin ingestion
Using COMPLETED avoids partial ingestion and inconsistent results.
Where COMPLETED appears
- The file is placed in the parent/top-level folder for the delivery
- It covers all files and subdirectories within that delivery
- It appears for all supported delivery methods:
- S3
- Snowflake
- Azure
- GCP
- Direct Download
Don’t Use: _SUCCESS
Some deliveries may also include _SUCCESS files inside nested folders.
These files are not intended as a customer ingestion trigger because:
- They are created per subdirectory
- They can appear before the overall delivery is complete
- They reflect internal PDL processing, not final delivery readiness
Do not trigger ingestion from _SUCCESS files.
Use only the top-level COMPLETED file for automation.
Recommended automation workflow
- Monitor the delivery folder for
COMPLETED
- When
COMPLETED appears, start ingestion
- Process all files and subfolders in the delivery
- If
COMPLETED is missing, do not ingest partial data
- If the delivery is delayed, contact your CSM or support team
Example delivery layout
If the COMPLETED file does not appear after you expect the delivery to be ready:
- check your delivery notifications
- verify that the delivery destination is correct
- contact your Customer Success Manager
Why this is the best signal
COMPLETED provides a consistent ingestion trigger across delivery methods and avoids the confusion caused by _SUCCESS files appearing at different times.
For delivery-specific setup and access instructions, see the relevant Data License delivery method pages.
