Campaign Tracking
How agencies can manage client links
Agency work dies in personal shortener logins. Give each client a workspace or locked folder, their own host, and a seat that cannot rename every slug.
Zipy editorial · 2026-07-01 · 8 min
Key takeaways
- Separate hosts and folders per client. Do not share one anonymous list.
- Viewer seats exist so a client can read a report without editing production slugs.
- When the retainer ends, pause the campaign. Do not hunt a freelancer’s leftover account.
Stop storing client URLs in a personal login
The failure mode is familiar. A contractor’s Bitly-style list holds last year’s packaging QR. The agency cannot reset the password. The client’s legal team wants the destination changed by Friday. Nobody knows who owns the CNAME.
Put each brand in a workspace or a locked folder with its own hostname. Invite seats instead of sharing one password across a roster. Audit logs tell you who published the bad destination.
Roles that match how retainers work
Owners control domains and billing. Admins create slugs and QR. Members draft. Viewers read the monthly PDF without renaming go.brand.com/sale. White-label-style exports matter when the report should not open with someone else’s product chrome.
Handoff when the contract ends
The client should already own DNS. If they do, the host can point at a new backend and the printed paths survive. Export click rows and a slug list before you lose access. Pause campaigns you no longer operate so a stale landing page does not keep collecting traffic under your name.
IAB: standard terms and conditions
Related: what-are-branded-links · bitly-alternatives-for-small-businesses