# Build consistent campaign links with Replug—and verify what clicks actually mean

Documentation reviewed: 2026-11-01
Experience: documentation-backed, controlled teaching demonstrations; no company-result claim.

## Build
A campaign-link inventory, one validated tagged URL and a redirect/reconciliation test log.

## Inputs and source
- Audience/problem:
- Existing tool and reason for change:
- Consent/source permission:
- Destination or workflow version:

## Implementation
1. Write the measurement question before creating the link
   Expected output: The inventory names the source, destination, outcome and authoritative record without exposing a person.
   Observed evidence: 

2. Choose a small controlled vocabulary
   Expected output: Two teammates can independently build the same campaign URL from the same brief.
   Observed evidence: 

3. Build the destination URL without losing existing parameters
   Expected output: The output contains variant=a, the chosen UTM keys and #download, with no personal information or double question mark.
   Observed evidence: 

4. Optionally create the managed short link in Replug
   Expected output: The saved link points to the exact destination you reviewed, with the intended UTM values after redirect.
   Observed evidence: 

5. Test the redirect and the landing-page behavior
   Expected output: A human can follow the full path to the correct working destination; the inventory records the observed final URL.
   Observed evidence: 

6. Reconcile clicks, sessions and accepted enquiries
   Expected output: Your report keeps each denominator separate and traces accepted outcomes to the appropriate source records.
   Observed evidence: 

7. Keep the inventory and change history usable
   Expected output: Another teammate can identify the current destination, reproduce the test and restore the prior intended route.
   Observed evidence: 


## Completion checks
- [ ] The measurement question and accepted outcome are defined.
- [ ] UTM values follow a written lowercase convention.
- [ ] The destination preserves legitimate parameters and fragments.
- [ ] The short link, if used, reaches the correct final page on mobile.
- [ ] Clicks, sessions, accepted enquiries and customers remain distinct.
- [ ] The inventory has an owner, tested date and change/recovery record.

## Failure test
- Input:
- Expected failure:
- Actual result:
- Fix and retest:

## Handoff
- Owner:
- Review trigger/date:
- Remaining uncertainty:
- Next Blueprint module:

## Fictional link-inventory starter
Copy these headers into your own private sheet. The example destination is reserved for documentation, not a real funnel.

link_id,owner,destination,source,medium,campaign,content,short_url,last_verified,prior_destination,reason_for_change
ns-checklist-email-01,example-owner,https://example.com/checklist?variant=a#download,newsletter,email,trial-checklist,primary-button,not-created,not-tested,,initial-planning-example

Never mark a URL as live or verified until you test your own actual destination and observed final URL. Keep click requests, measured sessions, accepted enquiries and paid customers in separate columns/reports.