Channel Substitute.
I’ve seen so many wasteful forms of communication that could be handled more effectively with CRM channels—yet brands continue relying on outdated, inefficient methods. ✅ Event Reminders via Call Centers? → A well-timed push notification or SMS would be faster, cheaper, and ensure the message actually lands. ✅ Mass Email Blasts for Promotions? → A behavior-based CRM journey can tailor offers dynamically based on customer interest, rather than sending generic discounts. ✅ Website Pop-Ups for Account Reactivation? → A personalized email or in-app message triggered by inactivity would recover users without annoying everyone. ✅ Store Flyers for Loyalty Programs? → Why not leverage CRM automation to send a targeted push or SMS only to engaged customers instead of wasting print materials? ✅ Manual Follow-Ups for Onboarding? → A multi-step CRM journey with email + in-app education would ensure higher activation rates with less manual work. So many day-to-day marketing efforts could be more effective, personalized, and cost-efficient just by leveraging CRM channels properly. That's it, just a note of things I see that drives me crazy.
Benchmark of Re-consent Rates
Hi everyone, I am currently planning a re-consent campaign and have segmented our audience into 4 groups; highly engaged, moderate, lapsed and dormant. I am trying to get a sense of the reconsent rates for each segment to better predict business impact. If you have recently run a similar campaign - especially in the ticketing, live event, luxury goods or marketplace industries - could you share any insights or approximate success rates? Any benchmarks or lessons learned would be greatly appreciated! Thanks in advance :)
sending email to CSV list
Hi there! I'm new to Braze and recently uploaded a CSV file containing 1.5k email addresses. The import was successful, but when I tried to create a campaign using segments, the email addresses couldn't be found. I included the 'email' column along with randomly generated user alias names and labels in the file. Is there something I might have done wrong?New Braze YouTube Resource!!
Hey everyone! I'm excited to share that my team at Covalent Marketing (a trusted Braze consulting and services company), has just launched a series of new YouTube videos... Braze Bites. These resources cover essential topics and practical use cases for Braze users at all levels, in quick digestible videos. Check them out, and let us know if you find any of the videos helpful—or if there are other topics you’d like to see us cover! https://www.youtube.com/@CovalentMarketingControl group based on custom attribute
Hey everyone! I am wondering if anyone had a similar situation: standard tool for isolating control group (global or Canvas- specific) does not fit my business needs, because I want to measure incremental change of product conversions per B2B subscriber, and each B2B subscriber can have more than 1 employee (aka user ID in Braze). Therefore, there is a risk of having representatives of the same B2B entity in both control and treatment groups. How would you deal with this issue? I have an idea of assigning custom attribute (control_group = true/false) when importing each new user (so that all users within one B2B entity fall into either control or treatment group), but it makes managing campaigns and building reports more complicated. I'll be grateful for your ideas and sharing your experience. Thank you! :)Preference Center Question
Hi there, My team and I just set up a preference center for the first time with our email subscription groups. Does anyone know how to test that the page shows properly and is filtering emails properly through a test email? I wasn't able to figure it out on my own! Thanks all, Lexy M.Braze Building Blocks: A Brief Intro to Canvas Flow Audience Sync
Curious about Canvas Audience Sync? Senior Customer Success Manager Donna_Young will walk you quickly through how to create an Audience Sync step in a Canvas Flow in this 2-minute video. You can get all the integration information and suggested use cases in our documentation.
