Hi Rob
Can you let me know on what version of the plugin you are?
Also the WP_DEBUG_LOG should work and give you some output of the request that is being send. Here are the steps again:
1. Enable WP_DEBUG
2. Enable WP_DEBUG_LOG
3. test the form again with same values
4. Go to wp-content folder and put the copy here of the debug.log file.
Let me know how it goes.
Kind regards,
Dieter
Hi there,
I can see in the logs:
[28-Mar-2026 22:24:35 UTC] Elementor forms Sendinblue integration – Sendinblue list ID not set.
Please set a list ID in the settings and test again. Let us know how it goes.
Kind regards,
Dieter
I set teh list ID and now some forms send data to Brevo and some do not. I have been working with Brevo to offer you more details. Here is what I have rn:
Here are the specific errors we’re seeing that are worth reporting to them:
PUT /contacts/undefined: Some calls are arriving with the email field as “undefined” – the email address is being passed as a character-by-character object instead of a string. This suggests the plugin is not correctly reading the form field value before making the API call on certain forms.- PUT calls with the full JSON body URL-encoded in the path: On some submissions, the entire request body is being passed as the contact identifier in the endpoint URL instead of an email address. This is a critical bug that causes those submissions to fail entirely and silently – the contact is never created or updated. This is most likely why Form 16030 specifically is not sending contacts to Brevo.
- POST /contacts without
updateEnabled: true: When a contact already exists and the plugin tries to create them again without the update flag, Brevo returns a duplicate error. The plugin should either use updateEnabled: true or implement the check-first flow described above.
- Empty email submissions: Some calls are arriving with
email: "" – form-level validation should prevent empty email addresses from being sent to the API.
- Empty batch calls: Some
POST /contacts/batch requests are arriving with an empty contacts array, which serves no purpose and indicates the plugin is firing API calls before checking whether there’s anything to send.
Items 1 and 2 in particular are most likely the root cause of why some forms add contacts and others don’t – it’s a code inconsistency in how different forms are configured in the plugin.
Regarding #1. I have an elementor form, and I have checked the advanced tab to see the form field ID and pasted it to the Sendinblue mapping settings.
Here’s a loom which might help you see the settings. I shot it this morning to help Brevo help me… so it’s not 100% relevant.
Thank you, Rob
Hi Rob,
Can you contact us via our support page? That way we can check directly on the website itself;
Kind regards,
Dieter
yes, pls send me the link to your support page
Hi Rob,
You can send us via https://plugins.webtica.be/support/
Kind regards,
Dieter
OK, I’ve already reached out to you in that channel, but I am still waiting a reply and a solution.
Regards, Rob
Hi Rob,
We did reply 2 mails from Rob -> With what email did you send the requests?
Kind regards,
Dieter
maybe you could just respond to the above please?
I do receive these messages, and the other support system doesn’t have a ticket tracking option. You just email and say goodbye to the thread.
regards, Rob
The thing is we need login credentials so we can check directly on the website.
Can you make a staging environment with login credentials so we can check?
@dieterj You need to reply that you will not do that or ask for that again. You will get banned from here if you do not and your plugin could be closed.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their phpinfo(); output.
- Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
Hi @rob_strickland,
As you see we got a reply from WP mods that i totally understand. We will need to do the check here. Please again do the following exactly:
1. Enable WP_DEBUG
2. Enable WP_DEBUG_LOG
3. Test the form again with same values
4. Go to wp-content folder and put the copy here of the debug.log file. (Only the ones with our plugin)
Thank you,
Dieter
Hello,
I am sorry you got scolded!
I ran another test with 100% unique entries in the form, and it worked.
It appears that the conflict is centered around the fact that any duplicate data (email, phone, etc) prevents the additional record to be added. There is no error message indicating that a sup was found etc.
I have brought up this limitation to Brevo.
Do you know if your plugin can identify duplicate records? Or prevents the addition of a new record in Brevo?
It’d be great to have a merge and append option.
Kind regards,
Rob Strickland
Hi Rob,
No problem. Great to hear it is working.
Did you have double optin working? I know if you use double optin you need to set it to update the existing data. Normally the data should just update. I’ll do some tests later this week to see if we can reproduce this.
I’ll mark this issue as solved now. Feel free to open a new issue if you encounter any more problems.
Kind regards,
Dieter
