← All teams

ShortFreeURL for Agencies

Client separation, client domains and reporting you can hand over.

Agencies need the same platform to serve many clients without their work mixing. That means separate teams, separate domains, separate reporting, and the ability to hand a client their data or their whole link library without a negotiation.

One client, one team

An organisation can hold several teams, and each team has its own domains, folders, members and reporting. That is the cleanest way to run client work: nobody sees another client's links, and reporting scopes naturally.

Members can belong to more than one team, so an account manager working across three clients does not need three logins.

Links on the client's domain

Client links should carry the client's brand, not yours and not a generic shortener's. Connect the client's domain or a subdomain of it, and certificates are issued and renewed automatically.

It also makes handover clean: if the relationship ends, the domain and its links belong to the client, and the redirects continue to resolve.

Conventions that scale across accounts

Saved UTM presets and folder defaults let you apply the same naming discipline across every client without briefing every junior on every account. New links inherit the campaign, source and medium values from the folder they are created in.

Bulk creation and bulk editing handle campaign setup and mid-flight corrections at the scale agencies actually work at.

Reporting clients can read

Reports scope to a link, folder, tag, campaign or domain over any date range, with period comparison. Bot and human traffic are separated, which prevents the uncomfortable conversation about launch-day numbers that were mostly scanners.

Conversion tracking joins clicks to outcomes with values, so a report can talk about results rather than traffic.

Giving clients access, safely

Read-only roles let a client see their own numbers without the ability to change anything. Per-link permissions protect links that are already printed or live in paid media.

Because access is scoped to a team, giving a client a login never exposes another client's work.

Onboarding and offboarding

New clients arrive with an existing link library. CSV and XLSX import bring it in, and a dedicated Bitly import preserves existing short codes so shares that are already in the world keep resolving.

When work ends, everything exports — links, settings and analytics — so handover is a file rather than a favour.

Questions

Can we keep clients completely separate?

Yes. Each client gets its own team with its own domains, folders, members and reporting scope.

Can links run on our client's domain?

Yes, and they should. Connect their domain or a subdomain with automatic SSL.

Can clients log in to see their own numbers?

Yes, with a read-only role scoped to their team so they see their work and nothing else.

What happens if a client leaves?

Export everything and hand it over. Because the links live on their domain, redirects continue to resolve.

Can we bring across a client's existing Bitly links?

Yes, there is a dedicated Bitly import that preserves short codes so existing shares keep working.

Run every client on their own domain, in their own team.

Start Free — no credit card

The free plan includes 1,000 links, 6 custom domains and 50,000 tracked clicks a month, free forever. Choose a free subdomain from six shared domains. Paid plans start at $4 a month when you outgrow it, and you keep everything you have built.