Impact of Disabled Rules in Adobe Launch on Page Load Performance | Community
Skip to main content
Amruthesh_AG
Community Advisor
Amruthesh_AGCommunity Advisor
Community Advisor
November 26, 2024
Solved

Impact of Disabled Rules in Adobe Launch on Page Load Performance

  • November 26, 2024
  • 2 replies
  • 843 views

Hello Adobe Analytics Community, 

I have a question regarding the behavior of disabled rules in Adobe Launch and their potential impact on page load performance. 

When we disable rules in an Adobe Launch property do these disabled rules still contribute to the size of the JavaScript library or affect the overall page load performance in any way? 

From my understanding: 
- The disabled rules remain in the Launch interface but are not included in the published library when a new build is deployed. 
- This means they should not impact the page load performance since they are not executed or loaded by the browser. 

However, I’d like to confirm: 
1. Does disabling a rule fully exclude it from the JavaScript library, or is there any residual impact? 
2. Are there any best practices to follow when managing disabled rules in a production environment? 

Your insights on this topic would be greatly appreciated! 

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 Isha Gupta

Per my understanding - disabled Rules/Data Elements/Extensions are never included in libraries hence have zero impact on page performance. However, deleting unnecessary elements is always preferable to simplify managing stuff around Adobe Launch.

 

Best,

Isha 

2 replies

Isha Gupta
Community Advisor and Adobe Champion
Isha GuptaCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
November 26, 2024

Per my understanding - disabled Rules/Data Elements/Extensions are never included in libraries hence have zero impact on page performance. However, deleting unnecessary elements is always preferable to simplify managing stuff around Adobe Launch.

 

Best,

Isha 

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    November 26, 2024

    This is my understanding as well... I think this is also why when you want to delete something, you need to disable it first and deploy, only then can you delete... Launch will prevent you from deleting anything that is in the Upstream Builds...

     

    If the disabling is temporary, then leaving it there and disabled shouldn't hurt anything... but if it's really gone, then cleaning it up just for your own management's sake is a good idea...

     

    If you are concerned about needing it for historical reference, you could always create an "Archive" property, with no intention to ever use it, but simply to make copies of old rules that you have removed from your build over the years.... Basically, you can copy the rule to this fake project... you will then have a date stamp for when the rule was moved, and you can always use the notes inside the element to give more context about why the rule was removed from the real property... If you ever need to bring it back, you can copy it back in and update it to your standards, or use it as a side by side template to rebuild it in your real property.

      bjoern__koth
      Community Advisor and Adobe Champion
      bjoern__kothCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      November 27, 2024

      Maybe worth mentioning that a disabled rule has to be published first to be able to delete it. So, even though it should not affect the library size, you must make sure to "push it through" before you can get fully rid of it

      Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...