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

Coffee Break: Join us on Wednesday, April 5th at 10am PT to chat with Ben Gaines, Director of Product Management for Adobe Analytics. Ben will be online to answer your Analytics and Adobe Summit questions.

Adobe launch Rule Creation Suggestion


Level 4

Hi All,


We have been doing custom tracking for certain landing page. We used to track all the buttons/links and other particular clicks under custom script (open editor). Refer the below code for example.

 Custom Code ExampleCustom Code Example

Since these days we have worked on many custom tracking, all these custom code falls under in to the “All Page Load Rule” which is obviously load on all the page and fire respectively for the mentioned click based on the identifier.

As all the code is fall under the all page load rule, it doesn’t feel standardized and bit difficult to maintain.  Therefore, we have choose below two option and would like to know from experts which suits best in order to launch rule optimize and perfect creation.

  1. Creating separate rule for each click with specific condition if required. However, this may need to create more rule if the custom tracking has more button and links. Eventually this also increase the file size of the launch script and very much difficult to maintain.
  2. Creating one rule for each landing page with specific condition if required and put all the custom code in open editor. So this may load only for the specific landing page and trigger for the respective identifier.

Any other suggestion would also welcomes. Please let me know if any.

Thank you,


1 Reply


Community Advisor

I think Option 1 is the "most correct" approach.

Launch's Core extension has several Event types that can respond to browser events. Mouse clicks are one of them, under the "Click" Event type. Furthermore, this Click Event type is not limited to regular <A> elements, so it can be used to detect clicks anywhere. When configuring the Event, you can set any valid CSS selector. In your example, the selector can be as simple as ".adobelaunchtest". You can also comma-separate selectors to include more than one with the same Event type, then you don't need to create multiple Rules if they all share the same Conditions and Actions.

If you're worried about having too many Rules to manage, you can go with a hybrid approach, e.g.

  1. Use your jQuery method for clicks within pages' content.
  2. Use the Click Event type for "common" elements, e.g. header and footer links, menu navigation.

But I would personally use the Click Event types only, even if it results in more Rules being created. I think that approach is more in line with how Launch has been designed to be used, and might also make sense to future maintainers of your Launch property.

The ultimate experience is back.

Join us in Vegas to build skills, learn from the world's top brands, and be inspired.

Register Now