Level 3

Solved

Identities recognition for a destination

6 replies
1196 views
Translate All

QQ - What does "identities were not recognized by the destination" means in context to exporting data to a Destination?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

abhinavbalooniAccepted solution

Community Advisor

Hi @md__ajazan

This error means there were no matching identifier between the two systems, AEP and the destination for the export.

Look into whether the identities you are exporting should align more (match rate) with the destination.

If that's the case then check what might be wrong with the identity values you are exporting from AEP.

Cheers,

Abhinav

abhinavbalooni

Accepted solution

Community Advisor

Hi @md__ajazan

This error means there were no matching identifier between the two systems, AEP and the destination for the export.

Look into whether the identities you are exporting should align more (match rate) with the destination.

If that's the case then check what might be wrong with the identity values you are exporting from AEP.

Cheers,

Abhinav

Translate

M

Md__AjazAnAuthor

Level 3

Is there a possibility that some identities were missing attributes? For example, lets say that I have following mapping to destination:

Attributes - src. ---> Attributes - Dest

A ---> A1 (mandatory at destination side but maybe optional in my datalake/dataset.)

B ---> B1 (not mandatory but Null at source)

C ---> C1

1) What happens in case of attribute A above where the mandatory field is not present in dataset since its optional?

2) Case of Attribute B above where B is Null/empty at the source?

Translate

abhinavbalooni

Community Advisor

@md__ajazan As per my understanding, it is only looking at the identity fields here. Unless the attributes you've mentioned are identity fields, should not impact.

Cheers.

Translate

Sign up

Login with SSO

Login to the community

Login with SSO