Storing Event Data and Using It in a Decision Split - Canvas
Storing Event Data and Using It in a Decision Split I'd like to know if it's possible to set up the following scenario in Canvas. I'm currently sending a custom event with a numeric value related to a purchase. My goal is to store that value so that when a second purchase happens, and the combined total exceeds $50, a Decision Split can send the user down a specific path. For example: If Derek makes a first purchase of $30 and then a second one of $30, the combined total would exceed $50, and he should go down one path. But if Lina makes a $10 purchase followed by another $10 purchase, she wouldn’t meet the threshold and should go down another path. From what I understand, this seems difficult (if not impossible) to do, since Canvas doesn’t store the value of the first purchase while waiting for the second event to arrive.
Databricks and Braze Integration with CDI: Alias Management
Hello! I'm currently integrating Databricks tables with Braze using a CDI. I'm wondering if there's a way to include alias_name and alias_label when adding new users or updating existing users' values through CDI. I've been referencing the Braze documentation to configure my table schema, but the alias_name and alias_label values I've added to it aren't being updated. (https://braze.com/docs/en/user_guide/data/cloud_ingestion/integrations) Additionally, I'm curious if it's possible to add a new user by including both custom attributes and aliases together using the user/track API endpoint.
User Data Export with callback endpoint
Hey hey! Hope y'all doing well. Has anyone ever exported User Data using not currents but a callback endpoint? I'm currently trying to automate exporting user data from a given segment using a callback endpoint. I'm using a Pub/Sub topic in GCP to do this. The problem is that I don't fully understand the mechanisms on how Braze publishes the URL to download the folder containing the user data in the payload response, after the API call. For example, if I'm exporting a big segment (10k+), the response from Braze is immediate: { "message": "success", "object_prefix": "812ad47c-451b-4d0a-b158-6d33713ba07b-1734705464", "url": null } But the URL is still not available (probably due to the size of the segment). My idea was to set a Pub/Sub topic which would be populated with the URL once it is ready, but I don't know what is the mechanism that Braze uses to update the URL in the payload response. I know it's a narrow specific problem, but any ideas, suggestions, or provocations would be of amazing enlightenment to me. Thank you!
Redshift cloud data ingestion
Hi folks, I am planning on using Cloud data ingestion in Braze and now my pipelines are setup via API pushes to Braze. I am interested to know the insights from someone that have already got this on redshift and if all API endpoints such as user/track, all types of events (custom and purchase) and custom attributes can be hosted on Redshift.
