Hey all, I have a Canvas with 15 message steps for different stores, and I need to cap user entry for each message step. Each step has a different entry limit, and if one store reaches its limit, the audience needs to move to the next store, and so on through the rest.
I tried a workaround using the Catalog (Synchronous) API as a tracker; each time a user enters a step, the tracker increments by 1, and when it reaches the limit, users move to the next step. Unfortunately, the rate limit for updating the catalog through the API isn't sufficient, and there's significant latency when multiple users enter simultaneously. I don't want to create 15 separate Canvases for this. Has anyone worked on limiting users at message step level?
Hi HariSirigiri1,
This is a really interesting use case. Just like we have Context Variables that work at the user level, it would be incredibly useful if Braze offered something like global context variables or even step-level frequency caps. That kind of capability would solve your scenario cleanly.
A couple of clarifying questions that would help determine what’s possible:
In other words, do you expect a predictable number of users entering the Canvas each day, or does this fluctuate?
Is it:
We need more details on this one, especially on the entry, what message(s) in each step, and what you really need to accomplish and why (the end result you are looking for). A screenshot of your canvas with be helpful.
As described, this isn't gong to be supported directly and if this is meant to be ongoing, if there was a limit per step, eventually each step would be full, and you would run of steps if it worked as describes.
You could make this work one time with a few experiment paths.
