0xOX0X
Digital Business

Brevo vs ConvertKit: 2026 SaaS Retention Workflow Guide

Quick Answer

Brevo fits B2B SaaS teams with large total contact lists and lower monthly send frequency because billing centers on email volume rather than stored contacts. ConvertKit (rebranded as Kit) fits creator-led or newsletter-centric SaaS funnels where subscriber-tier triggers and tag-based visual sequences justify per-contact pricing, provided dormant users are sunsetted consistently.

By Devon ReedUpdated 2026-11-215 min read
Isometric illustration of a B2B SaaS customer retention workflow syncing CRM data with automated lifecycle emails.

Brevo and Kit Retention-Event Architecture

Engineering workspace showing code for a CRM integration and an API error log.

Retention workflows work best when product telemetry is treated as a durable event stream rather than as a direct email trigger. A product event—such as an integration setup failure, a decline in API activity, or an incomplete onboarding step—should enter a queue or outbox before it updates Brevo or Kit (formerly ConvertKit).

This approach separates product reliability from vendor API availability. It also lets the application deduplicate events, preserve ordering per contact, and decide whether a change should start, stop, or update an automation.

For privacy-conscious measurement of downstream campaign clicks, see Plausible vs GA4 Privacy: 2026 Analytics Comparison.

Brevo Contact API Failures and Rate-Limit Troubleshooting

Do not assume a 429 response permanently loses a retention trigger. A trigger is lost only when the application does not durably retain the event for retry or reconciliation. Store events in an outbox, queue, or database table before calling a CRM API.

Log / Error MessageWhat It MeansNext Check
401 UnauthorizedThe Brevo API key is absent, invalid, or not accepted for the account.Verify the key in Brevo and confirm the request sends the api-key header.
400 Bad RequestThe payload does not match the contact endpoint contract, an attribute is unavailable, or a contact already exists without upsert enabled.Compare the body with Brevo’s Create a contact reference.
429 Too Many RequestsBrevo is asking the client to slow down.Preserve the event, honor Retry-After when supplied, and retry through a queue.
5xx response or timeoutThe request may not have reached Brevo, or Brevo may have processed it before the response failed.Retry only an idempotent desired-state update; do not blindly retry action-creating endpoints.

Symptom: Brevo returns `401 Unauthorized`

Verification command

bash
export BREVO_API_KEY='replace-with-a-staging-key'

curl --silent --show-error --verbose \
  --request POST 'https://api.brevo.com/v3/contacts' \
  --header "api-key: ${BREVO_API_KEY}" \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{
    "email": "retention-test@example.invalid",
    "attributes": {
      "RETENTION_STATUS": "AT_RISK_INACTIVE"
    },
    "listIds": [2],
    "updateEnabled": true
  }'

Output meaning

  • A successful 2xx response confirms that the key, headers, JSON encoding, and endpoint are accepted.
  • 401 indicates an authentication problem; rotate or replace the staging key rather than changing retry behavior.
  • 400 usually identifies a payload, list ID, or custom-attribute issue.
  • 429 confirms that the client needs queue-based pacing.

Next fix

Keep API keys in a secret manager or environment variable. Do not place a production key in source code, logs, curl history, or support tickets.

Symptom: Existing contacts fail or automations create repeated actions

Verification command

Compare the request body with Brevo’s documented POST /v3/contacts contract and verify that updateEnabled is explicitly set to true.

Output meaning

Brevo’s create-contact endpoint can update an existing contact when updateEnabled: true is supplied. Without that explicit upsert behavior, an existing email address can produce an error instead of applying the intended state.

Next fix

Use one durable outbox record per logical state transition, such as (internal_contact_id, retention_state_version). A worker should claim that record once, retry the same desired state when delivery is uncertain, and mark it delivered only after a successful API response.

Avoid using retries to create one-off actions such as “send recovery email now.” Instead, update a stable contact attribute such as RETENTION_STATUS, then configure the Brevo automation to enter only when the intended state transition occurs. Confirm the automation’s re-entry behavior in Brevo before enabling it for production.

Brevo and Kit Billing Models for Retention Workflows

Brevo and Kit use different primary pricing dimensions, but neither platform should be evaluated using unsupported assumptions about dormant-contact cost.

