Frequency Cap Hierarchy
Hi! I am wanting to implement frequency capping for my Braze instance. At the moment our main form of channel is Push which will continue. I am wanting to create a almost hierarchy, so e.g. user receives no more than 1 push in an hour UNLESS the canvas contains a tag 'offer' then they can receive this extra canvas.
Working with timezones
Hi there, I am looking to set up a campaign that be run manually daily day at around 8am-10am (depending on internal readiness). We want this campaign to be received in users local time zone at the same time. Eg. Campaign run at 8am Melbourne time and received in New York at 8am (14hours later) I have been looking at the recommended set up as per documentation (see below), however not sure if this would work for us. The reason for this is that we then want to a new version of this campaign the day after with updated content. Based on the below this may not work due to the 24hr of eligibility. I also looked at the option of running this as canvas and create separate audience paths and delays. However, can't figure out the best way forward. Can someone please advise on the best way approach?Transactional Push Notification ideas?
Hi - We hope to launch some basic transactional push notifications which we were told were high performers! I was wondering if anyone has done something similar and if they had any ideas of some of the 'lower hanging fruit' of transactional push's that were high performing... Some examples that we are starting with are: 1. Order Confirmed 2. Order Shipped 3. Order Delivered Are there any other 'transactional' messages such as the above that you have seen success with?
Forge 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&G
Segmentation of custom nested attributes by dates
Hi all, I'm new around here, so apologies if this has been asked before. I couldn't find a post on it though so here we go: I'm trying to set up a segment that'll show me users who have opened a specific campaign and then made a purchase within a specific timeframe. We organized our purchase data in custom nested attributes. So when trying to set up the segment, I use the "has opened email for campaign XYZ" filter, then insert my custom nested attribute purchase > purchase date > chose "after" from the time dropdown and then select a date from the calendar. I'm wondering if "after" really does mean after (so excludes the date chosen from the calendar), or if it actually means on or after (so includes the date chosen from the calendar). The latter is what I want to achieve. Grateful for any tips you may have! Thanks TanitaIgnore hour of timestamp custom attribute in segment filters
Hello, I'm using a "time" formatted custom attribute which has as value for each user a timestamp (precise date AND hour). I'm using this custom attribute in segments, using the filter "more than" or "less than" X days ago. I know the "day" in this filter means +24 hours (and not calendar days), so the hour in the custom attribute impacts actually a lot the eligibility. For example, my canvas using the segment starts at 11:30am every day and takes users with the custom attribute more than 1 day ago (because I want to make users entered if they had the custom attribute performed at least yesterday or before). However, if the the value of this custom attribute was indeed the previous day but at 12:30pm, then it means the user is not eligible to enter the canvas. So it's not answering my need. Apart from changing the starting hour of my canvas, or the "X" days in my filter (to 0 instead of 1), I was wondering is there a way to "ignore" the hour in a timestamp in a segment filter to just take into account the date, when my custom attribute is build with both? Thank you!
