Omnisend

Rekomi's Omnisend integration creates or updates contacts in your Omnisend account. Omnisend is account-wide (no list picker) and uses tags + segments for organization.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /v3/contacts with the identifier-based body shape Omnisend expects:

{
  "identifiers": [{
    "type": "email",
    "id": "...",
    "channels": { "email": { "status": "subscribed", "statusDate": "..." } }
  }],
  "firstName": "...",
  "lastName": "...",
  "tags": ["Rekomi affiliate"]
}

The endpoint is upsert, existing email returns 200; new email returns 201.

Finding your API key

In Omnisend:

1. Account → Integrations → API Keys.
2. Create a new key. Copy it.

Connecting Omnisend in Rekomi

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

Tags

Comma-separated. Omnisend accepts the tags array inline (max 100). Rekomi sends the Rekomi affiliate system tag plus any defaults you configure.

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 Omnisend as well, matched on email so existing contacts are updated, not duplicated. Each one carries:

• custom properties rekomi_referral_link, rekomi_campaign, rekomi_referring_affiliate, rekomi_referring_affiliate_code, rekomi_last_event, rekomi_last_sale_amount
• 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 the Settings tab and scroll to "CRM sync for this campaign".

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

• 401, API key invalid. Re-copy from Integrations → API Keys. Repeated auth failures mark the integration "action needed" and trigger a reconnect email once per breakage; after reconnecting, use Resync all on the Failed tile of the integration page.
• 400, Identifier shape malformed. This is internal; contact support.
• 429, Rate limited. Omnisend does not publish an RPS limit; Rekomi falls back to exponential backoff.

Disconnecting

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

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