18 When to Fire Tags or Page Load Events

Table of Contents

When to Fire Tags or Page Load Events?
In fact, there are only two types of user interactions on the page. One is the basic Pageviews, which belongs to Page Load, and the other is behavioral interaction, such as clicking. There are many types, such as browser, form, keyboard, and media and so on.

Pageviews——Page Load

There are four types of Page Load. Although the functions are similar, the order is different.Regardless of when the Launch library finishes loading, all the rules are guaranteed to be executed and they will be executed in the following order: Library Loaded (Page Top)>Page Bottom>DOM Ready>Window Loaded.

Although the order is always enforced, some rules might be executed immediately when the Launch library finishes loading, while others might be executed later. The following occurs when the Launch library finishes loading:

Rule A is executed immediately.
If the DOMContentLoaded browser event (DOM Ready) has already occurred, Rule B and Rule C are executed immediately. Otherwise, Rule B and Rule C are executed later when the DOMContentLoaded browser event occurs.
If the load browser event (Window Loaded) has already occurred, Rule D is executed immediately. Otherwise, Rule D will be executed later when the load browser event occurs. Note that if you’ve installed the Launch library according to the instructions, the Launch library always finishes loading before the load browser event occurs.

When applying these principles to your own website, consider the following:

A rule using the Library Loaded event type might execute before your data layer is fully loaded. This can result in the rule’s actions executing with missing data because the data was not yet available on the page. These types of issues can be mitigated by tweaking your rule configuration. As an example, instead of having a rule triggered by the Library Loaded event type, you could instead use the Custom Event or Direct Call event type that are triggered by your page code as soon as your data layer finishes loading.
The Page Bottom event type doesn’t particularly provide value when the library is loaded asynchronously. Instead, consider the Library Loaded, DOM Ready, Window Loaded, or other event types.

If you see things occurring out of order, it is likely that you have some timing issues to work through. Deployments requiring precise timing might need to use event listeners and the Custom Event or Direct Call event type to make their implementations more robust and consistent.

DOM Ready

Trigger when the DOM is ready and the user can interact with the page. But not all of the page content has been displayed. Maybe your page is only displayed a part, this state means that the DOM is ready, but the window is not complete.

There are no settings for this event type.

Library Loaded (Page Top)

Trigger the event as soon as the Launch library is loaded. Fired when the head Library is loaded.

There are no settings for this event type.

Page Bottom

Trigger the event once _satellite.pageBottom(); has been called. When loading the Launch library asynchronously, this event type should not be used. It’s basically useless now, because the code is loaded asynchronously by default.

There are no settings for this event type.

Window Loaded

Trigger the event when onLoad is called by the browser and the page has finished loading. The logo on the browser no longer turns.

There are no settings for this event type.

In general, we usually use Library Loaded (Page Top) when deploying code events conditions. This is the fastest loading to ensure the accuracy of the data.

Interactive behavior

There are many behavior interactions. Adobe Launch has a lot of built-in behaviors, which is convenient for users to set events and choose according to the actual situation: