Campaign Links — Overview

When you send a bulk email from your CRM, the recipient clicks a link and lands on your site — but by default you have no idea *which* individual clicked. Redsun's campaign links solve this by giving each email recipient a unique, short URL on your own domain. When they click, Redsun identifies them server-side, sets a 90-day cookie, and redirects to your chosen landing page. From that point on, every page they view is attributed to them as a Known Visitor.

Redsun supports two mechanics and chooses automatically based on which CRM you have connected: • **Pre-write path** (JobAdder, Loxo, Atlas) — Redsun mints one unique URL per contact and writes it into a custom contact field on your CRM. You merge that field into your email like `{{firstName}}`. No per-CRM merge-syntax gymnastics. • **Native-merge path** (Firefish) — Firefish's API doesn't allow custom-field writes, so Redsun gives you one template URL containing Firefish's native `{ContactId}` merge token. You paste it into your Firefish email once; Firefish substitutes at send time. Both paths land on the same worker route, set the same cookie, and feed the same Known Visitors dashboard.

Campaign URLs live on your tenant domain — they look like a normal link to your site: ``` https://yourdomain.com/client/q1-hiring-Abc12345 (pre-write: opaque slug) https://yourdomain.com/hiring/q1-hiring/{ContactId} (native-merge: Firefish) ``` The `/client/` prefix is used for campaigns sent to *clients* (hiring managers), and `/hiring/` for campaigns sent to *candidates* (job-seekers). Under the hood both paths route through the same Cloudflare worker handler — the prefix is a signal to the recipient, not the destination.

On click the worker: (1) matches the URL shape, (2) resolves the slug to the contact + campaign, (3) sets a first-party `rs_vid` cookie on your domain (90-day lifetime, SameSite=Lax), (4) records the click event, then (5) 302-redirects to the destination page you chose at campaign-launch time (Hiring landing page, Candidate apply form, Homepage, etc.). Because the cookie is first-party on your own domain, every subsequent page visit is attributed to the same contact — no tracking pixels, no cross-site cookies, no GDPR grey area.

Open the CRM-specific article that matches your integration: • **Loxo** — Campaign Links for Loxo • **JobAdder** — Campaign Links for JobAdder • **Atlas** — Campaign Links for Atlas • **Firefish** — Campaign Links for Firefish Each walks through the one-time setup and the per-campaign workflow for that CRM.