Forum Discussion
Re-triggering canvas after 30 days
I am trying to build a canvas that:
Is triggered by a custom event. I want that to create a content card. I want that particular content card to be available for 60 days. I can't quite figure out how to do this.
The canvas should really last 120 days, but at 60 days in, I want to create a new content card with different content, and repeat the above by keeping it available for 60 days.
Is there a way to achieve this in the canvas builder?
Hey there,
Content cards can't stay in a feed for more than 30 days. I suggest you can still create the canvas with the following steps:
1. Content card block (last for 30 days)
2. delay block of 30 days
3. Content card
4. Delay of 30 days
5. New content card
6. Delay of 30 days
7. New content card again
Thanks for responding Alex,
The canvas is triggered by an event that has an event property. Is there a way to essentially store that event property and use it in subsequent content cards up to 120 days later? I am getting an error when I try and use an event property that was triggered by the initial event:
"Event properties may only be used in action-based Full steps or Message steps that advance through a path (except the Everyone Else path) of an Action Path step triggered by purchase or custom events only"
In order to store the entry properties for later use, you need to reach out to your CSM. https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties/canvas_persistent_entry_properties#persistent-entry-properties
You can also save the entry property as a custom attribute before sending the content card. you may end up with a timing issue though if you are using the same attribute for the new content card and the one you want persisted for 60 days. If I am understanding there is an overlap of 30 days between the 2 content cards is that correct?
I have actually descoped this and created 2 canvases now - which makes it much easier. However, I am struggling with persisting event properties from:
Entry schedule > action based options
Am I right in thinking that event properties (let's say first_name) sent via an API should be available in a content card via:
this is some dummy text {{canvas_entry_properties.${first_name}}}
AHH! You are using Canvas Builder and not Canvas Flow, is that correct?
It looks like there are more restrictions for what you can do with Entry properties the original canvas builder.
Are you able to clone to Canvas Flow? This may solve your issue easily.
