Postponed on #3470738: Brevo newsletter (un)subscribe (via SDK)

Problem/Motivation

Would be great to provide a checkbox for the Drupal user registration form to subscribe to a Brevo newsletter using the API.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork brevo-3467876

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

Anybody created an issue. See original summary.

renrhaf’s picture

renrhaf
Primary language French
Location 📍 Strasbourg 🐦🦜
commented
Version: » 1.0.x-dev

Future releases of this module might implement newsletter subscription feature.
We will try to make it as user friendly as we can, to provide basic feature out of the box, and also as developer friendly as possible for overriding. Thanks.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Issue summary: View changes
Status: Active » Postponed
Related issues: +#3470738: Brevo newsletter (un)subscribe (via SDK)

Very cool @renrhaf nice to see progress here!
I created #3470738: Brevo newsletter (un)subscribe (via SDK) as a first step to postpone the UI / form features on it.

renrhaf opened merge request !21

  • renrhaf committed 322637c2 on 1.0.x 
    Issue #3467876 by renrhaf: Add user registration newsletter subscription...
renrhaf’s picture

renrhaf
Primary language French
Location 📍 Strasbourg 🐦🦜
commented
Status: Postponed » Fixed

Merged into 1.0.x.

A new opt-in brevo_user submodule adds a newsletter subscription checkbox to the user registration form. When ticked, the user is subscribed to the configured Brevo list(s) through the shared event system (BrevoEvent) — asynchronously via the brevo_create_contact queue by default (registration is never blocked by the API), or synchronously if configured.

It is unchecked by default (explicit opt-in, GDPR-friendly), with configurable label, description, default state, target lists, processing mode and attribute mapping. As discussed in #3553922, it reuses the main module's ContactsApiClientHelper and event subscriber (no separate credentials) and the trigger is overridable via the standard event system — matching the "basic out of the box, developer friendly to override" goal from #2.

The shared BrevoEvent was also generalised to accept a list_ids array, so a contact can be subscribed to several lists at once.

Thanks @anybody for raising this and for the base-module direction. Setting to Fixed.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

Whao thank you very very much @renrhaf - great work!!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.