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

Allow for DTM to suppress/disable Tools for page load rules.

Avatar

Avatar
Contributor
MVP
joshd7227840
MVP

Likes

275 likes

Total Posts

241 posts

Correct Reply

70 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Contributor
MVP
joshd7227840
MVP

Likes

275 likes

Total Posts

241 posts

Correct Reply

70 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
joshd7227840
MVP

31-07-2014

When making an Event Based Rule or Direct Call Rule, there is a Tracking section at the top of each Tool's section to flag it to be disabled for the rule. 

 

However, this feature does not exist for Page Load Rules.  So for example, if I want to disable Adobe Analytics tracking on a certain page, there is no built-in way within DTM to do this.  Or for example, If I only want to output Adobe Target code on a certain page (e.g. landing pages), there is no native within DTM to suppress it. 

 

Please add this feature to DTM!  

3 Comments

Avatar

Avatar
Contributor
Level 4
mikethompson
Level 4

Likes

62 likes

Total Posts

102 posts

Correct Reply

14 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Contributor
Level 4
mikethompson
Level 4

Likes

62 likes

Total Posts

102 posts

Correct Reply

14 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
mikethompson
Level 4

07-08-2014

If you put s.abort=true; in the custom page code in the rule, it should block the page from tracking. However, it would be nice to have a radio button like the others.

Avatar

Avatar
Contributor
MVP
joshd7227840
MVP

Likes

275 likes

Total Posts

241 posts

Correct Reply

70 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Contributor
MVP
joshd7227840
MVP

Likes

275 likes

Total Posts

241 posts

Correct Reply

70 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
joshd7227840
MVP

07-08-2014

Hello MikeT,

 

Thanks for the comment! Yes, that is a workaround I use in some "better than nothing" cases but two things about that:

 

1) This only accounts for AA, not any other tools/tags

 

2) Using s.abort simply supresses the actual request to Adobe from happening. It does NOT wholesale stop AA from executing. So if you have any rules or other code invoked sometime before that final s.t or s.tl call, it will get executed - including s_doPlugins calls.  So for example.. if you have cookie based plugins this could affect cookie values or logic in general.  IOW using s.abort is generally a BAD IDEA in practice, depending on your tracking code setup. 

 

.josh

Avatar

Avatar
Boost 3
Level 1
michaell9759171
Level 1

Likes

3 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile

Avatar
Boost 3
Level 1
michaell9759171
Level 1

Likes

3 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile
michaell9759171
Level 1

07-04-2015

A way I worked around this was to make a data element (like "firePage") and set to default to 1. Then I have custom script for that element and can set it to 0 for any URL, etc. I want.


Then in the global anlytics config under Custom Page Code I check to see if that dataElement is 0 and if so, I return false;

 

var firePage = _satellite.getVar('firePage');
if (firePage != "1") {
_satellite.notify('do not fire page',1);
return false;
} else {
_satellite.notify('ok to fire page',1);
}