Impact of deploy (load) Alloy.js ,At.js,AppMeasurement.js all together while planning to migrate to WebSDK. | Community
Skip to main content
N
NidhiAgrawal1
Level 2
December 19, 2022
Solved

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

  • December 19, 2022
  • 2 replies
  • 2487 views

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.

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

    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.

    2 replies

    vikramcl92
    vikramcl92
    Level 2
    December 19, 2022

    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-alloy-js-faq-s/ba-p/358527

    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-web-sdk-and-edge-network-880b635e6819

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

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

    Cheers!
    Vikram 

    N
    NidhiAgrawal1Author
    Level 2
    December 19, 2022

    If i want to keep legacy and alloy.js both. What will be the effect.

    vikramcl92
    vikramcl92
    Level 2
    December 20, 2022

    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.


    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. 

    yuhuisg
    Community Advisor
    yuhuisgCommunity AdvisorAccepted solution
    Community Advisor
    December 28, 2022

    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.

      Terms & ConditionsAccessibility statement

      Loading footer...