since ‎18-11-2016
‎10-12-2019
davidp86482746
Level 1
Re: Fire analytics only on certain pages...
Avatar

davidp86482746

davidp86482746
- Dynamic Tag Management
Actually, the advice has changed, so my initial method would appear to be correct, although I'm still not seeing the expected results in my reporting.In my original post I was using the following logic:if(document.location.href.indexOf("whatever")!=-1){ return false}As I'm trying to fire Analytics only where "whatever" is present in the URL, this was slightly incorrect, as the comparison operator should have been == and not !=. The guidance from customer care is: You can navigate to Analytics to...

Views

189

Like

1

Replies

0
Re: Fire analytics only on certain pages...
Avatar

davidp86482746

davidp86482746
- Dynamic Tag Management
Thanks Alexis-- customer care confirms this as the correct solution, although I'm still not seeing the results that I would expect. I'll follow up with any additional insight once I have a complete solution. I would imagine that the issue lies with me and how I'm setting up the rules/conditions, rather than this approach itself.

Views

188

Likes

0

Replies

0
Fire analytics only on certain pages...
Avatar

davidp86482746

davidp86482746
- Dynamic Tag Management
Is it possible to have Analytics fire only on certain pages? I tried adding a path condition in DTM to the page load rule, but that didn't seem to make any difference at all. I'm now trying to accomplish the same result by deactivating the beacon via the following custom code:if(document.location.href.indexOf("whatever")!=-1){ return false}Does anyone have any tips on what the actual best way to have Analytics only fire on certain pages?

Views

1.2K

Likes

0

Replies

5
Likes from