Adobe Launch Core Extension Events: Complete Guide

Adobe Launch BCS 7 years ago (2020-02-20) 6710 Views 0 Comments
文章目录[隐藏]

When creating an Adobe Launch rule, the most important question is usually not “How do I create a rule?”

It is:

Which event should I use?

For example, a Click event is enough to track a CTA button. But it is not enough to track a successful lead form submission. A History Change event can detect SPA navigation, but it does not guarantee that the new page content is ready.

In this guide, I will explain the main Adobe Launch Core extension events, when to use them, and the situations where another event type is a better choice.

 

How Core Events Work

A Launch rule normally has three parts:

Rule component What it does
Event Decides when the rule starts
Condition Decides whether the rule continues
Action Sends data or runs code

For example, to track a Contact Us button:

  • Event: Core → Mouse → Click
  • Condition: The clicked element is the Contact Us button
  • Action: Adobe Analytics → Set variables → Send beacon

The event is only the starting point. You still need to configure the correct conditions and actions.

Browser

  • Tab Blur fires when the current browser tab loses focus. For example, a visitor is reading your website and clicks another browser tab. Your tab loses focus, so the Tab Blur event fires.
  • Tab Focus fires when the visitor returns to your browser tab. For example, the visitor switches from another tab back to your website.

Form

Form events are designed for standard HTML forms. A simple form might look like this:

<form id="contact-form">
  <input type="text" name="name" placeholder="Your name">
  <input type="email" name="email" placeholder="Your email">
  <input type="submit" value="Submit">
</form>

When configuring form rules, use a stable ID, class, or data attribute. Avoid targeting a form only by its position on the page.

  • Blur fires when a selected form field loses focus. For example, a visitor enters an email address and then clicks elsewhere on the page.
  • Focus fires when a visitor clicks or tabs into a selected form field. For example, a visitor clicks the first field in a contact form and the cursor appears.
  • Change fires when the value of a selected field changes. For example, a visitor changes a subscription plan from Basic to Pro.
  • Submit fires when a standard HTML form is submitted. For example, a visitor completes a form and clicks Submit.

A Submit event does not always mean that the form was successfully processed. The server may reject the form or return an error, so use a thank-you page, Custom Event, or Direct Call rule for conversion tracking.

Keyboard

  • Key Press fires when a visitor presses a keyboard key. For example, a visitor presses Enter to submit a search or activate a button.

Media

  • Media Play fires when media starts or resumes. For example, a visitor clicks Play on an HTML5 video.
  • Media Pause fires when a visitor pauses media. For example, a visitor watches a video for 20 seconds and then clicks Pause.
  • Media Ended fires when media reaches the end. For example, a visitor watches a video until it finishes.
  • Media Loaded Data fires when the browser has loaded media data. This is mainly useful for technical debugging rather than engagement reporting.
  • Media Stalled fires when media playback cannot continue. For example, a video pauses because of a slow or unstable connection.
  • Media Time Played fires after media has played for a specified time. For example, you can trigger an event after 30 seconds of playback.
  • Media Volume Changed fires when a visitor changes the volume. For example, a visitor lowers the volume while watching a video.

Mobile

  • Orientation Change fires when a mobile device changes orientation. For example, a visitor rotates a phone from portrait to landscape while watching a video.
  • Zoom Change fires when a visitor zooms in or out. This event may not be available in every Core extension version and should be tested before use.

Mouse

  • Click fires when a selected element is clicked. For example, a visitor clicks a Contact Us button, download link, banner, or navigation item.
  • Hover fires when a visitor moves the pointer over a selected element. For example, a visitor keeps the mouse over a product image for one second.
  • Mousedown fires when the pointer is over an element and the mouse button is pressed. It occurs before Click and is mainly useful for interactions such as drag-and-drop.

Other

  • Custom Code fires a rule when your JavaScript calls trigger(). Use it when a built-in event cannot detect the required behavior.
    if (window.location.pathname === "/thank-you") {
      trigger();
    }
  • Custom Event fires when the website dispatches a custom browser event. For example, a developer can dispatch an addToCart event after a product is successfully added to the cart.
    document.dispatchEvent(
      new CustomEvent("addToCart", {
        detail: {
          productId: "SKU-123",
          quantity: 1,
          price: 49.99
        }
      })
    );
  • Data Element Changed fires when a selected Launch data element changes. For example, a data element storing the selected subscription plan changes from basic to pro.
  • Direct Call fires when the website calls _satellite.track(). For example, the website can trigger a rule after a contact form has been successfully submitted.
    _satellite.track("contactFormSuccess", {
      formName: "contact form",
      formId: "contact-form"
    });
  • Element Exists fires when a selected element appears on the page. For example, a confirmation message or logged-in navigation element becomes available.
  • Enters Viewport fires when a selected element becomes visible in the visitor’s viewport. For example, a visitor scrolls down until a promotional banner appears on screen.
  • History Change fires when the browser URL changes through pushState, replaceState, or hashchange. For example, a visitor navigates between pages in a single-page application without a full page reload.
  • Time Spent on Page fires after a visitor remains on the page for a specified time. For example, you can trigger an event after 30 seconds.

 

Page load

  • DOM Ready fires when the browser has parsed the HTML and created the DOM. For example, the page structure is available, but images and other resources may still be loading.
  • Library Loaded (Page Top) fires when the Launch library loads. Use it when a rule must run as early as possible, such as for initial page-view configuration or consent logic.
  • Page Bottom fires when the website calls _satellite.pageBottom(). This event is generally not recommended for asynchronously loaded Launch libraries.
    _satellite.pageBottom();
  • Window Loaded fires when the browser has finished loading the page and its resources. For example, images, stylesheets, and scripts have finished loading.

Which Event Should You Use?

What you want to track Recommended event
CTA or button click Click
Successful form submission Custom Event or Direct Call
Standard HTML form submit Submit, then verify success
Video start Media Play
Video completion Media Ended
Video milestone Media Time Played
Banner impression Enters Viewport
SPA page view History Change + view-ready event
Traditional page view Library Loaded or DOM Ready
Dynamic element appears Element Exists
Custom business action Custom Event or Direct Call

Final Words

The Core extension contains many event types, but you do not need to use all of them.

Start with the real action you want to measure. Then choose the event that can detect that action reliably.

For simple interface interactions, Click is often enough. For important business outcomes, such as successful form submissions, purchases, or registrations, use a Custom Event or Direct Call whenever possible.

Like (4)
Post my comment
Cancel comment
Expression Bold Strikethrough Center Italic

Hi, you need to fill in your nickname and email!

  • Nickname (required)
  • Email (required)
  • Website