Campaign Links for Firefish

Unlike JobAdder, Loxo, and Atlas, Firefish's public API doesn't expose a way to write custom-field values on contacts. So the Firefish path skips the pre-write mechanic entirely. Instead, Redsun uses Firefish's **native `{ContactId}` merge token**. You paste a template URL into your email once; Firefish substitutes the correct contact ID for each recipient at send time; Redsun resolves the ID on click.

Redsun needs your Firefish contacts in its local index (`vie_contact_identities`) to resolve `{ContactId}` values on click. Open the Connections page and confirm Firefish shows Connected with a recent sync.

Open **Intelligence → Campaign Links**, expand a consultant, click **New campaign**: 1. Name the campaign. 2. Pick a destination (landing page or apply form). 3. Click **Launch**. Redsun creates a campaign record with the destination info but doesn't enumerate contacts or mint per-contact tokens — there's nothing to write. Instead, the success state shows a single template URL ready to paste.

The success dialog shows something like: ``` https://yourdomain.com/client/q1-hiring/{ContactId} ``` Copy the raw URL, or use the **Copy HTML** button to get a ready-made `<a>` tag with your link text — that drops cleanly into Firefish's rich-text email editor without mangling the `{ContactId}` token.

In Firefish, open the email template you're sending from (campaign sequence, mailshot, or personal email) and paste the URL (or the HTML link) wherever you want the CTA. At send time, Firefish replaces `{ContactId}` with each recipient's actual contact ID. So a recipient with contact ID `12345` gets a URL like `https://yourdomain.com/client/q1-hiring/12345` — unique to them, same campaign.

Send a test email to yourself via Firefish. On receipt, the link's final segment should be a real number (your own Firefish contact ID), not the literal `{ContactId}`. Click it — you should land on your chosen destination page. If the link still contains `{ContactId}`, the merge failed — most common causes: wrong case, extra spaces, or the email template type doesn't support merge fields (some quick-send modes in Firefish skip merge).

When a recipient clicks, Redsun's worker parses the path, looks up the contact by `external_crm_contact_id`, sets the cookie, and redirects. The click appears in Campaign Links (per-campaign count) and the contact shows up as a Known Visitor — exactly the same as the pre-write path, just resolved via Firefish's native merge instead of a pre-written URL.