Third-party profile enrichment with partner data

What it does

Partner enrichments send your profile data to an external provider — Experian for household demographics, LiveRamp for AbiliTec identity, HERE Technologies for location — and write what comes back into a separate enrichment table keyed to the customer ID. You bring your own contract with the provider; Customer Insights supplies the connection, the run and the output.

Key facts

The enrichment catalogue on Data > Enrichment covers AbiliTec Identity (LiveRamp), Brands and Interests (Microsoft), Demographics (Experian), Enhanced addresses (Microsoft), Location data (Azure Maps), and SFTP custom data import for provider files you already receive.
Experian demographic enrichment is United States only and needs an active Experian subscription arranged directly with Experian.
The Experian connection is created under Settings > Connections and needs a User ID, Party ID and Model Number from an SSH-enabled Secure Transport account, plus verification of the connection and acceptance of the data privacy and compliance terms before it will save.
Input match keys: at least one of name and address, phone, or email. Supplying more than the minimum improves match rates.
Returned attributes include household size and income alongside other demographic data; the exact set depends on the model number your Experian contract covers.
Output is a named enrichment table, related to the unified profile by customer ID. Original profile fields are never overwritten.
Enrichments are managed from My enrichments: view, edit, run, activate/deactivate and delete. Deactivate leaves the configuration in place but excludes it from scheduled refreshes.
Scheduled refresh is set globally under Settings > System > Schedule, not per enrichment.
Detailed job progress and error reporting is available for Experian, Leadspace, HERE Technologies, SFTP import and Azure Maps — select the enrichment status to open the progress pane and drill into task details.
Results include enriched profile counts, a trend over time, a sample of the output table and a per-field coverage breakdown, which is the quickest way to judge whether the match keys are working.
Enrichment can also be applied to a data source before unification rather than to unified profiles, which is the right choice when the goal is better matching rather than more attributes.

When to use / skip

Partner enrichment earns its place when the client already buys the data — most large retailers and financial services firms have an Experian or equivalent relationship — and the pain is that the file lands in a spreadsheet nobody joins to CRM. Wiring it into Customer Insights turns a quarterly file into an attribute on the profile, and that is genuinely useful.

Skip it when the client does not already have the contract. You are then selling a third-party data purchase on top of a Dynamics project, with its own procurement cycle, its own legal review, and a US-only limitation in Experian's case that rules out most UK and EU work outright. Also skip when the actual requirement is address quality — Enhanced addresses and Azure Maps are first-party, included, and solve that problem without a vendor conversation.

Configuration decisions

Whether enrichment happens on the data source before unification or on the unified profiles afterwards. Pre-unification enrichment improves match quality and cuts duplicates; post-unification adds attributes. They are different jobs.
Which match keys you send. More keys means better match rates but more personal data leaving the tenant, and legal will want that decision documented.
Whether to enrich the whole Customer table or a segment, particularly where the provider charges per record matched.
Output table naming, agreed with whoever builds segments and measures, since those tables are what downstream logic references.
Refresh cadence, bearing in mind the schedule is system-wide, so the enrichment inherits whatever the unification schedule is.
Who holds the provider credentials and who is accountable for rotating them when the contact leaves.

Gotchas

Enriched attributes land in a separate table, not on the Customer table. Every segment or measure that uses them has to traverse the relationship, and people forget this and then claim the enrichment "did not work".
Experian is US-only. This catches out UK and European projects that saw the enrichment in the catalogue and assumed availability.
The connection is admin-owned and shared. Delete it and every enrichment built on it stops; deactivating the enrichment is usually what you actually want.
Sending customer identifiers to a third-party processor is a data protection decision, not a configuration one. Under UK GDPR you will need the processing basis and the DPA in place before the first run, and the client's DPO will ask.
Match rates on partner enrichment are rarely what the sales conversation implied. Run against a sample and read the per-field coverage before quoting a number to anyone.
The system-wide refresh schedule means you cannot run an expensive partner enrichment on a slower cadence than unification through the standard schedule settings; plan around it or run manually.

Consultant notes

Establish early whether the client owns the vendor contract. If they do not, park this and re-scope — procurement will outlast your project timeline.
Get the DPIA conversation started at design stage, not at UAT. It is the most common cause of a partner enrichment being configured and never switched on.
Demo the coverage-by-field view to the client rather than the raw table. It makes the value and the limits obvious in one screen and avoids arguments later.
If address quality is the underlying complaint, steer to Enhanced addresses or Azure Maps first. Both are included, and they often remove the perceived need for a paid enrichment entirely.
Before go-live, confirm the enrichment is activated as well as configured. A deactivated enrichment looks perfectly healthy in the list and quietly never refreshes.

Worth another look if Experian availability extends beyond the US, or if the partner catalogue changes.