The Data Update Trigger in Blueshift allows you to update user, transaction, or interest attributes directly within a journey. This trigger is available across journey types, including Segment, Event, Recurring, and One-Time Send campaigns, except for Live Content campaigns.
Accessing the data update trigger
- Create or open an existing journey in the Journey Builder.
- In the Choose a Trigger panel, locate and select Data Update under the Data section.
Adding delays, filters, and conditions
Delay
Set a delay before the trigger executes.
Please check out the trigger delays, dayparting, and send time optimization guides for more details on delay options.
Filters
Add conditions to refine which users qualify for the Data Update action.
For further details, refer to the Branching using filters user guide.
Configuring the data update trigger
Once delay and filter settings are configured, you can configure the main attributes in the Data Update Trigger. Here’s how to set up each attribute type:
-
Type selection
- Select the type of attribute you want to update:
- User attributes: Modify general user profile information.
- Transactions: Update attributes related to specific transactions.
- Interest: Manage subscription status for specific interests.
- Select the type of attribute you want to update:
-
Configuring each attribute type
-
User attributes:
- Attribute: Select the specific user attribute you want to update from the dropdown list.
- Value: Specify the new value using a Liquid expression (e.g., {{user.subscription_status | default: "action_movie_plus"}}.
-
Transactions:
- Transaction: Choose the type of transaction to update.
- Attribute: Select a specific transaction attribute.
- Value: Enter the desired value using a Liquid expression.
-
Interest:
- Topic: Select the interest topic.
- Value: Choose to subscribe, unsubscribe, or flip subscription status.
-
User attributes:
Saving, validating, and launching
- After configuring the Data Update settings, click Save.
-
Review and validate: Before launching, thoroughly review each configuration to ensure all conditions and updates are set as expected. This includes:
- Check all delay and filter settings to ensure the correct criteria are applied.
- Ensuring the attribute values are correctly entered, primarily if they use Liquid expressions.
-
Launch the journey:
- Once validated, return to the journey overview.
- Click on Launch to activate the journey with the Data Update Trigger.
-
Monitoring:
- After launch, monitor the journey’s performance under the Reports tab of the campaign to verify that the trigger operates as expected. Check if user profiles, transaction details, or interest subscriptions update correctly based on the trigger setup.
Use cases for data update trigger
Example 1: Subscription Level Update Using Loyalty Tier from Triggering Event
Scenario: A user's loyalty tier is updated based on a recent event.
Action: The journey triggers a data update to set the user’s subscription level according to the loyalty tier in the event.
Configuration:
- Attribute: subscription_level
- Value: {{ bsft_event_context.loyalty_tier }}
Explanation: This Liquid expression captures the loyalty_tier attribute from the triggering event (bsft_event_context.loyalty_tier) and assigns it to the user’s subscription_level. This update is limited to event-triggered campaigns, as it relies on the event context.
Example 2: Subscription to Interests Based on Engagement
Scenario: A user clicks on a "Winter Sale" announcement email, indicating interest in seasonal promotions.
Action: The journey triggers a data update to add the user to the "Winter Sale 2024" interest group, allowing the brand to send targeted sale notifications to those interested in seasonal offers.
Outcome: This setup enables automated follow-ups for users interested in winter deals. By focusing updates on engaged users, the brand enhances engagement and ensures that only those with a clear interest receive these notifications.
Comments
0 comments