How to track traffic from LinkedIn


If you've shared your Lickstats campaign link on LinkedIn, you may have noticed that it does not get tagged as a source in your Lickstats campaign link stats.

Instead, it will be marked as a Direct referral. This can be frustrating but there is an easy way to work around this with Lickstats.

UPDATE: as of 25 July 2019, LinkedIn has updated their code base in such a way that referral tracking is no longer a problem.

We have left this Help Center post without modification for now, and the steps are still relevant for any other source you come across that doesn’t seem to tag referral sources as you’d expect. If you’re curious about what LinkedIn has changed, we explore it in depth on our recent blog post: LinkedIn reinstates referral tracking.


Why does Lickstats not tag LinkedIn as its own source like it used to?


Just the other day, we noticed that our recent blog post didn’t identify LinkedIn as a source. This, despite LinkedIn being the channel on which we found our greatest engagement. If you discover an unexpected volume of Direct traffic in your own campaigns, this might be why!

It turns out that LinkedIn has recently begun stripping out all referral data from links posted on their platform, regardless of whether that link came through a URL shortener or not. For what it's worth, we admire their increasing attention to user privacy but it makes life difficult for digital marketers.

When you come across a situation like this, Lickstats segments become particularly useful.


How to track traffic from LinkedIn


STEP 1 - Simply create a Lickstats segment under your campaign link that you will use specifically for LinkedIn and you’re all set! We recommend using /lnkd as the segment name.


STEP 2 - Filter your stats by the lnkd segment and you will see all your traffic originating from LinkedIn as a separate source.


Use the same trick for email


A similar use case is email. If you wish to track clicks originating from emails, the only consistent way of tracking them is by using a Lickstats segment such as /email.

Zane Pocock