Email Marketing Integrations

Audience: Marketing managers and developers connecting Reevix to email marketing platforms.

Reevix can trigger behavioural emails through your existing email marketing platform — automatically, based on what shoppers do (or don't do) on your site.


How It Works

When a shopper triggers a qualifying event (e.g., abandons their cart), Reevix fires a webhook payload to your email platform. Your platform then sends the email using your own templates, sender domain, and branding.

Reevix handles: Event detection, payload formatting, and secure delivery.

Your platform handles: Email sending, subscriber management, deliverability, and unsubscribe.


Supported Platforms

Integrations page full view

PlatformIntegration TypeWhat Reevix Sends
KlaviyoNative API integrationtrack and identify calls via Klaviyo API
OmnisendWebhookStandard Omnisend event payload
MailchimpWebhookMailchimp event format
Custom WebhookHTTP POSTYour choice of JSON payload format

Setting Up Klaviyo

Webhook integration cards

  1. In Klaviyo → Account → Settings → API Keys, create a new Private API Key with Events: Write permission
  2. In Reevix → Setup → Integrations, click Add Integration → Klaviyo
  3. Paste your Klaviyo Private API Key
  4. Select which events to send (see table below)
  5. Click Save & Test — Reevix fires a test event; verify it appears in Klaviyo's Activity Feed

Klaviyo events sent by Reevix:

Event NameWhen It FiresPayload Includes
Cart AbandonedVisitor leaves with items in cart (30-min delay)Product list, cart value, session ID
Browse AbandonedVisitor leaves after viewing products without addingCategory, products viewed, price range
Checkout StartedVisitor enters checkout but doesn't completeCart value, item count
PurchaseOrder completedOrder ID, revenue, items

Setting Up Omnisend

  1. In Omnisend → Store Settings → API Keys, copy your API Key
  2. In Reevix → Setup → Integrations, click Add Integration → Omnisend
  3. Paste your Omnisend API Key
  4. Select events
  5. Click Save & Test

Omnisend uses the same event names as above. Events appear in Omnisend → Reports → Automation Activity.


Setting Up Mailchimp

  1. In Mailchimp → Account → Extras → API Keys, click Create A Key
  2. In Reevix → Setup → Integrations, click Add Integration → Mailchimp
  3. Paste your Mailchimp API Key
  4. Select your Audience (list) from the dropdown — Reevix will only trigger automations for subscribers in this audience
  5. Select events
  6. Click Save & Test

Mailchimp events trigger Customer Journeys (Mailchimp's automation builder). Create a journey starting with the relevant Reevix event tag.


Custom Webhook

For any platform not listed above:

  1. In Reevix → Setup → Integrations, click Add Integration → Custom Webhook
  2. Enter your Endpoint URL (must accept HTTP POST with JSON body)
  3. Choose your authentication method:

- Bearer Token — Reevix adds Authorization: Bearer <token> header

- HMAC Signature — Reevix signs the payload with a shared secret; verify on your end

- None — No authentication (only for internal endpoints behind a firewall)

  1. Select events
  2. Click Save & Test

Webhook Payload Format

{
  "event": "cart_abandoned",
  "timestamp": "2026-04-28T14:32:00Z",
  "storeId": "sto_abc123",
  "session": {
    "id": "sess_xyz789",
    "email": "shopper@example.com",
    "userId": "usr_456"
  },
  "cart": {
    "subtotal": 149.99,
    "currency": "USD",
    "items": [
      {
        "productId": "prod_001",
        "title": "Classic Wool Sweater",
        "price": 89.99,
        "quantity": 1,
        "imageUrl": "https://yourstore.com/products/sweater.jpg",
        "productUrl": "https://yourstore.com/products/sweater"
      }
    ]
  },
  "metadata": {
    "behaviorState": "evaluating",
    "sessionDuration": 312,
    "pageCount": 8
  }
}

HMAC Verification (Node.js example)

const crypto = require('crypto')

function verifyReevixWebhook(payload, signature, secret) {
  const expected = crypto
    .createHmac('sha256', secret)
    .update(payload)
    .digest('hex')
  return crypto.timingSafeEqual(
    Buffer.from(`sha256=${expected}`),
    Buffer.from(signature)
  )
}

Testing Integrations

Each integration card has a Send Test Event button. Click it to send a synthetic cart_abandoned event to your platform. Verify it arrives before going live.


Event Delay Configuration

EventDefault DelayWhy
cart_abandoned30 minutes after exitGives the shopper time to return on their own
browse_abandoned60 minutes after exitBrowse abandonment is lower-intent; longer delay is better
checkout_started15 minutes after exitCheckout abandonment is high-intent; act faster
purchaseImmediateNo delay — fire as soon as conversion is confirmed

You can customise these delays in the integration settings.