Campaign link & codes

Tie a request back to the campaign that drove it. Useful for “did our spring newsletter actually generate requests?”

Who this is for: anyone running campaigns + tracking outcomes.

How it works

• Every campaign has a campaign code (see Campaign codes).
• The public request form reads the code from a ?c=… query parameter on its URL. (Older links that carry ?campaign=<name>&cid=<id> still work.)
• When a campaign links to the request form with the code in the URL, the request that comes in stores the campaign’s id and name.
• In the Requests list such a request carries a via badge with the campaign’s name, and typing the campaign’s name in the search box narrows the list to the requests that campaign drove. The CSV export has a Campaign column.

What staff cannot do

The link is set only by the public form. There is no campaign field on + New request or in Edit request, so a request entered by hand has no campaign, and an existing request’s campaign cannot be added or changed afterwards.

What you’ll see

Common issues

• Request came in with no link — the requester arrived without the ?c= query parameter. They typed the URL by hand or the link in your email was broken. It cannot be linked afterwards.
• Campaign code reused across two campaigns — code-based reporting aggregates across both. Use unique codes per campaign if you need to disambiguate.

Last updated: 2026-06-01 · Applies to: CartonCrew v1.56+