Neodata

Drop gzipped TSV audience files into a Neodata-provided Azure Blob container via a SAS URL. Neodata picks up device IDs (MAIDs), cookie IDs, and a taxonomy file from the drop directory on a recurring ingest cadence.

Prerequisites

A SAS URL issued by your Neodata account manager for the target Azure Blob container. SAS URLs embed a time-limited signature — rotate before expiry.
Your Client Name (assigned by Neodata) used as the parent directory prefix.
Your audiences configured with at least one of: gaid, idfa, idfv, advertising_id, device_id, cookie_id, tdid, external_id, user_id.

Authentication

Neodata uses Azure SAS URL authentication. The SAS URL includes the signature as a query parameter (sig=...). Paste the full URL into the SAS URL field:


https://<account>.blob.core.windows.net/<container>?sv=...&sig=...

SAS URLs expire — if syncs start failing with authorization errors, request a fresh SAS URL from Neodata and update the destination.

Configuration

Field	Type	Required	Description
Client Name	Text	Yes	Client identifier used as directory prefix: `ClientName-yyyy-mm-dd-hhmmssSSS/`.

Target Settings

Field	Type	Required	Description
Audience Name	Text	Yes	Segment name in Neodata’s taxonomy. Must match `[A-Za-z0-9][A-Za-z0-9_]*`.
Segment ID	Number	No	Numeric segment ID. If omitted, Zeotap generates a deterministic 4-digit ID from the audience name.

Supported Operations

Sync Modes

Neodata is audience-only; regular data-sync modes are not supported.

Audience Sync Modes

Mode	Supported
Add	Yes
Mirror	Yes (removes are dropped — SAS drops are append-only)
Remove	No
Upsert	No

Features

Field Mapping: No
Schema Introspection: No

How It Works

For each batch, Zeotap uploads up to three gzipped TSV files into a freshly-named directory under the SAS container:


<ClientName>-<yyyy-mm-dd-hhmmssSSS>/
├── Neodata_DeviceID_<ts>.csv.gz      # MAIDs (gaid, idfa, idfv, ...)
├── Neodata_Cookies_<ts>.csv.gz       # cookie/external IDs
└── Neodata_Taxonomy_<ts>.csv.gz      # segment ID → name mapping

Data file format (no header):


<userId>\t<segmentId1>,<segmentId2>,...

Taxonomy file format (no header):


<segmentId>\t<segmentName>

Rows with neither a MAID nor a cookie/external identifier are skipped and reported as failed rows. Mirror mode drops removed rows — Neodata’s drop model has no removal endpoint.

Troubleshooting

SAS URL returned HTTP 403 or 401

Your SAS URL has expired or lacks write permission on the target container. Request a fresh SAS URL from Neodata and update the destination’s credentials.

SAS URL host or container returned 404

The container path embedded in the SAS URL no longer exists or was typed incorrectly. Verify the full URL against the one Neodata provided.

Audience not appearing in Neodata

Neodata ingests files asynchronously from the drop container. Allow a few hours after the sync completes. Confirm the taxonomy file for your audience was uploaded — without the taxonomy entry Neodata cannot onboard the data files.

Rows skipped (“no usable identifier”)

Zeotap skips rows that do not contain any of the recognised identifier fields. Ensure your audience query projects at least one of gaid, idfa, idfv, advertising_id, device_id, cookie_id, tdid, external_id, user_id.

Audience name rejected

Neodata requires segment names to start with alphanumerics and contain only letters, numbers, and underscores. Rename the audience to comply.