Person IDs & privacy

A good customer ID should make data easier to use without making identity easier to expose.

Infinite Audience returns an iag_person_id as an organization-scoped, non-reversible label. It helps your team recognize the same resolved person across enrichment, segments, audiences, and supported integrations—without exposing the underlying identity used inside the Infinite Audience graph.

One identity, safely scoped to your organization

Every organization gets its own private identity namespace. We combine the identity with an organization-specific secret before creating the ID you receive.

That gives you three useful guarantees:

Consistent for your team. The same resolved person receives the same ID within your organization.
Different across organizations. Another company receives a different ID for that person, so IDs cannot be compared across customer accounts.
Built for reuse, not reversal. The value is a durable reference—not a container for a name, email address, or raw platform identity.

Think of it as a privacy-safe customer key made for your Infinite Audience workspace.

Real IDs and derived IDs do different jobs

Resolved person ID

A tier 01 ID means the record resolved to a real identity in the Infinite Audience graph. Keep it: this is the ID that can support direct refresh, record licensing, reusable segments, and audience building.

Derived ID

A tier 02–05 ID is a consistent label created from the unmatched row’s own identity signals. It keeps that row recognizable in your output, but it does not claim that Infinite Audience found a real person.

Derived IDs use the strongest available combination from the submitted row—such as name and address, email, name and phone, or name and ZIP code. They are still organization-scoped and non-reversible.

What comes back	What it means	What to do next
Tier `01` person ID	A real graph identity was resolved	Save it with the customer record and reuse it in supported refresh and audience workflows
Tier `02–05` derived ID	The row did not resolve, but had enough signal for a consistent organization-safe label	Keep it for file continuity and reconciliation; send stronger identity signals if you want to try resolution again
No ID	The row did not resolve and did not have enough signal to create a derived label	Keep the source `row_id` for correlation and add better identity data when available

Why this matters for enrichment

When a record resolves, its tier 01 ID lets supported workflows go straight back to the known identity. That can make future enrichment refreshes faster and avoid repeating identity resolution when the ID is supplied.

A derived ID cannot be used for direct refresh because there is no resolved graph identity behind it. If the customer returns later with a stronger email, phone, or address, submit those signals again. A successful match will return a tier 01 ID.

Why this matters for audiences

Resolved tier 01 IDs give audience building a clean identity foundation. Multiple rows that point to the same person can resolve to one durable identity, and that identity can move from an enriched file into a segment and then into an audience without relying on raw contact details.

Derived IDs keep unmatched rows visible in supported exports, but they are not treated as resolved audience members or activation-ready identities. This keeps audience counts grounded in people Infinite Audience actually resolved.

A simple operating habit

Save the tier 01 iag_person_id alongside the customer record in systems where your privacy and data policies allow it. Send it back on supported workflows, and keep your own source row_id as the reliable link to the original file row.

Next, see how identity resolution and enrichment creates these IDs, or learn how record licensing makes a resolved identity reusable for 12 months.