Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Impact of deploy (load) Alloy.js ,At.js,AppMeasurement.js all together while planning to migrate to WebSDK.

Avatar

Level 2

HI,

We are planning to migrate WebSDK but instead of removing all js files like Appmeasurement.js,mbox.js,visitor.js at.js in one shot at the beginning state of migration we are planning to keep both (alloy and lagacy js(appmeasuremnet,at.js,mbox,js,visitor,js)). We want to know what will be impact for keeping both js (mbox.js,visitor.js ,alloy.js,at.js,AppMeasurement.js) apart from the effect on page performance.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

One thing to note is the risk of double-counting your hits.

For example, if you have configured the Datastream that you are using with WebSDK to also data to your Analytics service with your existing report suite ID, then you will be counting hits from Web SDK and hits from AppMeasurement.js to that Analytics same report suite. Similarly for Target and Audience Manager.

View solution in original post

5 Replies

Avatar

Level 2

Hi Nidhi,

Thanks for asking. 

If you are moving all the tags from the existing setup to web SDK, be mindful of the fact that a spike in page performance and data being sent to different vendors are to be expected.  

Below are some of the links that might be useful in understanding the implementation to impact risk analysis. 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-launch/adobe-web-sdk-allo...

https://experienceleague.adobe.com/docs/experience-platform/edge/web-sdk-faq.html%3Flang%3Den

https://blog.developer.adobe.com/solving-implementation-pain-points-with-adobe-experience-platform-w...

https://blog.developer.adobe.com/adobe-experience-platform-web-sdk-migration-scenarios-for-adobe-ana...

I hope this helps. Looking forward to more answers from other contributors 🙂 

Cheers!
Vikram 

Avatar

Level 6

Hi @NidhiAgrawal1 if you are not worried about page performance then I don't see a major impact. Its just additional scripts on the page and capturing stats multiple times.

We have had situations where we kept analytics connector & websdk enabled and were capturing stats twice since there were issues with WebSDK video event capture.

Avatar

Level 2

Correct. 

From the performance perspective impact would be on the page level and evet data being sent to the vendors. 
From a technical perspective, server calls would be increased as we retain both legacy and alloy.js, in turn, would impact the web server processing and storage space if we are having a huge traffic. 

Avatar

Correct answer by
Community Advisor

One thing to note is the risk of double-counting your hits.

For example, if you have configured the Datastream that you are using with WebSDK to also data to your Analytics service with your existing report suite ID, then you will be counting hits from Web SDK and hits from AppMeasurement.js to that Analytics same report suite. Similarly for Target and Audience Manager.