DEV Community

_s._hyn
_s._hyn

Posted on

7 Things About Developer Marketing That Nobody Warns You About

I sent the same link to three Slack channels last Tuesday and realized I had zero way of knowing which one drove the 47 signups I saw that morning. Honestly, it was a bit of a panic - I had been using the same link for weeks, and suddenly I had no idea what was working and what wasn't. The thing is, I'd been using plain old curl to test my links, but that wasn't giving me any insights into who was actually clicking on them.

Why curl wasn't enough

I'd been using curl to test my links for months, and it had always seemed like enough - I could see if the link was working, and that was all I needed, right? But as it turned out, that was only half the story. I was using a simple Python script to generate my links - just a basic requests call to the destination URL - but that wasn't giving me any information about who was actually clicking on the links. I was essentially flying blind, with no way to know which channels were driving the most traffic. I tried adding some logging to my script, but that just gave me a bunch of IP addresses and user agents - not exactly the most useful information.

The spreadsheet that saved my sanity

I decided to try using a URL shortener to get some more insights into my link traffic. I was looking at the device breakdown in LinkCut and noticed that a huge proportion of my traffic was coming from mobile devices - which was surprising, because I'd assumed that most of my users would be on desktop. (I mean, who uses their phone to sign up for a developer service, right?) But it turned out that was exactly what was happening - and once I started optimizing my landing page for mobile, I saw a big increase in conversions. This was weird, because I'd always assumed that mobile traffic would be lower-quality - but it turned out that was just a bias on my part. I also started using custom slugs for my links, which made it way easier to keep track of which link was which - instead of having to deal with a bunch of random characters, I could just use something like /my-link and know exactly what it was.

What actually worked

Using LinkCut to track my links was a game-changer - I could finally see which channels were driving the most traffic, and which links were actually converting. I was surprised to find that one of my Slack channels was driving way more traffic than the others - and that was mostly because I'd posted a link to a popular subreddit, which had sent a bunch of traffic my way. I didn't expect this, because I'd assumed that my other channels would be more effective - but it turned out that was just a mistake on my part. I also found that setting an expiration date on my links was really useful - it meant that I could create links that would only be valid for a certain period of time, which helped me avoid having to deal with stale links.

When this approach falls apart

Look, I'm not going to lie - using a URL shortener isn't always the right choice. If you're dealing with a huge volume of traffic, it might be better to just use a custom solution - and if you're working with sensitive data, you'll want to make sure that your shortener is secure. (I still don't fully understand why some shorteners are more secure than others - but I'm working on it.) And of course, there are always going to be cases where you need more advanced analytics - in which case, a simple URL shortener might not be enough. I'm not sure this is the best approach for every use case, but it worked for me - and that's all I can really say.

The thing is, I'm still figuring out how to use LinkCut to its full potential - and I'm not sure what other features it has that I'm not taking advantage of. Has anyone else hit this exact wall - where they're using a URL shortener, but not really getting the most out of it?

Top comments (0)