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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

DTM: trackDownloadLinks, trackExternalLinks don't fire via Adobe Analytics integration

Masaharu_Hachiy
Level 2
Level 2

Hi,

I'm trying to implement Adobe Analytics via DTM.

Regular "s.t()" functions well, but for some reason trackDownloadLinks and trackExternalLinks don't fire.

My settings are bellow.

 

Tools

Adobe Analytics

General settings

Load Adobe Analytics page code at : Page Bottom (tried both Page Top and Page Bottom)

s_code : Managed (tried both Legacy code and AppMeasurement code)

Link Tracking settings

Track download links : checked

Track outbound links : checked

* I also tried to configure those settings on the managed s_code, but it didn't work too.

s.trackDownloadLinks=true;

s.trackExternalLinks=true;

s.linkDownloadFileTypes='exe,zip,wav,mp3,mov,mpg,avi,wmv,pdf,doc,docx,xls,xlsx,ppt,pptx';

s.linkInternalFilters='javascript:,mydomain.com';

 

Are there any fault on my settings?

I will appreciate any help.

 

Masaharu

1 Accepted Solution
sdiadam
Correct answer by
Level 2
Level 2

These should work just fine out of the box.  Check your s_code to see if you have any unique configurations for these, such as using the s.linkHandler, s.downloadLinkHandler, or s.exitLinkHandler plug-ins.  If you are, remove them just in case.  If you have the link settings configured in the s_code, it will trump any settings you have in DTM.  Otherwise DTM's settings will be applied.  If you still have issues try getting rid of your current s_code and instead pasting a brand new copy of the AppMeasurement code without adding any additional settings.  This includes creating the s object in the code.  This will allow DTM to do everything for you.  It should work.  Then you can add your customized code and if it doesn't work you'll have to troubleshoot to see what code is causing the problem.

View solution in original post

8 Replies
sdiadam
Correct answer by
Level 2
Level 2

These should work just fine out of the box.  Check your s_code to see if you have any unique configurations for these, such as using the s.linkHandler, s.downloadLinkHandler, or s.exitLinkHandler plug-ins.  If you are, remove them just in case.  If you have the link settings configured in the s_code, it will trump any settings you have in DTM.  Otherwise DTM's settings will be applied.  If you still have issues try getting rid of your current s_code and instead pasting a brand new copy of the AppMeasurement code without adding any additional settings.  This includes creating the s object in the code.  This will allow DTM to do everything for you.  It should work.  Then you can add your customized code and if it doesn't work you'll have to troubleshoot to see what code is causing the problem.

View solution in original post

Harsh_Kabra
Level 4
Level 4

Download and Exit link tracking works Automatically by the out-of-box s_code. Try to eliminate the issue between DTM of s_code config as suggested in the previous comment. Also, make sure that the domain name (exit link domain) is not included in s.linkInternalFilter in your s_code file hosted on DTM.

Regards,

 Harsh Kabra |  Adobe Certified Expert: Digital Analytics® & SiteCatalyst Implementation & Reporting®

Masaharu_Hachiy
Level 2
Level 2
Hi, sdiadam, Harsh.
 
According to your advise, I swept my s_code clean and it worked!
Some of my configurations on s_code and DTM were contradicted each other. 
Thanks for you advise!
adam_haining
Level 2
Level 2

Glad that helped.  However, there is a recent update that came out in DTM that will allow you to apply certain configurations before or after the DTM configurations.  These can be found at the bottom of the Adobe Analytics tool configuration in the section titled "Customize Page Code".  You'll see there are now 2 options:

  1. B
  2. After UI settings (custom code takes precedence)

​Here you can see that you can specify if the UI or the code is going to trump the other.  Just note that you must put the code in this section, and not in your s_code file.  When you enter the code in this section, always use "s" as the object, even if you have set it up to be something else.  DTM will always refer to "s" in any custom code.  It refers to it locally, not globally, so it is safe to do so.

julià_pujol_ar1
Level 2
Level 2

Hi Adam,


I'm concerned after read your post, I've a couple of question about your words:

- On "Costomize Page Code" section, must use a "s" object instead "smetrics" (my object declared in DTM)?

- On Adobe Analytics Rules, If I use custom code, should I use a "s" object also? Same for Data Elements?


Many thanks for your help,


Julià.

Harsh_Kabra
Level 4
Level 4

Thanks for the update Adam, looks like Adobe is listening to their Audience and acting very swiftly. In fact, I did mention in few of my posts in the public domain and wished to have such option in DTM which can let you execute Before/After UI Settings in DTM. Glad that we got one. I will test it and post my review comments in the forum soon, for the benefit of other DTM users.

Regards,

Harsh Kabra

Harsh Kabra |  Adobe Certified Expert: Digital Analytics® & SiteCatalyst Implementation & Reporting®

adam_haining
Level 2
Level 2

Hi Julia,

Yes, although you may have declared the global object as "smetrics", you will still want to use "s" when referring to any custom code block.  This applies to the customize code section in the Adobe Analytics tool settings, as well as the customize code section for Adobe Analytics in any rules.  You most likely will never refer to Adobe Analytics code outside of these sections, but if you do refer to it from a 3rd party tag, you will need to make sure it is "smetrics".  The reason is that in these custom code sections, DTM is actually creating a function, and the "s" object you defined (in this case "smetrics") will be passed as "s" in the parameter of this function.  For example, when the custom code gets created, it will look something like this (although this is very simplified):

function customJS(s){
  s.linkInternalFilters="javascript,tel:,domain.com,"+document.domain;
}

Then when the custom code section gets called, it will be called like this:

customJS(window.smetrics);

In the custom function, it passes your "s" object, which the function has defined as "s".  That way you can update any settings, regardless of what you are using.  The key is that you always refer to it as s.  Also, never do something like this in the code, although there might be others that say to do this, even some Adobe documentation or videos.

var s = window.smetrics;

julià_pujol_ar1
Level 2
Level 2

Grand Explanation Adam,

It is those kind of things that Adobe guys must be explained on DTM documentation, It's important know this.

Many, many thanks for your help,

Julià,