Solved

Disable clkn Wrapper

  • 1 December 2015
  • 34 replies
  • 1312 views


Show first post

34 replies

Hi Adam, I’ve used a custom script to remove the clkn wrapper which solved the issue with GA tracking & conversions. However, you won’t be able to track Unbounce conversions. For us, this was not an issue since we simply set up conversions through GA.

(Remove the --s from the script below)

<–script–>
lp.jQuery(function() { (‘a[href]’).each(function(){
(this).attr('href', (this).attr(‘href’)
.replace(/clk(n|g)/https//, ‘https://’)
.replace(/clk(n|g)/http//, ‘http://’)
.replace(/clk(n|g)/tel//, ‘tel:’));
});
});
<–/script–>

Any progress on this? @sberman is absolutely right that this breaks Google Analytics cross-domain tracking.

Hi Justin, I know your post was from a year ago but I just wanted to mention that the clkn wrapper does disrupt cross-domain Google analytics tracking.

Any update here on disabling the clkn wrapper?

Thank you! This was just what I needed also for integration with CallRails to work.

Yes, one way to remove the clkn wrapper is using the custom HTML element. Unbounce does not apply tracking to links in that code base. I’m doing this now because I don’t want the click wrappers on links for SEO purposes.

Hi Folks! 
There isn’t any way to disable the  clkn wrapper at this time, as we use those clkn and clkg wrappers to keep track of stats for links and then use a 300-redirect once the appropriate count is fired back to Unbounce. Can you let us know if you’re running into any issues with these wrappers and reaching your goal? 

Hi Mark,

the use of the Clkn wrapper could be a vulnerability issue for someone (such as a bank), since it may induce some hacker to make open redirect attack . It would be useful to be able to decide which links or buttons use the Clkn wrapper, with the possibility of excluding it if needed. It’s possible?
Thank you for your answer

Joe

Hi Andi,

Curious to know why you would need this ability. 🙂

Mark

Reply