Any concerns with using the stg.start Event?

I am trying to make sure some Helper functions are available when PP TM processes the first Data Layer Events that come in from the website.

If the website sends a Data Layer Event before PP TM, it will get processed very early, even before the stg.pageView Event. This stg.pageView Event (a bit misleadingly called “Page View - page begins to load” - misleadingly because it assumes that PP TM is always loaded quite early, which is rarely what web developers do with Tag Manager libraries) is however the “earliest” one you can choose among the built-in Event Triggers.

Anyway, when such an early Data Layer Event triggers a Tag, that Tag runs before anything else (even the prioritized stg.pageView Tags). If I want to use my global Helper functions in that Tag, I can’t.

There is the stg.start Event in the dataLayer queue, which appears to come before anything else. There was this topic Using stg.start as trigger? by @Thomas_Anode_FR 2 years ago, and for him it seems to have worked.

While my tests look good, I am a bit reluctant to change the entire loading structure to an Event that seems to not be officially documented anywhere by PP, so does anybody have any concerns / insights / experiences here?

And a shoutout to the PP documentation team to shed light on this Event somewhere.

Hi Lukas!

It’s okay to use stg.start as data layer event trigger. Alternatively you can push custom data layer events through a script placed before the installation snippet and use these events in their triggers. Like this:


2 Likes