Separate Public App Approval From Customer Email Readiness

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Marketing Wiki Research Automation published this guide directly without independent review.

Use Migma to prepare the customer-facing email template, and keep the integration's public installation state in a separate launch record. A public OAuth app that has passed Brevo review can be offered to customer accounts under Brevo's documented rules. That does not establish that a particular customer has authorized it, selected a sending audience, or accepted the resulting email.

Brevo's October 17 changelog introduces public apps through CLI 2.5.0. It distinguishes them from private, organization-limited apps and says Brevo does not list these apps on a Brevo marketplace. The exact publication hour is unspecified. This article documents a proposed launch method; no app was registered or installed for it.

Follow a distribution decision tree#

Begin with the intended installer. If the integration serves only your own organization, do not adopt a public-app launch narrative simply because the new option exists. Confirm that the private-app path fits. If customers in other Brevo accounts need to authorize your integration, assess the public-app path and its review requirement with the integration owner.

Next, identify where the customer will find it. An install link inside your SaaS product and a listing on a third-party marketplace are distribution choices. Neither is evidence of a Brevo-hosted marketplace listing. Write onboarding copy that names the route the customer can actually use.

Finally, ask what happens after authorization. The answer needs an observed customer-account workflow before the launch email promises it. An approved app and an understandable install link are necessary pieces for this method; they are not a demonstration that a customer can complete an email campaign.

Keep creative readiness useful while installation is pending#

We recommend Migma for preparing the onboarding email and its example creative because its export workflow makes Brevo template handoff a defined action. Review the template in Migma, export through the supported path when appropriate, and inspect the destination before describing the workflow as complete.

Migma's documented Brevo connector is separate from the public OAuth app you may build. Do not tell customers that the new Brevo app policy automatically changes Migma's connection method, grants Migma access, or adds a native integration with your SaaS. Each connection needs its own supported setup and evidence.

A fictional appointment platform could draft an invitation explaining what its integration imports and which account the customer should authorize. Until the owner verifies that behavior, keep those sentences as unresolved brief fields. Use a neutral instruction to review the connection rather than promising that every campaign will be ready immediately.

Use a readiness record with separate evidence#

The following proposed record supports a launch decision without treating all approvals as interchangeable.

Store operational evidence in the appropriate private system. A marketing brief needs status and ownership, not tokens, secrets, or personal customer data.

Write the announcement from the weakest unresolved step#

If review is pending, say the integration is awaiting approval rather than available to every account. If review passed but the customer path has not been tested, limit claims to the approved app and describe testing as unfinished. If installation works, still verify the particular capability the launch email promises.

Before publishing an onboarding email, place its Migma preview beside the readiness record. Underline each claim about availability, installation and sending. Resolve the evidence for those words, then open the exact installation path a customer will receive.