About VvdIm

VvdIm is an independent blog focused on the practical side of URL shortening, link tracking, and marketing attribution. I started writing here because I kept running into the same problems in real projects — and I couldn't find clear answers that weren't buried in vendor documentation or wrapped in affiliate recommendations.

Everything published here comes from actual implementation work. If something didn't work the way the docs described, I write about that too.

Who's Behind This Site

My name is Horim, and I'm a developer based in Seoul, South Korea. I've spent the last several years building web services — including vvd.im, a URL shortener I built and operate myself. Along the way, I've integrated Google Analytics, set up UTM workflows, debugged broken attribution pipelines, and watched redirect chains quietly corrupt conversion data.

I'm not a consultant selling services. I'm a practitioner who got tired of half-finished tutorials and decided to document what actually works — and what doesn't — for anyone dealing with the same stack.

What This Blog Covers

The articles here focus on five areas that tend to be tightly connected in real-world marketing and analytics setups:

  • Short URLs — how redirect behavior affects tracking, which HTTP status codes matter, and how to build reliable link shortening without losing attribution data
  • Link Tracking — UTM parameters, click tracking setups, and common places where tracking breaks silently
  • Google Analytics — GA4 configuration, event structures, and debugging sessions when the data doesn't match expectations
  • Attribution — how traffic sources get credit (or don't), and why the same campaign can look very different across tools
  • Conversion Tracking — integrating goals, understanding assisted conversions, and making sure your reporting reflects what actually happened

I try to write guides that are honest about complexity. Most of these systems interact in ways that aren't obvious, and I'd rather explain the real trade-offs than give you a five-step setup that falls apart in edge cases.

How I Approach These Articles

I don't write from documentation alone. Each guide starts with a problem I've actually encountered — or one a reader has brought to me — and works through the implementation with specific configurations, code where relevant, and honest notes on what caused problems.

There are no affiliate links on this site. I don't accept sponsored posts or get paid to recommend tools. If I mention a service or platform, it's because it was relevant to the problem I was documenting.

Get in Touch

If you've run into something that's not covered here, found an error in one of my guides, or have a different approach to a problem I've written about, I'd genuinely like to hear it. You can reach me through the contact page. I read everything and try to respond when I can.