Types of rules in Adobe Launch – Detailed Guide

by
5/5 - (4 votes)

Adobe Launch, part of Adobe Data Collection Tags, enables efficient tracking and data collection through customizable rules. This detailed guide covers the types of rules in Adobe Launch, their use, and when to use which for optimal performance. Whether it’s page load, click tracking, or advanced media interactions, understanding these rules helps streamline tag management and improve website analytics.

Rules in Adobe Launch/Adobe Data Collection Tags

Rules in Adobe Launch are sets of instructions that tell the system when to execute specific actions based on predefined conditions and events on a website. A rule is composed of three parts:

  1. Events – Define the user or system actions that trigger the rule (e.g., page load, click).
  2. Conditions – Optional filters that refine when an event leads to an action.
  3. Actions – Specify what happens when the event and conditions are met (e.g., sending data to an analytics tool).

When to Use Rules in Adobe Launch/Adobe Data Collection Tags

  • Use rules to track user interactions such as clicks, page views, or form submissions.
  • To fire marketing tags (like Adobe Analytics or Google Analytics) under specific conditions (e.g., when a user completes a transaction).
  • For custom tracking implementations, like tracking video plays, button clicks, or any custom user interaction.

Types of Rule Events in Adobe Launch (Free and Premium)

1. Core Events (Free)

These are basic events available in the Core Extension of Adobe Launch.

  • Library Loaded: Fires when the Launch library is fully loaded.
    • Example: Track initial page load time.
  • Page Bottom: Fires when the browser has finished rendering the page.
    • Example: Trigger a pixel to track page views.
  • DOM Ready: Fires when the DOM has finished loading (before images and styles are fully loaded).
    • Example: Track user behavior after the DOM loads, but before all assets are loaded.
  • Custom Event: Fires when a developer-defined custom event occurs.
    • Example: Custom trigger like a user hovering over a special menu.
  • Click: Fires when an HTML element (e.g., a button or link) is clicked.
    • Example: Track clicks on a download button.
  • Element Visibility: Fires when a specific element becomes visible within the viewport.
    • Example: Trigger an action when a certain section of the page (like a hero banner) is visible.
  • Focus: Fires when an element (like an input field) receives focus.
    • Example: Track when a user clicks into a form field.
  • Mouse Over: Fires when the user hovers over an element.
    • Example: Track mouse hover on a product image.
  • Scroll Position: Fires when the user scrolls to a specific position on the page.
    • Example: Trigger an event when a user scrolls past a specific section.

2. Premium Events (Available in Specific Extensions)

These events are available in premium extensions or for advanced tracking use cases, particularly for Adobe tools.

  • Adobe Analytics – Track Action: Fires an event tied to specific Adobe Analytics actions.
    • Example: Trigger an Adobe Analytics event when a user submits a form.
  • Adobe Target – VEC Event: Fires an event when a user interacts with an element involved in an Adobe Target test.
    • Example: Trigger an action when a user clicks on a test variant in an A/B test.
  • Video Tracking Events: Available for platforms like Brightcove or YouTube within the video tracking extensions.
    • Example: Fire an event when a user starts, pauses, or finishes a video.
  • eCommerce Events: Specific to eCommerce platforms like Magento or Shopify.
    • Example: Track add-to-cart or checkout completion events.
  • Media Analytics: Tracks events like video plays, pauses, and video completions.
    • Example: Track video milestones for media-rich websites.

Examples of When to Use Specific Rules

1. Tracking Button Clicks (Core Extension)

  • Event: Click (on a specific button)
  • Condition: Button ID matches “cta_button”
  • Action: Send data to Adobe Analytics and Google Analytics

2. Page Load Tracking (Core Extension)

  • Event: DOM Ready
  • Condition: None (always fire)
  • Action: Send page view data to Adobe Analytics

3. Tracking Scroll Depth (Core Extension)

  • Event: Scroll Position (50% of the page)
  • Condition: User has scrolled past 50% of the page
  • Action: Fire an Adobe Analytics event to track scroll depth.

4. Tracking Video Interaction (Premium – Brightcove Extension)

  • Event: Video Play
  • Condition: None
  • Action: Send video play data to Adobe Analytics

5. Tracking User Test Variants (Premium – Adobe Target Extension)

  • Event: VEC Event (Variant Interaction)
  • Condition: User interacts with variant “B”
  • Action: Send conversion data to Adobe Target

Core Extensions (Free) – These provide general functionality available to all Adobe Launch users:

  • Click
  • Form Submission
  • Page Load
  • Element Visibility
  • Custom Event
  • Scroll Position
  • Time on Page

Premium Extensions – Available for specific advanced or premium features in Adobe Launch:

  • Adobe Analytics (for advanced tracking)
  • Adobe Target (for personalization events)
  • Media Tracking (Brightcove, YouTube, etc.)
  • eCommerce Tracking (Magento, Shopify, etc.)

Summary

Use Core Rules for general tracking needs like page loads, button clicks, and scroll tracking. Use Premium Rules when you need to integrate with advanced Adobe tools like Analytics, Target, or Media Tracking for more specific or detailed interactions. Each rule type caters to different tracking or tagging needs, providing flexibility in data collection and user interaction monitoring.

In summary, mastering rules in Adobe Launch is key to optimizing data collection and tag management across various user interactions. For more insights and expert tips on web analytics, visit Interview Techies, your go-to resource for cracking interviews and enhancing your technical skills in the analytics domain.