Trackable Link and QR Hub Automation: A Code That Outlives the Destination Behind It

A QR code or a shared link is usually generated once and then lives far longer than expected — printed on a flyer, painted on a storefront window, saved in a client's WhatsApp history, embedded in a signed approval email. The moment the destination behind it needs to change — a new landing page, a corrected form, a different campaign — a QR code pointing straight at the old URL is now permanently wrong, and nobody can quietly fix it without reprinting or resending everything that already carries the old code. On top of that, most ad hoc links generated for a client or a campaign carry no tracking at all: a WhatsApp message gets sent, a QR code gets handed out, and whether anyone actually engaged with it is anyone's guess.

Generating a one-off shortened link or a QR code is fast, and adding real tracking to it is not — building a redirect that logs an access, updates a click count, and respects a pause or expiry state is meaningfully more engineering than pasting a destination URL into a free QR generator. Most agencies either accept the lack of tracking as the cost of speed, or reach for a separate, unrelated tool just for link shortening and link-in-bio pages, which then lives outside whatever system already tracks the client, the campaign and the deliverable it belongs to.

Every link created inside Run's Central de Links gets a unique six-character code stored in the run_links table, reachable at a public, unauthenticated route on Run's own domain. A link carries one of four types — WhatsApp (a pre-formatted wa.me link with an auto-encoded message and an automatically applied Brazilian country code), QR Code (a general link whose main purpose is generating a scannable code), Approval (for review and validation flows) or Custom (any destination with commercial context attached) — plus optional metadata: the associated client, campaign, source channel, responsible person and internal notes. When someone visits the short link's public route, the front end calls a database function running with elevated, server-controlled privileges, using only the public key, since the route is intentionally open with no login required; that function checks the link's status and only then inserts an access record and returns the real destination for the browser to redirect to. A link marked Paused or Expired is not redirected and is not counted — the block happens inside that same database function, not merely in the interface, so it cannot be bypassed from the client side. Generating a QR code for a link deliberately encodes the trackable short URL rather than the final destination URL, specifically so that the destination can be changed later — a new landing page, a corrected offer — without a single physical QR code needing to be reprinted or reissued; the code falls back to the raw destination only if a trackable URL is genuinely unavailable. Every access — and, separately, every access to a Link Space page and every click on one of its buttons — is logged with a truncated referrer and user agent, and an automatic trigger increments a click counter and a last-accessed timestamp on the parent record; the module's own documentation states plainly that IP addresses are not collected in this version. A Link Space is a distinct kind of resource inside the same system: a public, multi-button page reachable at its own short URL, built for campaigns, events or a single client-facing hub of several destinations at once — WhatsApp, Instagram, Facebook, a website, Google Business Profile, a catalog, a form or an approval link, each as its own button with its own click count, and the whole page carrying its own separate view count. A dedicated statistics view shows total page views, total clicks, the last access, a per-button click breakdown with a proportional bar, and the twenty most recent individual accesses. Five permissions gate the whole feature — view, create, edit, pause and delete — with different default access for admin, manager, executor and client-contact roles, and the public redirect and Link Space pages themselves display only generic status messages, never internal metadata like the owning organization or the responsible person.

An agency prints a QR code on in-store signage for a client's seasonal promotion, generated from a Central de Links custom link pointing at that season's landing page. Over the following weeks, the tracking dashboard shows a real, growing click count on that specific code — evidence the physical signage is actually driving traffic, not just a guess.

The season ends and the client needs the same signage to point at a different, permanent page instead. Because the printed QR code encodes the trackable short link rather than the original landing page directly, the agency simply edits the link's destination in Central de Links — the physical signage does not need to be reprinted, and the click count keeps accumulating on the same historical record rather than resetting. Separately, the same client gets a Link Space page built for a launch event, bundling a WhatsApp contact button, an Instagram link, and a "reserve your spot" form button on one page; the stats view afterward shows the form button drew noticeably more clicks than the Instagram link, a specific, real signal about where interest actually went that a plain flyer could never have produced.

A QR code printed once survives a destination change without a reprint, because the physical artifact encodes a stable short link rather than a URL that expires with the campaign. Every link and every Link Space produces a real click or view count instead of an untracked guess about engagement, and a paused or expired link stops counting the moment it is deactivated rather than continuing to silently accumulate hits nobody trusts anymore.

An agency that never reuses a printed QR code or a shared link across more than a single, short-lived context has little need for the destination-swap protection this system is built around — the value shows up specifically when a link or a code needs to outlive the exact destination it originally pointed to.

A QR code or link pointing straight at a destination URL works exactly until that destination needs to change, at which point every physical or shared copy of it becomes permanently wrong. Centriu Run's approach adds one layer of indirection on purpose — a stable short code that can be repointed — plus real click and view tracking that a plain destination URL never had in the first place.