PlatformBilling Model to ValidateRetention-Workflow Consideration
BrevoBrevo’s marketing plans are primarily organized around email-send volume; plan capabilities, add-ons, transactional sending, and account terms can vary.A low-send dormant audience may reduce send-volume pressure, but it does not prove that contact storage, account access, automation features, or transactional capacity are free.
KitKit pricing is primarily subscriber-tier based, with plan features and limits determined by the selected tier.Keeping inactive subscribers can affect the applicable subscriber tier even when those subscribers receive little or no mail.

Use the current official Brevo pricing page, Brevo transactional email documentation, and Kit pricing page when modeling a specific account. Confirm whether the selected plan includes the required automation, segmentation, API, transactional-email, and contact-management capabilities.

A pruning policy can still be useful, but it should be based on consent, contractual retention requirements, suppression rules, and the platform’s current billing definition. Do not delete suppressed or opted-out records merely to reduce a billing tier; retain suppression evidence where required and prevent accidental resubscription.

Brevo Idempotent Contact Upsert Worker

The following worker performs a desired-state contact upsert. It explicitly permits retries for POST because this specific request is made idempotent at the application level: the same email, retention state, list ID, and updateEnabled: true are sent again after a transient failure.

The caller must invoke this worker only after a durable outbox has deduplicated and serialized state changes for the contact. Do not reuse this retry policy for endpoints that create non-idempotent campaign actions.

python
import os
import requests
from requests.adapters import HTTPAdapter
from urllib3.util.retry import Retry

BREVO_CONTACTS_URL = "https://api.brevo.com/v3/contacts"

# User-configured values: set these in the deployment environment.
BREVO_API_KEY = os.environ["BREVO_API_KEY"]
AT_RISK_LIST_ID = int(os.environ["BREVO_AT_RISK_LIST_ID"])

retry_policy = Retry(
    total=3,
    connect=3,
    read=3,
    status=3,
    backoff_factor=1,
    status_forcelist=(429, 500, 502, 503, 504),
    allowed_methods=frozenset({"POST"}),
    respect_retry_after_header=True,
    raise_on_status=False,
)

session = requests.Session()
session.mount("https://", HTTPAdapter(max_retries=retry_policy))

def upsert_retention_state(user_email: str, retention_status: str) -> None:
    headers = {
        "accept": "application/json",
        "api-key": BREVO_API_KEY,
        "content-type": "application/json",
    }

    payload = {
        "email": user_email,
        "attributes": {
            "RETENTION_STATUS": retention_status,
        },
        "listIds": [AT_RISK_LIST_ID],
        "updateEnabled": True,
    }

    response = session.post(
        BREVO_CONTACTS_URL,
        headers=headers,
        json=payload,
        timeout=(3.05, 15),
    )
    response.raise_for_status()

respect_retry_after_header=True instructs urllib3 to follow Brevo’s Retry-After guidance when that header is present. The backoff factor covers retryable responses that do not provide a usable delay.

Brevo or Kit Selection for SaaS Retention Programs

Choose based on verified requirements rather than absolute product rankings:

  • Choose Brevo when send-volume-oriented billing, contact upserts, transactional-email capabilities, and Brevo’s automation features match the workload. Validate marketing and transactional sending rules separately.
  • Choose Kit when its subscriber-based plans, creator-oriented forms, sequences, and visual automation features match the team’s lifecycle-marketing process.
  • Use separate systems only when the operational cost of data synchronization, consent management, suppression handling, and reporting is justified.

Before switching platforms, document the expected contact count, monthly marketing-send volume, transactional-send volume, required automations, custom attributes, API throughput, and consent/suppression workflow. Compare those requirements against current official plan documentation rather than using illustrative monthly-price estimates.

Share this article

Frequently Asked Questions

Can I use Brevo for transactional emails and ConvertKit for marketing?

Yes, many B2B SaaS companies use a 'split stack' where Brevo handles high-volume system alerts and retention triggers via API, while ConvertKit manages the editorial newsletter. This optimizes costs by keeping the expensive subscriber count low in ConvertKit.

What is the best way to track if my retention emails actually work?

Use UTM parameters combined with privacy-first analytics. Monitor the 'Re-activation Rate'—the percentage of users who log back into your app within 48 hours of receiving a retention email—rather than just open rates.

Does Brevo offer a free tier for startups in 2026?

Brevo typically maintains a free tier that allows up to 300 emails per day with unlimited contacts. This is ideal for early-stage B2B SaaS testing their initial retention workflows before scaling.

Free Weekly Dispatch

Get the Weekly SMB AI & SaaS Brief

Practical software benchmarks, prompt templates, and ROI breakdowns delivered every Tuesday. No fluff, unsubscribe anytime.