What keys are used when audience from CDP is pushed to Target
Hi,
In our CDP we defined 2 identities:
- ECID from Adobe
- Client ID: our ID of the Client identified
We load online data in the CDP thanks to the source connector Adobe Analytics. We don't use any Adobe SDK or datastream.
In this connector, we also filter out the row if the cookie consent is equal to '1'.
It means that the data is available in the CDP data lake but not for profiling. So we cannot use this info for audience creation.
Now that I have set the scene, here are the facts:
- we upload information as attribute based on 'Client ID' identity to define the user to be part of the campaign. By checking the audience membership based on 'Client ID' identity, the user is part of the audience. This audience is pushed to Target as destination.
- this user can see the Target personalization on Edge browser but not on Chrome. By using the ECID from Chrome, I don't find any profile linked to it when I search for it based on ECID identity namespace.
- the same ECID from Chrome is present on the CDP datalake using query service BUT with a cookie consent equals to '1'. So it means that this info has been filtered out for profiling in the Analytics source connector due to a level of cookie consent not ok for profiling, what is the expected behavior.
Now I finally reach my question:
When an audience is pushed from CDP to Target, what keys are shared for mapping?
All identities keys defined, full list of ECID or even others keys?
I have the feeling it's about ECID but I would like to validate my assumption and I don't find any doc on this.
So on a business point of view, the behavior makes sense but I want to validate the technical part.
I tried to make it clear as possible but don't hesitate if you need any other details.
Thanks in advance for your help
Robin