Hi Team,
I have an existing rule in adobe launch that loads on pageBottom and some custom code.
Now, I have changed the existing rule to load on "windowLoaded" and also changed the custom code inside the rule.
Expected: The existing rule should be updated with the new configuration.
Strange behavior :
I can see two rules appearing in the launch script - one with the old configuration and one with the new configuration.
Does anyone experience a similar situation? If yes, what way it can be solved, please give some pointers.
Thanks in advance!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @RitendraS11
Clear Cache: Start by clearing your browser cache and refreshing the page to ensure you're seeing the latest changes.
Publish Changes: Make sure that you have properly published the changes you made to the rule. Sometimes, changes might not take effect if they haven't been published.
Check for Duplicate Rules: Verify that you don't have duplicate rules in Adobe Launch. It's possible that the old rule was not updated, but instead, a new rule was created with the updated configuration. This could lead to both rules appearing in the launch script.
Rule Priority: Check the priority of your rules to ensure that the new rule with the "windowLoaded" configuration takes precedence over the old rule with the "pageBottom" configuration. You can adjust the rule priority in Adobe Launch to control the order in which rules are executed.
Review Rule Conditions: Review the conditions set for both the old and new rules to ensure they are mutually exclusive and don't overlap. Overlapping conditions can cause multiple rules to fire, leading to unexpected behavior.
Inspect Launch Container: Use the browser's developer tools to inspect the Adobe Launch container on your website and see which rules are being loaded. This can help identify any discrepancies between the rules configured in Adobe Launch and what is actually being executed on the website.
What you're experiencing is not expected.
Check the following:
Views
Replies
Total Likes
The issue seems to be with how you might have built your library. But even that seems unlikely, because, since there is only 1 rule as per your description, there is not really a possibility of seeing two rules in Launch script unless you have created a new rule. Can you confirm how did you come to the conclusion of seeing two rules? Did you check in the Developer tools -> Sources -> Adobe assets -> launch script ?
Views
Replies
Total Likes
Hi @RitendraS11
Clear Cache: Start by clearing your browser cache and refreshing the page to ensure you're seeing the latest changes.
Publish Changes: Make sure that you have properly published the changes you made to the rule. Sometimes, changes might not take effect if they haven't been published.
Check for Duplicate Rules: Verify that you don't have duplicate rules in Adobe Launch. It's possible that the old rule was not updated, but instead, a new rule was created with the updated configuration. This could lead to both rules appearing in the launch script.
Rule Priority: Check the priority of your rules to ensure that the new rule with the "windowLoaded" configuration takes precedence over the old rule with the "pageBottom" configuration. You can adjust the rule priority in Adobe Launch to control the order in which rules are executed.
Review Rule Conditions: Review the conditions set for both the old and new rules to ensure they are mutually exclusive and don't overlap. Overlapping conditions can cause multiple rules to fire, leading to unexpected behavior.
Inspect Launch Container: Use the browser's developer tools to inspect the Adobe Launch container on your website and see which rules are being loaded. This can help identify any discrepancies between the rules configured in Adobe Launch and what is actually being executed on the website.
Views
Likes
Replies