Campaign Links — Identifying Email Recipients
How Redsun identifies the individual who clicked a link in your CRM's bulk email, and how to set it up.
Why campaign links exist
When you send a bulk email from your CRM, someone clicks and lands on your site — and by default you have no idea which recipient it was. Campaign links solve that by giving each recipient a unique URL on your own domain. On click, Redsun identifies them server-side, sets a first-party cookie, and forwards them to the page you chose. From then on their browsing is attributed to them in Signals.
Two mechanics, chosen for you
Redsun picks the mechanic based on the CRM you've connected: • **Pre-written links** (JobAdder, Loxo, Atlas) — Redsun mints a unique URL per contact and writes it into a custom field on their CRM record. You merge that field into your email like any other. • **Native merge** (Firefish) — Firefish's API doesn't allow custom-field writes, so Redsun gives you one template URL containing Firefish's own `{ContactId}` merge token. Paste it into your Firefish email once and Firefish substitutes at send time. Both land on the same route, set the same cookie, and feed the same dashboard.
Set it up from Signals
Open the **Signals** hub. The setup banner — **Get Visitor Intelligence working** — walks three steps: 1. **Connect your CRM** 2. **Add the tracking field in {your CRM}** — pick an existing text field from the list Redsun reads out of your CRM, or click **Create it for me** and Redsun adds one. It then verifies it can write to it. 3. **Activate** On Firefish, step 2 is skipped: it uses the native `{ContactId}` token, so there's nothing to create.
Once the field is verified you can change it later with **Reconfigure field** if you ever move it in your CRM.
If the field list won't load
Redsun reads your CRM's custom fields over the same connection it uses to write tracking links. If it can't read the list, reconnecting the CRM is the fix — a field ID typed in by hand would fail in exactly the same way.
Contacts without an email address are skipped. Redsun uses email as the identity it matches on.
What the click does
On click the worker resolves the link to a contact and campaign, sets a first-party `rs_vid` cookie on your own domain (90 days, SameSite=Lax), records the click, and redirects to the destination page. Because the cookie is first-party, every later page view is attributed to the same contact without third-party tracking.
Test before you send
Always send yourself a test. On the pre-written path, the merge field should resolve to a URL rather than printing the field name. On Firefish, the final segment of the URL should be a real contact ID rather than the literal `{ContactId}` — leave that token exactly as given, because Firefish is case-sensitive on merge tokens.
Guide complete
You've covered all 6 steps. Check out the related guides below.
Still need help?
Our support team is here to assist you.