WebmasterID logoWebmasterID
Referrers

ow.ly (Hootsuite) shortener referrer

ow.ly is the link shortener associated with the Hootsuite social-scheduling platform. Links shortened with ow.ly redirect to the destination, so the referrer often shows the shortener host or nothing — and crucially does not tell you which social network the post ran on. This page explains the mechanics and the UTM approach for scheduled social links.

Verified against primary sources

What an ow.ly referrer tells you (and doesn't)

ow.ly is the shortener used in the Hootsuite ecosystem for scheduling and posting links to social networks. When someone clicks an ow.ly link, the shortener issues an HTTP redirect to the destination, and the referrer the browser sends reflects that redirect rather than the social post itself.

The important limitation is that an ow.ly referrer is network-agnostic: the same shortener fronts links posted to multiple networks, so the referrer alone cannot tell you which network drove the click. Many social clicks also originate in apps that send no referrer, leaving only the redirect or direct traffic.

Tagging scheduled social posts

Because the shortener flattens every network into one referrer (or none), distinguish networks at the destination. Give each scheduled post a destination URL tagged with utm_source for the network and utm_medium for the channel type (for example social or paid-social), then shorten that tagged URL.

The query string passes through the ow.ly redirect to your page, so analytics records the correct network and campaign for every scheduled post — something the referrer can never reliably provide for shortened social links.

How it appears in analytics and logs

An ow.ly referrer means the click came through a Hootsuite-associated shortener redirect. It does not reveal whether the click came from a post on one network or another; when no referrer arrives, the source is invisible entirely.

Diagnostic use case

Understand why an ow.ly referrer does not identify the social network a scheduled post ran on, and tag each post's destination so the network and campaign are measurable.

What WebmasterID can help detect

WebmasterID reads UTM parameters that survive the ow.ly redirect, so a scheduled post whose destination carries utm_source and utm_medium is attributed to the right network even though the referrer is the shortener or absent.

Common mistakes

Privacy and accuracy notes

Shortener and redirect behaviour produces missing or generic referrers by design; this is not a tracking gap to be closed by identifying visitors. WebmasterID reads the referrer if present and nothing more.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.