adobe - Receiving unexpected server calls -

in adobe analytics try implement link tracking links can found in page using this:

$(document).on('click', 'a', function() {      s.tl(this, 'e', 'external', null, 'navigate');      return false;  }); 

try test using page

the calls coming how have adobe analytics configured. there handful of config variables cause requests depending on how set them (on own and/or in relation each other).

here listing of adobe analytics variables reference. these ones at:

s.trackdownloadlinks - if enabled, standard links href value ending in value(s) specified in s.linkdownloadfiletypes trigger request on click. generally, enable automatic tracking links prompt visitor download (e.g. pdf file).

s.trackexternallinks - if enabled, standard links href not matched in s.linkinternalfilters or matched s.linkexternalfilters trigger request on click. generally, enable automatic tracking links count visitor navigating off site(s).

s.linkinternalfilters - if have either of above enabled, clicking on links may trigger request, depending on values here vs. enabled above vs. have in s.linkexternalfilters. generally, should include values represent links not want count navigating off site(s).

s.linkexternalfilters - if have either of above enabled, clicking on links may trigger request, depending on values here vs. enabled above vs. have in s.linkinternalfilters. generally, should never set this. it's intended edge-use-cases people know doing , have complex site eco-system , definitions of counts internal vs. external.

s.trackinlinestats - clickmap/heatmap tracking. may or may not trigger request, depending on how lot of different stars align.

in addition these, may have plugins or other custom code triggers click tracking. example, there linkhandler, exitlinktracker, , downloadlinktracker plugins may have included in code may play part in requests being triggered.

finally, more recent versions of adobe analytics code may trigger multiple requests depending on how data trying send in request (whereas older versions truncated request, resulted in data loss).

in case, long story short here if looking roll own custom link tracking, should make sure above variables/plugins removed or otherwise disabled.

but on note of rolling own custom link tracking.. i'm getting sense of de ja vu here, made comment relatively in post, on exact same code... speaking, not idea:

        $(document).on('click', 'a', function() {              s.tl(this, 'e', 'external', null, 'navigate');              return false;          }); 

you wholesale implementing exit link tracking on every single link of page. , giving them same generic "external" label. , native exit link reports pretty limited , useless begin with, ideally should pop evar or exit url or something.

but more importantly.. unless literally every single link on pages links navigate visitor off-site, not going useful in reports in general, , it's going ruin lot of reports.

i can't believe (or accept) really want count every link on pages exit links..