bob
Specialist
Joined 2 years ago
User Profile
User Widgets
Contributions
Re: Catalog Selections personalization based on array data type
Are we sure that you can take an array variable and pass that in? I suspect that it's only going to work with scalar values. It would be neat though - if it would take all the scalar value in an array, but I can understand why it wouldn't.6Views0likes0CommentsRe: Need help with Regex
Wow, that makes no sense. I've tested this, just in case the docs and my memory were wrong, and ^ and $ absolutely do work in this context to match beginning and end of string. Did this custom attribute have it's type confused? Was it an array at some point and now it's a string?545Views0likes1CommentRe: API to create/update Segments
Why do you need to export this segment of users? I wonder if we knew more about what you're achieving, there might be another solution. This is perhaps something that could be implemented as a webhook campaign and Braze could push the data to a destination. Can you use currents or the snowflake integration? That would let you dump all the data and query it externally. Regardless of anything though, there is a clear gap in the API. If Braze were to create such an endpoint, I feel that they'd want to implement it such a way that it maintained feature parity with the segments in the UI - which is presumably a more challenging thing to implement. I wonder though if it could be limited to those only defined by SQL, which would keep things simple from an implementation standpoint.714Views0likes2CommentsRe: Need help with Regex
Okay, ignore any simple starts-with/contains filters. I thought you only wanted to match when there was a single identifier in the string, so no multiple values and no comma-separation? "...need only that user that has got only one account starting with "o" and they should not have any other account numbers." In which case, the ^ at the start will ensure that the following character occurs at the beginning of the string and the $ at the end will ensure that there's nothing after the preceding matched characters - which in this case are specific enough to only match a single account number.553Views0likes3CommentsRe: Webhook - Add dates
It's a late reply, but might be of use to someone. To output a formatted date using liquid, you'd use: {{ 'now' | date: '%B %d, %Y' }} That would get you 'February 28, 2024'. Importantly there wouldn't be any timezone adjustments based on where the user is - though that's very possible if you need it. I would ask though, what email client isn't going to show the date it was received? Is this an issue that your customers have mentioned? No idea what this would have to do with webhooks though. Maybe I've missed the point.255Views0likes0CommentsRe: Need help with Regex
If there can only be a single instance of the account number, then you could keep it simple using starts with 'o' and does not contain a comma. If you need to more robustly match your account numbers, then you'd need to be more specific with the rules, but given what you've said already, something like this should work. ^o[a-z]{3}-[0-9A-Z]{8,10}$ Using the start and end of string characters (^ and $) to make sure there was only one instance. If you had a list of things that should match and things that should not, I can probably better refine what you're looking for. (and as David said, it's a starting point for a conversation.)611Views1like5CommentsRe: How to loop products from added_item_to_cart events in an email?
Manoj__, I'd be interested if you made progress with this - I was scrolling back through posts after not being around for a while. Do you know what the structure of your added_item_to_cart event is? So far as I know there's no standard definition of which attributes should be populated, so the answer to this is going to be dependant on what your data looks like.530Views0likes1CommentRe: Non-User-Specific Custom Events?
I agree with all the other things mentioned, but if you really want to do this in Braze yourself, you could: Trigger an event/attribute update to a 'fake' user - on that exists in Braze, but doesn't correspond to an actual user. That will cause, for that user, a webhook campaign or a canvas with a webhook step in it... ... that triggers a campaign/canvas for the actual audience via the Braze API. I'm not convinced this is the right way of solving your actual problem, but it could be made to work and would work reasonably well. I'd be really interested in working on this with you if you'd like to reach out.452Views2likes1Comment