During the ingestion of ID-Precise (Audience) or Geo-Contextual (Proximity) datasets, some records may be filtered out. The most common cause is "malformed" UUIDs, which occur when IDs do not follow the standard GAID or IDFA formatting required by our system.
How to check rejection reasons
After ingestion, you can find a detailed breakdown of rejected lines directly in your S3 bucket:
The .fail File: This file lists the exact number of rejected rows.
Error Logs: Alongside the rejected data, the file provides specific reasons why the records did not pass (e.g., invalid format or missing required fields).
More information on what is classed as a MAID can be found here.
x lines were processed, in which y errors occurred.
Note that only up to 10000 error messages and 1000 malformed device ids were printed out.
Remaining lines were processed successfully.
Onboarding result:
- status : WARNING
- start time : 2022-01-27T12:59:51.994189Z
- end time : 2022-01-27T12:59:53.203815Z
- duration : 1.21 seconds
Onboarding metrics:
- total file rows : 8963
- total datasets : 1
- total geometries : 8957
- total geometry references : 8957
- total rows with errors : 0
- total errors : 0
- total rows with warnings : 6
- total warnings : 12
- total missing geoIds : 0
Datasets geometry assignments:
- geo_id : 8957