EmailOctopus

Rekomi's EmailOctopus integration adds every approved affiliate to an EmailOctopus list.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls PUT /lists/{listId}/contacts (upsert) with email_address, status: "subscribed", fields: { FirstName, LastName }, and your configured tags (on the PUT upsert, tags travel as a map of tag name to true; existing tags on the contact are untouched).

PUT is the upsert path, POST would 409 on duplicate emails.

Finding your API key

In EmailOctopus:

1. Settings → API keys (emailoctopus.com/developer/api-keys).
2. Click Create a key. Name it "Rekomi".
3. Copy the key.

Connecting EmailOctopus in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the EmailOctopus card.
3. Paste your API key. Click Connect.
4. Rekomi runs a test call against GET /lists?limit=1.

Tags

Comma-separated strings. Tags are applied inline on the upsert, Rekomi includes the Rekomi affiliate system tag plus any defaults you configure. Only the tags Rekomi sends are added; tags already on the contact are left alone.

Field name caveat

EmailOctopus's fields map is keyed by the brand's per-list field tags. The defaults are FirstName / LastName (PascalCase), and Rekomi sends with those names. If you renamed the field tags in your list, the first/last name values will be silently dropped, verify your list's field tags match the default convention, or rename them back to FirstName/LastName.

Referred customers and leads (optional)

Turn on Sync referred customers and leads on the integration page and every sale or lead Rekomi attributes to an affiliate is written to EmailOctopus as well, matched on email so existing contacts are updated, not duplicated. Each one carries:

• list fields Rekomi referral link, Rekomi campaign, Rekomi referring affiliate, Rekomi referring affiliate code, Rekomi last event, Rekomi last sale amount (tags RekomiReferralLink and so on), created on the list on first use
• tags Rekomi customer or Rekomi lead
• Affiliates synced by the section above also get Rekomi referral link, Rekomi campaign and Rekomi affiliate status in the same fields, so you can merge a partner's link into your emails.

Refunded, denied and fraud-quarantined conversions are never pushed, and imported historical conversions are skipped. It is off by default.

When sync fires

• Default: only Approved affiliates sync.
• Optional: turn on "Include applicants before approval" to also sync Pending.

Per-campaign overrides

Each campaign can override the account-level configuration. From a campaign's detail page, open Settings and find the CRM sync for this campaign section.

Per-affiliate sync visibility

Open any affiliate's detail page. The CRM sync panel shows the per-CRM status. Resync clears prior jobs and re-fires the sync.

Troubleshooting

• First / last name not showing on contact, Field tags don't match the FirstName / LastName defaults. Rename in EmailOctopus or check your list's field schema.
• 429, EmailOctopus throttles at 10 req/sec sustained, 100 burst. Rekomi honors X-RateLimit-Retry-After when present.
• Sync fails with 401/403 after working before, The API key was revoked. Rekomi marks the integration "action needed" and emails you a reconnect prompt once per breakage. Reconnect with a fresh key, then use Resync all on the Failed tile of the integration page.

Disconnecting

From the EmailOctopus connect page, click Disconnect. Integration row + per-campaign overrides are deleted. Sync history is preserved.

---

See the emailoctopus integration overview on the marketing site for use-cases, persona fit, and unique automation patterns.