I am managing a restaurant menu website that integrates with Brevo for email communication, including promotional campaigns, menu updates, and transactional notifications. The goal is to automatically notify users when new items are added, prices change, or limited-time offers become available. While the basic integration works, I am encountering inconsistencies in how contacts are created, updated, and segmented within Brevo. Some users receive notifications as expected, while others who meet the same criteria do not, even though their data appears correctly stored in both the website database and Brevo contact lists. This makes it difficult to trust the automation logic and ensure consistent communication with users.
One major challenge is synchronizing contact attributes between the website and Brevo. User data such as location preferences, dietary interests, and subscription status is updated frequently based on interactions with the menu. These attributes are pushed to Brevo via API calls, but updates do not always reflect immediately or accurately in contact profiles. In some cases, older attribute values overwrite newer ones, possibly due to timing issues or parallel updates. I am unsure whether this behavior is caused by API rate limits, asynchronous processing within Brevo, or mistakes in how attribute updates are structured on the website side.
Automation workflows are another source of complexity. I have set up scenarios that trigger emails when certain conditions are met, such as a new menu category being published or a seasonal promotion going live. However, workflows sometimes trigger multiple times for the same user or fail to trigger altogether. Debugging these scenarios is difficult because it is not always clear which condition prevented the workflow from executing. I would appreciate guidance on designing reliable automation logic in Brevo that avoids duplicate sends while still reacting quickly to frequent content updates.
Transactional emails also present challenges. The website sends confirmation emails when users subscribe to menu updates or request notifications for specific items. While these emails are generally delivered, there are occasional delays or missing sends without clear error responses from the API. Logs on the website side indicate successful API calls, yet the corresponding emails never appear in Brevo’s transactional logs. Understanding how to properly monitor transactional email delivery and interpret Brevo’s API responses would help diagnose whether these issues originate from the integration or from internal processing within Brevo.
Deliverability and sender reputation are additional concerns. Because menu updates can be frequent, especially during promotions, email volume can spike over short periods. I want to ensure that this does not negatively impact deliverability or cause emails to be flagged as spam. I am currently using a shared IP and standard authentication settings, but I am unsure whether additional configuration such as dedicated IPs, advanced warm-up strategies, or more granular send throttling is recommended for this type of use case. Advice on best practices for maintaining strong deliverability with frequent, content-driven emails would be very helpful.
Finally, I am planning to scale this setup to support multiple restaurant locations, each with its own subscriber base, menu variations, and promotional schedules. This will require more advanced segmentation, dynamic email content, and possibly multiple automation workflows running in parallel. Before scaling further, I want to ensure that the current integration approach is sound and maintainable. Insights from the Brevo community on structuring scalable contact models, automations, and API integrations for content-driven websites would be greatly appreciated. Sorry for long post
