Recent Content
Calling all Braze Freelancers π©βπ»π¨βπ»π
Hey Brazefriends, We building a collective of freelancers specialising in Braze integration, strategy and campaign management to help Braze customers around the world. Our collective has a range of different clients who are using Braze and we need freelancers with different specialisations to connect them with for work opportunities. If you are a CRM marketing manager, analyst, product manager or creative and would like to do freelance work for different clients and apps then we would love to hear from you. Commitment could be as little as 10 hours per week and work would be fully remote. Simply fill out this short form to applyhttps://forms.gle/JNM1mC2GofQ3wrFg7 If you have any questions please DM me for more info!Ed2 years agoPractitioner II2.7KViews18likes5CommentsI miss the Braze slack community
I'm really sad the Braze Slack community was disbanded. Getting ideas or help in Bonfire is very difficult, it seems like the audience is less engaged or the entire Slack community didn't move over.Solvedisabellelabadie2 years agoPractitioner II3KViews17likes8CommentsI've created a beginner liquid 'for loops' tutorial. Would love some feedback.
Hi all I've started working on a series of videos to help unpack some liquid terms to help others and teach myself along the way. After recently needing 'for loops' to solve a problem I started by making a tutorial on those. Even though this video is a smidge more advanced, I plan to do quite a few videos, especially for beginners. Would love you to check it out, write comments, subscribe, and provide any feedback on ease to follow, length, or any thoughts at all. I want these to be a useful tool for all Braze (and liquid) users. Discover the power of liquid for loops in Braze: Beginner tutorial - YouTubeDavidO2 years agoStrategist II712Views10likes6CommentsWelcome to the Connection Lounge
Welcome to the Connection Lounge! This is where you can introduce yourself, network with others, share events, share creative ideas, and more. We'd love if you start out by introducing yourself by Starting a new conversation,selecting the "Introductions" label,creating a Subjectline that speaks to you, and sharing in the below format in theBody: πΊWhere I'm from: π Where I live now: πΌWhat I do now: πA brand I admire: πFavorite trip I've ever taken:MaggieBrennan3 years agoCommunity Manager1.9KViews9likes0Commentsπ Hi Bonfire friends!
π€ tap, tap, tap - is this thing on? π Now that I've set the stage with a corny first line, I'm Elizabeth and I joined Braze towards the end of March to lead the Community & Advocacy team (πMaggieBrennan,EmilyCalderonandSadafQayumi have done amazing work!). I'm new to Braze but not new to community - before Braze, I built the Slack Community at Slack and the Mobile Growth Community at Branch (where a company formerly known as Appboy joined or hosted a number of our community meetups!). I'm β¨stoked β¨to be at Braze and excited to get to know y'all - drop me a message if you want to connect or share what being part of Bonfire has meant to you. Let's go!eakinsey2 years agoCommunity Manager3.4KViews8likes6CommentsTriggering IAMs in Canvas - Questions from Braze Product Team
Our team at Braze wants to bring real-time triggering in-app message (IAM) functionality to Canvas. Today, real-time triggering IAM functionality only exists in Campaigns. If anyone has a few minutes, weβd appreciate it if you could answer the questionsin boldbelow. We can add you to the early access when the feature is available in exchange as well. Let me know if you have any questions and thank you in advance! Also, if youβd prefer to chat over a call, happy to do so instead (please schedulehere). Thank you, Rishi Product Manager at Braze Questionnaire - Triggered IAMs in Canvas The current state of triggered IAMs: In Campaigns, marketers can specify a custom event that triggers/shows an IAM to a user in real-time In Canvas, marketers can specify a custom event within an Action Path that triggers/shows an IAM to the user once they do the following: (1) perform the action, then (2) restart the app (theyβll then see the IAM once the app opens) Our ask: We are considering one of the following approaches for providing more real-time triggered IAMs in Canvas and would like your input. Approach 1 Approach 2 Allow real-time triggering of IAMs via the Action Path Allow real-time triggering based off actions specified within an IAM Message Step Benefits: Branching actions. Marketers can define several triggers/actions that all show different IAMs and qualify the user for all of them, but only display the IAM for the first action performed (and disqualify the rest) Ranking actions. If multiple actions are performed by the user within the action pathβs time window, Braze will show the associated IAM then send the user through the highest-ranked action path only Benefits: Independent control of IAM message triggers/actions. Actions will be defined within the IAM Message (similar to IAM expiration), giving the marketer more control This approach/feature is easier for Braze to build, so we can deliver it to customers faster A couple of questions for you here: Among the two approaches, which would you favor, and what are the reasons for your preference? On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if we implemented the other approach? We are also seeking feedback on how βreal-timeβ the Canvas<>SDK information refresh/exchange needs to be. Today, the SDK (which is the agent that shows IAMs) only refreshes information from Braze when the user opens the app, and users may not necessarily open their apps as quickly as they move through a Canvas. Consider the following hypothetical example of how triggered IAMs could work: 9:00 am: In Canvas, UserA reaches the Canvas step where they are qualified to be shown IAM_1 immediately after they perform ActionX 9:20 am: UserA performs ActionX. No IAM is shown 9:30 am: UserA leaves the app and reopens it. Note: at this time, the SDK refreshes information from Braze 10 am: UserA performs ActionX. This time, they are shown IAM_1 immediately since the SDK has the latest information from Canvas The need for the user to leave/reopen the app may not be ideal, but if you feel the feature is still usable, we can deliver a first version of the feature (triggered IAMs in Canvas) to you sooner. With this in mind, we had a few additional questions: On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if users needed to reopen the app to allow the SDK to refresh information? Would you still be able to use triggered IAMs if this was the case? How frequently do your users typically leave/reopen their app? What scenarios, if any, do you foresee where users are unable to be shown IAMs due to them not reopening the app?rishi2 years agoBraze Employee1.7KViews8likes14Comments