Ignore 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!FAQ: 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!FAQ: What is expected Canvas re-eligibility behavior?
Currently, re-eligibility for variants is tied to Canvas entry rather than message receipt. Users who enter a Canvas and do not receive any messages will not be able to re-enter the Canvas unless re-eligibility is enabled. If re-eligibility for a Canvas is set to shorter than the duration of the Canvas, it is possible for users to enter the Canvas more than once, which can lead to misleading behaviour for Canvases that use IAMs with particularly long delays. Since multiple Canvas IAMs could be triggered by the same session start, the end user could potentially have the experience of receiving the same message repeatedly, if a specific step renders faster than others.Resource: Canvas Flow Component Guide
For those of you getting started with Braze Canvas Flow or exploring new use cases, here is a quick look at the different components you can mix and match in our customer journey management tool!Use as a guide of when to leverage each component while executing user journeys in Canvas Flow. Includes information and use cases for the following components: message, delay, decision split, action paths, audience paths, experiment paths, and audience sync.
