Data Lake Ingestion
Batch via Azure Data Lake or synchronous direct API ingestion
Upload Data File
Supported formats: CSV (with header row) and JSON (array of objects).
Required column/field: profileId.
The background scheduler processes uploaded files every 30 seconds.
Drop your CSV or JSON file here, or browse
Max 500 MB per file
Ingestion Job History
| File Name | Format | Status | Progress | Created | Actions |
|---|---|---|---|---|---|
|
|
|||||
| No ingestion jobs yet. Upload a file to get started. | |||||
| Loading... | |||||
File Format Guide
CSV Example:
profileId,email,firstName,lastName,eventType abc-123,alice@example.com,Alice,Smith,customerDataImport def-456,bob@example.com,Bob,Jones,customerDataImport
JSON Example:
[
{
"profileId": "abc-123",
"email": "alice@example.com",
"eventType": "customerDataImport"
}
]
Direct API Ingestion
Sends records synchronously to POST /api/events/ingest,
bypassing Azure Data Lake and the batch scheduler.
Supports CSV and JSON files.
Drop your CSV or JSON file here, or browse
File is parsed client-side and sent directly to the API
How Direct API Ingestion Works
- Your file is parsed in the browser and sent as a JSON array to
POST /api/events/ingest. - Records are processed synchronously in batches of 100 — no scheduler, no Data Lake storage.
- Use this mode for immediate ingestion when you don't need the audit trail of the batch pipeline.
- For large files (> 50 000 rows) prefer the Batch (Data Lake) mode to avoid browser memory limits.