Use case

Agencies

An agency runs links on behalf of brands that are not its own. Every link a client sees should carry the client's name, not the agency's and certainly not a shortener's, and the numbers have to be exportable when the client asks for them or when the relationship ends.

Start for free See every use case

The problem

What gets in the way

Most shorteners price per workspace or per brand, so the bill grows with the client list rather than with the work. And a link on a shared domain ties the client's campaign to a reputation shared with everyone else using that shortener, including whoever is sending phishing through it this morning.

How it works

Three steps with Lua

A domain per client

Point each client's own subdomain at Lua. Their links carry their name, and if they leave they keep working: the mapping moves with the domain.

Tag by account

Group every link by client and by campaign, so a report is a filter rather than a spreadsheet exercise.

Hand the numbers over

Everything on the screens is reachable over the REST API, so a client report can be generated rather than screenshotted.

What's included

Built for this

Custom domains, one per client
Tags per account and campaign
Team members with their own access
REST API for reporting

Where it stops

The honest limit

Lua has one workspace per team rather than a client-switcher, so an agency separates clients by domain and tag rather than by account. That works well up to a point; a very large roster may want a workspace per client.

Other use cases

See how else Lua is used

Use case

Marketing campaigns

Tag every placement before you publish it, and read back which one actually moved. UTM parameters, per-campaign tags, and click data that does not expire.

Explore

Use case