Brevo

Brevo exposes a broad set of objects: contacts, email campaigns, SMS campaigns, CRM deals, CRM tasks, email templates, and transactional messages. This integration focuses on the two objects that support attributable performance indicators: CRM deals, where every record carries an owner field resolved to a user email, and email campaigns, where sender identity provides a weaker but usable attribution signal. Contact and task objects were evaluated and excluded: contacts carry no owner field, and tasks present strong gaming dynamics in small teams. Five KPIs were retained, selected against three criteria: ability to attribute to an owner, resistance to gaming, and balance between leading and lagging indicators.

CRM pipeline: reading deal progression through paired metrics

Four KPIs cover the CRM deal pipeline. Deals Created is the only leading indicator in this block: it counts new opportunities entered in the period and anticipates future activity. The three remaining indicators — Deals Won, Deal Close Rate, and Average Deal Cycle — are lagging, confirming results already realized.

Deals Created carries a medium gaming risk: a sales representative under pressure to show activity can inflate the count by entering low-quality or fictitious opportunities. Deal Close Rate functions as the natural counterweight. When Deals Created rises while Deal Close Rate falls, the pipeline is accumulating unqualified volume. When both rise together, the increase in activity translates into real conversion. Neither indicator is interpretable in isolation; the relationship between them is the signal.

Average Deal Cycle measures the mean elapsed time between deal creation and close for won deals. It introduces a velocity dimension absent from the other three indicators. A shortening cycle is generally positive, but it can also indicate premature closing — deals pushed across the line before they are sufficiently qualified. For this reason, Average Deal Cycle is read against Deal Close Rate: a declining cycle combined with a declining close rate suggests that speed is being gained at the expense of quality. The combination protects against the drift where efficiency metrics are optimized through selective disqualification rather than genuine acceleration.

Email campaigns: the specific scope of Campaign Click Rate

Campaign Click Rate is retained as the sole email engagement indicator. Open rate, the more commonly cited metric, was deliberately excluded: since Apple Mail Privacy Protection introduced background email pre-fetching in iOS 15, open rates on campaigns sent to Apple Mail users are systematically inflated by machine-generated opens. The signal is corrupted at the source and cannot be used as a reliable performance indicator. Click rate is not affected by this mechanism and remains an accurate measure of genuine recipient action.

Attribution for Campaign Click Rate rests on sender identity rather than a user account field. Email campaigns in Brevo carry a sender email address — which may represent a shared inbox rather than an individual — making attribution structurally weaker than on the CRM side. This KPI is most reliable when sender identities are mapped one-to-one to team members; it degrades when multiple people operate under a shared sending address.

Scope and limits of the integration

Brevo records deal stages, amounts, and campaign statistics, but does not capture the quality of commercial interactions or the content quality of email campaigns. A deal marked as won may reflect sustained relationship-building or a single favorable circumstance; the data does not distinguish between the two. Deal stage names are account-specific and depend on custom pipeline configuration, which means the won stage must be mapped during onboarding — misconfiguration at this step would silently exclude all closed deals from the KPI calculation.

The reliability of these KPIs depends directly on how consistently the team records activity in the tool. Deals that progress informally outside the CRM, campaigns sent from sender identities not mapped to a team member, and tasks closed without completion of the underlying work all remain invisible to the integration. Data discipline is not a technical requirement that the integration can enforce; it is an organizational prerequisite that the integration assumes.