Common Issues

Connection issues

Invalid API key error when connecting

Double-check that you've copied the full API key from Brevo — it's easy to accidentally trim characters. Go to Brevo → Account settings → SMTP & API → API Keys and regenerate the key if needed, then paste the new one into Coupler.io.

Data flow connects but returns no data

Make sure the entity you selected actually contains data in your Brevo account. For example, if you pick CRM deals but haven't created any deals, the export will be empty. Check the relevant section in Brevo directly.

Missing data

Historical campaign data is missing or incomplete

Brevo's API limits how far back some data is accessible depending on your plan. Check your Brevo plan's data retention limits. Also make sure you've set an appropriate start date using the date picker in the data flow settings — if the start date is too recent, older records will be excluded.

Contact custom attributes are showing as empty columns

Custom attribute values are only populated if contacts have those fields filled in. Export the Contacts attributes entity to see which fields are defined, then cross-reference with your Contacts export. Attributes that have never been set will appear blank.

Contacts lists contacts entity returns no rows

This entity pulls contacts for a specific list. If the list you selected is empty in Brevo, the export will return nothing. Verify the list has subscribers in Brevo's Contacts section before re-running.

Permission errors

403 Forbidden error on specific entities

Some Brevo entities — particularly CRM features — are only available on certain plans. If you get a 403 on CRM deals, pipeline stages, or tasks, check whether your Brevo subscription includes CRM access. Upgrading your plan or switching to a plan that includes those features will resolve the error.

API key doesn't have access to all features

Brevo lets you create restricted API keys scoped to specific features. If your key was created with limited permissions, certain entities will fail. Generate a new key with full access or expand the permissions on your existing key in Brevo's API key settings.

Data discrepancies

Campaign stats in Coupler.io don't match what I see in Brevo

Brevo updates some metrics (especially opens and clicks) in near real-time, so there can be a small lag between what Brevo's dashboard shows and what the API returns at the time of your sync. Re-run your data flow a few hours after a campaign send for the most settled numbers.

Rate limits

Sync fails with a rate limit or 429 error

Brevo's API enforces rate limits that vary by plan. If you're pulling a large number of entities in one data flow or running syncs very frequently, you may hit these limits. Try reducing the number of entities in a single run or spacing out your scheduled syncs.