Event firing more often in Launch than DTM | Community
Skip to main content
Level 4
June 10, 2020
Solved

Event firing more often in Launch than DTM

  • June 10, 2020
  • 12 replies
  • 5058 views

Hi everyone!

We've migrated from DTM to Launch.

We have some legacy page view events in our custom code that fire both the hit and visit based variant of the event when a customer visits a specific page:

 

 

if (pageName == "section|subsection1|subsection2|title") { s.events = s.events ? s.events += ',' + 'event1,event2' : 'event1,event2'; }

 

 

The hit based variant of the event tracked against the page views metric in Analytics exactly when deploying with DTM, but since migrating to Launch the event metric exceeds the page views metric by about 50%. After firing the event I'm using the 'Clear Variables' action to reset the event string and when debugging I can't see multiple instances of the same event.

Does Launch process or send events differently? Is there something I need to tweak in the configuration?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Andrey_Osadchuk

Philip,

What I would advise to start with is to optimize the code the way that event1 and event2 are appended through the s.apl() plugin to prevent events duplication in case they are set somewhere else (in other rules, for example).

Ideally, share the website URL and scenario where that is happening. I am sure we will find an issue in the code. Alternatively, share the library URL and I will help you debug the Launch implementation via Launch Inspector.

12 replies

Andrew_Wathen_
Community Advisor
Community Advisor
September 17, 2020
@philipk92120636 Happy to have a look if you DM me the URL. Also, have you had a look in Workspace to see what the additional events are coming through against? Is it setting the event more than once against a single page view, or are the additional events originating from link tracking metrics calls?
Level 4
September 18, 2020
The event itself was linked to our page load rule. It just fired the success event if the page was the specified page name. I had to turn off the events in our production environment. I'll have a look at the historical data as you've suggested.