Connect WordPress sign-ups to Brevo with mapped contact attributes, list membership and a checked opt-in journey. We assess your existing forms and Brevo setup, then define what is saved, what requires confirmation and how failures are reviewed.
We agree on the records, fields and operating rules before connecting WordPress and Brevo. The scope below defines the work to review together.
We map form inputs to the contact attributes available in your Brevo account and agree on the receiving lists. Different form choices can have different destinations without treating every enquiry as a marketing subscriber.
The scope defines whether a sign-up uses double opt-in and which approved confirmation template and destination it uses. Existing contacts and blocked or unsubscribed states need explicit handling.
We check required values and API responses, with a way for the site owner to review failed sign-ups. A retry must preserve the original permission intent rather than forcing a contact onto a list.
Provide the form plugin, intended lists and existing contact attributes. We inspect available account features, authorization and the supported route before configuring the connection.
Your team supplies the permission wording and approves any opt-in confirmation template and redirect page. The API configuration must match that journey, including which list membership changes occur.
Password resets, order notifications and other transactional messages are a different delivery system. If those need Brevo transport, sender authentication and delivery checks are added as an explicit separate scope.
Review the sign-up form, current success state and the expected Brevo contact. Record attribute types, lists and confirmation requirements.
Test a new sign-up, an existing contact, a repeated request and invalid input. For double opt-in, verify both the confirmation message and the completed confirmation state.
Review the saved attributes and list memberships. Check controlled failures and document monitoring, access ownership and how to update the form without changing subscription behavior accidentally.