Drip

Rekomi's Drip integration adds every approved affiliate to your Drip account with tags. Drip is account-wide with no list picker, tags drive segmentation.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /v2/{accountId}/subscribers with:

{
  "subscribers": [{
    "email": "...",
    "first_name": "...",
    "last_name": "...",
    "tags": ["Rekomi affiliate", "..."]
  }]
}

The endpoint is safe to retry: re-syncing returns 201 with the existing subscriber updated. Tags are additive (re-applying the same tag is a no-op).

Finding your credentials

In Drip:

1. User Settings → API. Copy your Personal Access Token.
2. Your Account ID is the number in your Drip dashboard URL (e.g., https://www.getdrip.com/1234567/...).

Connecting Drip in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the Drip card.
3. Paste your API token and Account ID. Click Connect.
4. Rekomi runs a test call against GET /v2/accounts/{accountId} to verify both credentials.

Tags

Comma-separated. Each tag becomes a Drip tag on the subscriber. The Rekomi affiliate system tag is always applied.

Double opt-in

POST /v2/{accountId}/subscribers does NOT trigger Drip's double opt-in email, affiliates land as active immediately. This is intentional: affiliates already opted in by accepting your program in Rekomi.

If you also enroll affiliates into a Drip campaign manually (via Drip's UI or another API), that campaign's own double opt-in setting applies, Rekomi has no control over that.

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

• custom fields 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 affiliates.

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

• account_id_invalid, Account ID must be numeric. Re-copy from your Drip URL.
• 401, API token is invalid or doesn't have access to that Account ID. Re-copy the token from User Settings → API. 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.
• 429, Drip throttles at 3,600 req/hr. Rekomi's worker pace is well under this.
• Subscriber landed but no tags, Drip's per-tag failures don't undo the subscribe. Check the affiliate's CRM sync panel for the specific tag-attach error.

Disconnecting

From the Drip connect page, click Disconnect. The integration row and per-campaign overrides are deleted. Historical sync history rows are preserved for audit.

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