Brevo “OPT_IN” attribute not filled

  • krollekop39

    (@krollekop39)


    2 weeks ago

    Hi all,

    I’m setting up a form with Brevo integration. Everything works as expected (after following the Brevo integration guide, including troubleshooting and checking localized French attribute names :-).
    The only hitch is that the Brevo “OPT_IN” variable doesn’t get set even when the acceptance is set in the form (and correctly interpreted, since other attributes do indeed get forwarded).

    The acceptance tag I used is as follows: 

    [acceptance your-opt_in optional consent_for:sendinblue] Je souhaite recevoir votre infolettre (environ 4 newsletters par an) et j'ai pris connaissance de votre politique de confidentialité et mentions légales. (Vous pouvez vous désinscrire facilement en cliquant sur le lien de désinscription dans nos courriels.) [/acceptance]

    I changed the default ACCEPTANCE attribute to YOUR-OPT_IN in the hope of mapping correctly to the name of the attribute in Brevo, to no avail. I tried to change the consent_for:sendinblue tag to consent_for:brevo but that breaks the form. Actually, when the consent_for: tag isn’t used at all, the behaviour of the form doesn’t change.

    Probably I need to create a specific “user-defined additional attribute” that correctly maps to OPT_IN in Brevo but I don’t understand how to do so. Any idea?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    2 weeks ago

    I can’t access the linked page because it’s still in draft status. Can you please publish the page first?

    Thread Starter krollekop39

    (@krollekop39)

    1 week, 6 days ago

    Hello! Here is a published copy:

    https://www.chant-interieur.be/temp-contact/

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    1 week, 6 days ago

    OK. Look at the Contact Attributes dashboard on Brevo (doc). Do you have a corresponding OPT_IN attribute there?

    Thread Starter krollekop39

    (@krollekop39)

    1 week, 4 days ago

    Yes, it’s there. It’s a boolean type (screen copy below). Is upper/lowercase an issue? Do I need to write acceptance your-OPT_IN optional rather than acceptance your-opt_in optional ?

    By the way, those links you shared about brevo attributes are really helpful, possibly worth adding to you doc about brevo integration in the “Contact attribute–form field mapping” section.

    Many thanks for your help!

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    1 week, 4 days ago

    Uppercase/lowercase doesn’t matter there. Try setting other attribute types on OPT_IN and let us know if this changes anything.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.