AEP Web SDK - First party Edge Domain configuration resets ECID on page load

[AleksandarRi]

I have tried to configure AEP Web SDK/CDP in the first-party context: 

1. Adobe Launch to be self-hosted.

2. Reverse proxy to forward the Web SDK network calls from the first-party domain to the original Adobe Edge domain default folder /ee (edge.adobedc.net/ee).

3. Datastream configuration to pick the FPID cookie value. (can be accessed via Adobe Launch, verified as a cookie data element value).

At the moment, I have configured the edge domain not to be the original edge.adobedc.net, but one of the websites. It starts to mess up the ECID value, giving it a new one with each payload. The FPID cookie value stays the same on the page (re)load, but it seems it is not utilised to generate the same ECID. 

Also, originally used JavaScript to get the ECID value for the custom solution for the identityMap, but even when removing that part, having no ECID JS the problem stays. 

And in the end, I can see the data in the dataset/CJA, but every page has a new ECID. 

Any tips/tricks what to check in the configuration, or how to debug the moment when/if Web SDK can or cannot access the ECID generated on the previous pageload or the FPID as well? 

[nnakirikanti]

@AleksandarRi Did you tried these method to debug your web app?

1) https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/use-cases/debugging

2) https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/monitoring-hooks

Also few of the cases i have seen which might generate new ECID for every page reload (or new request). 

1) Third party cookie enablement would disrupt sometime.

2) try to proxy or block web app related code to find out that some one have not written cookie deletion.

Let me how it goes and happy to help more on this.

~cheers,

Naresh Nakirikanti.

[GigiCotruta]

Hello, @AleksandarRi,

Can I ask you some questions:
1. Can you please send some screenshots related to your proxy implementation. 

2. You said the following "At the moment, I have configured the edge domain not to be the original edge.adobedc.net, but one of the websites. It starts to mess up the ECID value", can I ask you why did you have to do that change?

3. Where did you configure that FPID inside RTCDP? Could you send a screenshot of that config? As I understand, it has to be in the Datastream configuration. 

4. Do you collect the FPID with identityMap right now or only with a data element from cookies?

I think that the problem might be related to how you are stitching the FPID and the ECID.

[kautuk_sahni]

@AleksandarRi Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

[aleksris · Accepted solution]

Hello everyone, 

@nnakirikanti @GigiCotruta @kautuk_sahni 

Thank you for the support, and apologies for the delayed reply, had a busy period. Here is the solution in the end, or the problem that had caused it. 

For the identityMap value, we have implemented a custom JS that rotates the primary identity, depending on which one is available to set as a primary, email, phone or ECID in that order. The problem began when we just added FPID in the JS, and the solution is to kick the ECID and replace it with the FPID. 

The learning is that you can have either ECID or the FPID in the identityMap, not both of them. 

It can also be monitored in both the extension and the interface. 

Here it is in the extension, you send the FPID and you get the ECID in the reply.

The same happens in the interface. The request. 

And the response.