Customer experience | Sales, Customer Insights,...

Matching Error - Conflation: Match failed

(1) Share

Report

Posted on by Barney Lawrence

Hello, I’m encountering an issue with Customer Insights while running the unify process.

Matching runs for a few minutes and then fails with the error message - Conflation: Match failed. Something went wrong. Please try again and if the problem persists contact support.

Looking at the list of tasks it appears that deduplication on the primary source runs and then something fails after this but before moving on to the next source in the list to match. I have deleted and re-created the deduplication rule with no impact on the issue.

I’ve also re-ordered the matching order after the primary record to see if the issue was the match on the secondary sources but that makes no difference either.

I’ve checked the source data for error values and see none.

The environment has worked before. We hit errors when changes to column names pushed through power query into customer insights meant that the names CI was expecting didn’t match the source. I resolved this by removing some unneeded columns that simply pass through the process untouched and duplicated columns needed for matching so that a copy with their old names existed. This resolved the initial errors we were encountering but led to the above new one.

Any suggestions on how to proceed from here?

Thanks,

Barney

Are you able to provide advice on how to resolve this issue?

All responses (2)

Answers (0)

Scott Stabbert on at

Like (0)

Report

RE: Matching Error - Conflation: Match failed

Hi Barney,

I think you're on the right track as to what the problem was.
Customer Insights maintains metadata about your source entities. If the schema changed, that can cause issues. If the incoming data doesn't match the schema, that can cause issues.

This was happening in the Match phase, so it was something that wasn't caught during the data ingestion phase, but hard to say now.

Best of luck! Sorry it took a while to respond on this. We (The engineering team) generally look for posts every morning.
Suggested answer

Barney Lawrence 21 on at

Like (0)

Report
RE: Matching Error - Conflation: Match failed

I managed to make the problem go away but I'm not 100% sure what the actual fix was.

Steps I took:

Removed all deduplication rules in the deduplicate records section.

Identified a number of unneeded fields and removed them in the source fields section.

Made some order changes in the unified customer fields.

I suspect that somewhere in the process Customer Insights was trying to read in\use a field that no longer existed in the source although I have no way to prove this without deliberately recreating the situation.