ContributionsMost RecentMost LikesSolutionsRandomisation of users filtered by a segment for a canvas or campaign Hi there, I was just wondering if anyone could clarify whether or not user selection for canvases / campaigns is randomised, or will users always be entered into a canvas in the same order after running through segments and filters? I thought I'd read somewhere that user entry into a canvas is random, but now I can't find reference to that anywhere. Basically, if we had a canvas that entered a given number of users every day based on some criteria, would it always be the same set of users that are entered, or would this be random? Thanks in advance. SolvedSegmenting on a custom location field Hi all, I've currently got a use case where I want to target a Braze canvas at customers who have previously ordered within a given radius of a specific location. We don't use Braze's SDK based location tracking, and don't need to (we don't need that granularity, and don't need real time location of customers), but do have location points that we would like to use and segment on. The way I'd like to do this is: Store the location we're interested in as custom property on the customer's profile as lat / long. Use this custom to be the centre of a location radius in a segment filter. In the same way as we can do for `most recent location` as shown in this screenshot: I can't find any reference to a location data type for custom properties. Clearly Braze is capable of doing such location based calculations, and has the concept of location - but this seems to be something that is very tightly coupled to use location tracking in the SDK, and not more arbitrary location operations. We don't want to be tracking users as such, but do have specific relevant locations stored in our system. We'd like to be able to send these over to Braze so that we can use them in segment filters - but I can't see anywhere in the documentation whether this is possible or not. At present we are able to use connected audience filters to segment based on postcodes (using a regex), but we'd prefer to be more accurate re radius from a given point. Any help or pointers with this would be hugely appreciated. Use most recent location in connected audience filters Hi All, This conversation is related to a previous conversation I started about segmenting on locationbut is more related to API Triggering of canvases. I have a use case where I want to do some location based filtering, (e.g., select users with a most recent location inside an X miles radius of location Y). We can do this in the Braze UI quite easily, but unfortunately this requires static data from what I can see. We can't use a dynamic centre point or distance, e.g. using liquid or some other way of getting variables in. In other uses cases where we've needed to do dynamic filtering with API triggered canvases, I've used connected audience filters and passed them in with the API trigger. However, in this case I'm not sure it's possible - the documentation doesn't seem to specify anything around doing location based filtering or geofences. Just wondering if anyone has done anything similar? Or has any solutions? I've considered doing max latitude / min latitude, max longitude, min longitude type filtering, but it really needs to be radius based to fit in with some other requirements. Re: Randomisation of users filtered by a segment for a canvas or campaign Braze support have just got back to me and confirm that user entry is indeed randomised, so this backs up your findingsAllanHeo. The response from support on this was: "Regarding the entry of users into your canvas, it's indeed will be randomized based on the specific filters you have set for your canvas. However, in your particular case, it's also worth noting that some users who have previously entered your canvas might still qualify to re-enter it after 2 days, depending on the re-eligibility setting you have configured." So, this is good news as it appears that canvas entry does indeed work in the way that I'd hoped. Was a bit worried otherwise as it changes some major assumptions, that may have involved re-working some of our strategies. Thanks all for this, particularlyAllanHeofor your tests to confirm this behaviour. Really useful. Re: Randomisation of users filtered by a segment for a canvas or campaign HiAllanHeo- yes that's right, I'm wanting to confirm if users are entered into a canvas randomly each time a canvas is run. The reason being that I've got some daily API driven canvases that target the same set of users. I use connected content to generate message content, and in some cases this can abort the run for a given user if they don't meet some other criteria on our API. If a user has been sent a message, then they won't be sent the same one again, and we limit the daily sends. Users then become re-eligible to receive after a certain amount of time has passed (time since message sent). What I'm worried about is that if user entry is not random, then over time we'll basically end up only trying to send to people who cannot receive the message. If it's random then this is less of an issue. I had assumed user entry was random (I was sure I read that somewhere) but now I'm not so sure. I'm in contact with Braze support about this, but haven't got anywhere yet. I'll update here when I do. I'd be really interested to hear how your experiment goes. Re: iOS push primers. How to open settings for them? What has worked? What hasn't? Our approach to this has been a wizard as a push primer, shown the first time a user opens the app. The wizard talks the user through the permissions requested and explains why they are needed, and then on a button press we call the native iOS permission request. Otherwise, we rely on the users to navigate to the iOS settings themselves if they want to make changes, but we felt that this is how iOS is intended to be used. Seems to work well so far. If the user declines, that's fine and we don't ask again. Same for location as push. Re: API driven campaign with audience driven by call I'd say this depends on whether you are going to be segmenting on static or dynamic values. If the segment filters can be created using static values e.g., (some_value >= 99 etc) then you are probably better using segments / filters in the canvas or campaign UI as they'll be easier to see and manage going forward. However if you want to segment or filter on dynamic values then I don't think this is possible via the UI (unfortunately we can't use liquid in filters) so in that case you'd probably want to use connected audience filters in your API call to filter on the dynamic values (e.g, some_property >= some_variable) etc. It would be nice if we could do more dynamic filtering in the UI, but it seems as if connected audience filters are the way to go here. Much more of a coding burden in using connected audience filters though - but if you are triggering via API calls anyway then it's maybe not so bad to pass in some connected audience data. Re: Segmenting on a custom location field The radius will change per canvas run. Basically for each run of the canvas I want to segment on users who have last ordered from a given point which is inside a radius from another point. So, although I can now set a location field for users, I can't figure out how to use this in a dynamic way. I use connected audience filters via the API to handle dynamic segmentation. Connected audience filters seem to cover most data type and allow us to create filters on most of the data types handled by Braze.. except for location. Braze must be able to do this behind the scenes, but the question is how do we do this dynamically? I can now do it via the UI. But that would mean (for us) creating a new canvas every time we want to send to customers for a different central point. This needs to be dynamic for us as it's going to be triggered in an automated way daily with different criteria. Re: Segmenting on a custom location field HiDavidO, thanks for this. What I was trying to understand here was whether it would be possible do e.g., radius checks on specific locations without having to track users via the SDK. I've since realised that we can explicitly set the `current location` user property (https://www.braze.com/docs/user_guide/engagement_tools/locations_and_geofences/location_tracking/#hard-setting-the-default-location-attribute). So, although this isn't a custom property it would probably satisfy what I'm trying to do. However, my next blocker is how to trigger this dynamically. E.g, I'd want to set the radius to include users for to be a dynamic property, different for each invocation of the canvas (I'm triggering these via API call). I think the best bet here would be using connected audience filters, but I can't see from the Connected Audience Filter docs (https://www.braze.com/docs/api/objects_filters/connected_audience/) whether it's possible to trigger a condition something like "Most recent location must be within a circle of X Miles" etc. Seems like this might be missing from connected audience filters... or I've not worked out how to do it yet.