Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Appmeasurement.js event is overriding the direct call rule event

Avatar

Avatar
Validate 1
Level 2
sidh19884490
Level 2

Likes

2 likes

Total Posts

32 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
sidh19884490
Level 2

Likes

2 likes

Total Posts

32 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
sidh19884490
Level 2

05-09-2017

Hi

I've some ajax pages on my site and I'm using direct call rule to track them. On some of the direct call rule I added some page / step specific events but these events are getting overridden by the event set ( which s.events="event4="+s_getLoadTime();) in the core appmeasurement.js. The specific events in the direct call rules get tracked if I remove s.events="event4="+s_getLoadTime(); from appmeasurment.js. Is there any workaround for this. or Is there a way to tell DTM to prioritize the events set in the direct call rule over the JS settings and override the JS events (s.events="event4="+s_getLoadTime();)?

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
sidh19884490
Level 2

Likes

2 likes

Total Posts

32 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
sidh19884490
Level 2

Likes

2 likes

Total Posts

32 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
sidh19884490
Level 2

07-09-2017

Yes, as I said if remove s.events from appmeasurment.js , then the direct call rule event works. However, I now used the s.events with s.apl plugin in the appmeasurement.js and the direct call rule events aren't getting overridden any more. My issue is resolved and everything is being tracked with this solution but posting it here for the information of the others if anyone is experiencing similar issue.

Answers (2)

Answers (2)

Avatar

Avatar
Springboard
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

329 likes

Total Posts

2,247 posts

Correct Reply

811 solutions
Top badges earned
Springboard
Validate 500
Validate 250
Validate 100
Validate 50
View profile

Avatar
Springboard
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

329 likes

Total Posts

2,247 posts

Correct Reply

811 solutions
Top badges earned
Springboard
Validate 500
Validate 250
Validate 100
Validate 50
View profile
jantzen_belliston-Adobe
Community Manager

08-09-2017

Thank you for posting the resolution! I'll go ahead and mark your own answer as correct.

Avatar

Avatar
Springboard
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

329 likes

Total Posts

2,247 posts

Correct Reply

811 solutions
Top badges earned
Springboard
Validate 500
Validate 250
Validate 100
Validate 50
View profile

Avatar
Springboard
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

329 likes

Total Posts

2,247 posts

Correct Reply

811 solutions
Top badges earned
Springboard
Validate 500
Validate 250
Validate 100
Validate 50
View profile
jantzen_belliston-Adobe
Community Manager

05-09-2017

It sounds like you are tying to set the s.events variable in two different places

  • In your core Analytics code library (AppMeasurement)
  • In a direct call rule

Whichever portion of code runs last it likely overwriting the previous variable value. I'm not aware of any work around for this or way of setting precedence.

I'd recommend pulling the s.events variable out of your core library if possible and only setting via rules.