Canvas
71 TopicsForge Canvas Template: Product repurchase reminder (with timing and channel testing)
Hello fellow Braze orchestrators, I didn't make it to Forge in person this year, but it was great tuning in to the keynotes and catching up on all the latest Braze innovations. 🔥 Here is a quick Canvas that we are about to launch to drive repurchase of two of our products that customers need to by on a regular basis. Entry criteria: purchase of a certain SKU Experimentation (both set up as Personalized Path): Message timing (30 days vs 45 days after the purchase) Message channel (email vs SMS, in this case) Message sequence: A user gets a reminder to repurchase the product she might be running low on; If a user engages with the message from step 1, but does not purchase, he receives a reminder 3 days later with a special offer, to incentivize the purchase. Let me know if you see any opportunities for improvement. I imagine, soon we will be able to simplify this flow by leveraging all the upcoming Braze AI tools. Cheers, Olga Baker Charlie Banana / P&G92Views5likes1CommentPRODUCT REQUEST: Split Audience Based On Canvas Entry Property
Hi Braze! Where in the Braze Product Roadmap is the ability to split Canvas audiences based on Canvas Entry Property? From my experience working with several teams, this seems to be a highly requested feature. We are currently using the workaround of having to log the Canvas Entry Property as a Custom Attribute, using the User Update Step, but this certainly is a workaround that requires extra DPs. Any insight would be super helpful! Thank you so much!198Views4likes0CommentsForge Canvas Template: Frequency/Channel mix Experiment Setup”
This Canvas serves as a starting point for setting up an experiment aimed at sending specific sub-groups of a user population down the engagement journey that has the highest likelihood of converting them. The criteria that differentiate the journey in this Canvas are tied to two variables: 1. Frequency: n times over n periods depending on the use case, industry, and type of product. For example, n times per week for n weeks. Both the 'times' and 'periods' should be customized according to the use case. 2. Channel mix: combinations of at least 2 channels based on the use case, industry, and type of product. For example, a push notification followed by an email or an IAM followed by an email. The channels to test should be customized based on the use case. The goal here is to leverage Braze's personalization systems to take experiments to the next level: no more simple A/B tests where all users are sent down the engagement journey that converts the most overall. Instead, specific sub-groups of the population will be sent down different, specific paths based on their unique characteristics/preferences. This allows us to avoid a 'one size fits all' approach and instead create multiple journeys that users can experience based on what they prefer (and what tends to convert users like them better 😉 )." I’ve been using this setup for a while, and the uplift compared to a single experience for the entire population (chosen after multiple iterations of a classic A/B test) is significant. Let me know what you think and if you have any ideas for improving this setup!65Views2likes1CommentSelecting multiple steps tool
I recently submitted a suggestion to Braze to introduce a feature/tool which would allow you to drag select multiple steps at at time? Similar to when you try select multiple files on your desktop. Does anyone think that would be something that would benefit them too, rather than having to individually select steps/branches one by one to delete or duplicate?348Views2likes1CommentBest Practice: Naming Convention
Hi Bonfire, Hope you are all doing well! I wanted to raise this discussion topic that has been on my mind for so long: CAMPAIGN/CANVAS NAMING CONVENTIONS. Having worked with 100+ Braze teams at this point, I have seen so many creative ways for naming conventions, all the way from a non-existent structure to a fully-structured, spreadsheet-formula-generated approach. Here are some initial thoughts/reflections I want to put out, and I'd love to hear all your suggestions: what's worked, what hasn't worked, what's simple/easy to manage, etc. 1. Easy navigation/search within the dashboard. I think one thing to consider when creating a naming convention is how easily will you be able to search for this in the dashboard. Considering that there are alphabetical sorts, I've seen many teams go for a "yyyy-mm-dd campaign name" structure. Even though there is a "last edited" sort, there are many times where the name sort could be helpful. However, when we start adding all sorts of helpful things in the name like "AB test", "email_iam_push_sms", "audience_type", etc., the campaign name starts to get really long. To the point where the distinguishing campaign name doesn't even show up. Which makes the dashboard navigation tough. Now, tags are a great usage for dashboard organization. However, there's one major downside to tags which leads to my point #2. 2. Tag information is not passed through Braze Currents. So even if we have an amazing tagging structure for channels, audience, delivery type, date, etc., when the data team receives the Currents data, they can't rely on the tag information to structure their data conveniently. This is where I've seen teams use the thorough naming convention in the campaign title, and the data teams are parsing specific key words in the campaign titles to run their analytics. A bit risky as it's fully dependent on the correctness of campaign name spelling. I do think if Braze can pass along tag data in the Currents fields, this could potentially solve some of the pain. Until then, I'D LOVE TO HEAR FROM YOU: If you are proud and satisfied with your Campaign/Canvas naming structure, please share them here! Thank you all, Allan211Views2likes0CommentsCanvas Reporting based on Date Ranges
When I am doing user data exports from Canvas, it always exports every user that has ever entered the canvas. I would like it so that when I am viewing a specific date range that it forces that date range into the data export. This prevents me from utilizing .csv exports effectively since it traps me into lifetime data rather than the specified date range.262Views1like1CommentAudience Path through event properties
Hello community! I need your help to set up a Canvas Flow: Context: In our subscription we are customising the unsubscribe flow based on the reason. We register this reason as an event property of the event that triggers the flow ( subscription cancel complete). Problem: It does not find the way to direct the users in a flow or another depending on the property of the event, since the ''audience path'' tool does not allow to split by event property. How would you do it? I could do it through conditions and liquid, but the flows are not exactly the same for all properties/reason. Thank you very much!Solved46Views1like3CommentsDo you use control groups in your Canvas set up?
Hi all, Just wanted to get a sense of how many people use control groups in their marketing comms campaigns. Do you use control groups? Why? Why not? Are there exceptions where you don't use control groups? How big do you make your control groups? Does having a control group sometimes lead to puzzling incremental uplift numbers? Is it worth it to use incremental uplift as a metric when you have to spend a few minutes just explaining to stakeholders what incremental uplift is? (As opposed to absolute metrics which is easily understood)562Views1like3CommentsFAQ: What Is A Race Condition?
A common question we get at Braze is "what is a race condition?" A race condition is a concept where an outcome is dependent on the sequence or timing of other events. For example, if the desired sequence of events is “Event A” and then “Event B”, but sometimes “Event A” comes first and other times “Event B” comes first—that is known as a race condition. You can learn more about Race conditions in our Documentation page here. If you have tips of your own for spotting or avoiding race conditions, share them in the thread!187Views1like0Comments