JournalTracking and ads

Why your paid clicks keep showing up as direct traffic

A waitlist launch spent on ads and saw the visits land in the wrong bucket. The fix was to remember where people came from.

A hand holding a compass over an orienteering map in a wood.

FlightCounter was a travel start-up collecting a waitlist. Paid ads were driving people to the page, and the analytics said much of that traffic was direct. Direct means someone typed the address or used a bookmark. It does not mean an ad worked on them, and that was exactly the problem.

Where the source goes missing

When someone clicks an ad, the link carries tags in the address, called UTMs. They say which campaign, which source, which medium. The first page sees them. But if the visitor moves to a second page, or the form submits through a redirect, or the browser strips the referrer, the tags are gone before the sign-up is recorded.

So the sign-up arrives with no memory of the ad. Analytics files it under direct.

Remember it on arrival

The fix is plain. Read the UTMs from the address the moment the visitor lands, store them, and send them with the sign-up whenever it happens. We also made the stored UTM win over the browser's referrer, because a stored campaign is more specific than the page the visitor came from.

The same project sent branded transactional email with SPF, DKIM and DMARC set up, so the confirmations arrived from the studio's own domain and not into spam.

A short checklist

  • Tag every ad link with source, medium and campaign.
  • Store the tags on the first visit, in a first-party cookie or the session.
  • Attach them to the form submission, not just the page view.
  • Prefer the stored tag over the referrer when both exist.
  • Look at your direct traffic after a campaign. A sudden rise is a warning.

If you cannot tell which of your campaigns produced which sign-ups, you cannot tell which ones to fund. Fixing that is cheaper than another month of guessing.

Photograph from Unsplash.

Bring us the account that is stuck.

Replies usually within 6 hours. Remote, working across UK, EU and US Eastern hours from UTC+1.