Frequency Capping
When using frequency capping, does that mean that the user will not receive the message at all? Say we were to set the frequency cap for Push to only allow 1 push per day for any given user. Does that mean they get set in a holding pattern and the Push message will still send next day or they won't receive the Push at all when using frequency capping rules?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/@CovalentMarketingChannel 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.Users marketing consent
Hi everyone, We're looking for ways to increase the number of contactable users. Some key actions we're considering include: A/B testing in the onboarding phase Ad hoc campaigns with in-app notifications for unsubscribed users Creating subscription groups (as we currently don't have any) Has anyone come across a successful case study on this? Or perhaps key metrics, like average user consent rates by industry, or useful websites for inspiration? We're struggling a bit with translating theory into practice, so any insights would be greatly appreciated. Many thanks in advance! Matteo
Can Liquid be passed in Custom Event Properties?
Hey Braze Community! I’m trying to set up a Canvas campaign to deliver personalized notifications to users over a time period. The Canvas is triggered by a custom event with a payload like this [ { "external_id": "78647", "app_id": "a5a9dfc3-0511-42d4-a2c6-1759645e30a8", "name": "Purchase Milestone Reached", "time": "2025-01-08T20:08:23.480Z", "properties": { "body": "Congrats on your new purchase!", "deepLink": "https://www..google.com", "deliveryId": 12345, "liquidBody": "Congrats on your new purchase. Call {% catalog_items Purchase_PushNotifications {{custom_attribute.${organizationId}}} %} {{ items[0].PN_name | default: 'your representative' }} for a free upgrade.", "milestoneType": "upgrade", "notificationType": "PREMIUM", "templateId": 107, "title": "✨ Congratulation!" }, "_update_existing_only": false } ] I’ve set up a message step in the Canvas to send iOS and Android notifications. To handle the notification content dynamically, I’m using the following Liquid logic: {% if canvas_entry_properties.${liquidBody} %} {{ canvas_entry_properties.${liquidBody} }} {% else %} {{ canvas_entry_properties.${body} }} {% endif %} The idea is that if the liquidBody property exists in the event payload, the notification should use it as the content. Otherwise, it should fall back to the body property. The Issue The liquidBody property contains a dynamic Liquid template, but when the notification is sent, the template is rendered literally as a string rather than being dynamically evaluated and resolved. For example, placeholders like {% catalog_items ... %} are not being processed; they appear in the notification as-is. My Question Is it currently possible in Braze to pass dynamic Liquid templates (e.g., the liquidBody property) through an event payload and have them evaluated dynamically in the final push notification? If not, is there another way to achieve this? My goal is to generate these templates dynamically outside of Braze and have them rendered properly within notifications. I’d appreciate any suggestions or guidance on whether this is achievable, or if there are alternative approaches that might work better! Thanks in advance for your help!
