# How to use a Righthand with Brevo

Prepare a Brevo campaign exception review with campaign IDs, reporting cutoffs, bounce categories, and owner-approved follow-up decisions.

By Righthand Team · 2026-10-09

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-brevo

## Review exceptions rather than inventing campaign success

Use Righthand with Brevo to prepare a campaign exception review for a specific sent email. The useful result identifies delivery questions, inconsistent links, and missing measurement sources. It should help the marketer decide what to investigate without resending to people whose eligibility has changed.

Brevo's [campaign-report reference](https://developers.brevo.com/reference/get-email-campaign) separates campaign detail from several statistics views, including global and link statistics. Keep the chosen view and reporting cutoff attached to every metric. A domain breakdown and a whole-campaign total answer different questions.

## Define the campaign and comparison inputs

Give the campaign ID, send time, reporting cutoff, intended audience, and the approved question. For an illustrative event announcement, the review could examine hard and soft bounce categories and whether the registration link points to the correct event.

Inspect Brevo's actual tools in [integrations](/integrations). If the relevant report is unavailable, use an approved export or a scoped browser review. The catalog does not prove that every statistics view, suppression read, or campaign-send operation is native to your connection.

## A worked review request

> At 1 PM America/Los_Angeles on Friday, review the selected Brevo event campaign and approved report snapshot. Return a private exception brief with campaign ID, send and report times, sent and delivered metrics as labeled, hard and soft bounce categories, available unsubscribe information, and primary-link evidence. Do not resend, remove contacts, or change lists. Send to me for marketing-owner review. Reconcile each reported value to its statistics view and keep unavailable measures separate from zero values.

This example is illustrative. A delivered metric records the provider's delivery evidence, not proof that the person read the announcement or attended the event.

## Define the expected result

An example entry might say: “Registration link points to the intended event; campaign report contains bounce categories; recipient-level follow-up eligibility not supplied.” The assistant can propose that the owner inspect the affected records without identifying an unsupported resend audience.

Keep unique views and total views distinct when both appear. A contact with several events should not be counted as several people. If conversion evidence comes from an event system, label it separately until the attribution rule and matching identifiers are supplied.

## Reconcile later snapshots

Reports can change after the first review. Match the campaign ID, compare equivalent views and cutoffs, and update the existing report. Do not treat a refreshed export as a new campaign or mix old and new totals silently.

Permission failures and missing statistics views should produce partial coverage. A confirmed unsubscribe should never become a suggestion to bypass the person's preference through another list or channel. Any contact change or follow-up send requires its own owner-approved rule and evidence.

Define recurring work through [Righthand's responsibility guide](https://docs.righthand.ai/guides/responsibilities-and-workflows). Check [pricing](/pricing) for ongoing campaign reporting, and keep the marketer responsible for recipient decisions.