Adobe Analytics

adobeusermouse · 4/6/23

We have two pages in our application that have different ways of serving our adobe analytics. The entry point is using the legacy implementation and interior pages are using the web sdk implementation. Will events be able to be tracked from one application to the other or will there be a loss of data since the implementation details are different? Some use cases below.

Visitor clicks on button in Site A - analytics event sent via legacy implementation, user is routed to Site B. In site B user signs up for a service. Conversion and other interaction events are recorded to adobe analytics sent via the web sdk.

yuhuisg · 4/7/23

Yes, you can most certainly track different sites with AppMeasurement or Web SDK.

However, to ensure that you track visitors with the same ID, you should also implement Experience Cloud ID Service (ECID) with both AppMeasurement and Web SDK. Normally, when implementing AppMeasurement, you would also implement ECID too. But with Web SDK, you don't have to implement ECID since Web SDK can generate one from the server side.

In your case, though, since AppMeasurement depends on a client-side ECID, you should also implement ECID on the client side, so that Web SDK can pick up this value instead of using its server-side one. In that way, you can ensure that visitor Leroy Jenkins will have the same visitor ID in both Sites A and B.

View solution in original post

yuhuisg · 4/7/23

Yes, you can most certainly track different sites with AppMeasurement or Web SDK.

However, to ensure that you track visitors with the same ID, you should also implement Experience Cloud ID Service (ECID) with both AppMeasurement and Web SDK. Normally, when implementing AppMeasurement, you would also implement ECID too. But with Web SDK, you don't have to implement ECID since Web SDK can generate one from the server side.

In your case, though, since AppMeasurement depends on a client-side ECID, you should also implement ECID on the client side, so that Web SDK can pick up this value instead of using its server-side one. In that way, you can ensure that visitor Leroy Jenkins will have the same visitor ID in both Sites A and B.