What’s changed?
Previously, audience exports always returned a single record per customer, even when selected fields existed at a more granular level (for example, multiple affluence segments per customer). As a result, some valid records could be excluded during the export process.
You can choose how your audience is deduplicated when creating an export.
Your deduplication options
When exporting your own customer base as a CSV, you’ll see a deduplication choice:
1. Distinct by selected columns
Produces one record per selected column combination
Useful when you want structured, column-level uniqueness
Behaviour matches existing exports to avoid surprises
2. Return all records
Returns all records across the selected fields
No implicit deduplication by customer ID
Ideal for enrichments and extractions where full granularity matters
Example: If a customer has three affluence segments and you include that field in your export, the file will now contain three records for that customer.
What stays the same
If you don’t select a deduplication option, exports default to one record per customer
Record counts shown in previews will always match the exported file
Built-in transparency and safeguards
To keep things clear and predictable:
Your selected deduplication mode is visible, saved, and auditable
Results are deterministic and repeatable
If “Return all records” produces a very large export, you’ll see a warning before proceeding
Data is never silently dropped or truncated
You can see the columns you chose to export
Why this matters
Different use cases need different levels of detail. This update ensures you can:
Export one row per customer when needed
Or retain full field-level detail for deeper analysis and enrichment
All while staying aligned with Omnisient’s privacy-first design.
As always, if you have questions or feedback, just reply here or reach out via Intercom—we’d love to hear from you.