New in communication activities

What’s new

• Banner activities can be triggered via Orchestration, using a Member Segment or an Event to control which customers see the banner in the mobile app.
• Banner validity. Triggered banners now support a Validity period (in days). It defines how long the banner remains visible from the execution time, per customer. If no validity is set, the banner remains visible until the Banner activity end date.
• Prompt activities can now be triggered via Orchestration using an Event. Prompts are triggered in real time when a customer performs an event, such as completing a challenge or making a purchase.
• Prompt validity. Triggered prompts now support a Validity period (in days). It defines how long the prompt remains visible from the execution time, per customer. If no validity is set, the prompt remains visible until the Prompt activity end date.
• Feed activities can now be triggered via Orchestration using an Event. Feed activities are triggered in real time when a customer performs an event, such as completing a challenge or making a purchase.
• Feed validity. Triggered feed activities now support a Validity period (in days). It defines how long the feed item remains visible from the execution time, per customer. If no validity is set, the feed item remains visible until the Feed activity end date.

One activity per flow

• Before: each execution of a flow containing a Feed or Prompt activity created a new activity instance. If a flow ran 10 times, 10 duplicate Feed or Prompt activities were created.
• Now: a single Feed or Prompt activity is reused across all executions of the flow.

• No unnecessary duplication of activities.
• More clarity and traceability in Campaigns and activity lists.
• A cleaner and more predictable execution model.