Hi everyone 👋
I’m looking for some guidance on how to effectively test Canvas journeys that use Context variables.
We’ve got several high-priority use cases where Context is essential (e.g., assigning voucher codes using Connected Content), but we’ve realised that Context isn’t supported in the Test Canvas feature. This makes it really difficult to validate personalisation, since variables won’t populate during testing — forcing us to rely on live sends to internal test accounts.
Has anyone found a good workaround or best practice for testing these kinds of setups? Would be good to hear how others are handling this.
Thanks
Hey tom_rowbo​
Adding to Ted's comment about restricting entry (which is a huge go to for me), if you have access to, or are willing to learn an API tool such as Postman or Bruno, you can trigger the canvases remotely and send any sort of payload and properties you like to test a flow. They are also universally used tools across tech, so the knowledge will never go to waste.
You hit the nail on the head - test internally.
Publish the canvas, but restrict entry to specific users by limiting to email, phone, or other unique identity, then take the action needed to put them into the flow (Also suggested is shorten any waits and allow reentry so you can test rapidly).
Hope this helps.
