Change in User Attribute campaigns trigger personalized messages when a specific user attribute changes. This campaign type supports powerful behavioral and lifecycle messaging based on shifts in user data.
Trigger logic
Trigger conditions
A message is triggered when a user attribute value changes. For example:
- Loyalty tier changes from “Silver” to “Gold”
- Loyalty points cross a defined threshold
- Region or language preference is updated
Supported value types are strings and numbers. Support for date values is planned for later this year.
Evaluation logic
- Changes are evaluated once a day, at the end of the day.
- The current feed is compared to the last synced User Data Feed—as long as it wasn't synced on the same day (if it was, the same-day sync is ignored, and the feed is compared to yesterday's sync).
- Works the same for both CSV and API-based feed updates.
Schedule
- This campaign type uses a schedule (not a wait time).
- Messages are sent in the next available scheduled window after a qualifying change.
- You can configure which days of the week messages can be sent.
Send to
- Messages are sent only to users who meet the specific attribute change condition.
- You can also send the campaign to a particular audience (select in the Send to field) in addition to the trigger condition.
Don’t send if (cancel conditions)
- There are no built-in cancel conditions.
- Unless the global cap of 5 message per user every 24 hours is hit, messages are sent.
- You can configure delivery rules or frequency limits in the campaign settings to manage messaging volume.
Prerequisites
- You must have an active User Data feed configured for your account.
- The feed must use the section’s primary identifier (CUID).
If you need assistance setting up your User Data feed, see our Dev Docs or contact your customer success manager for assistance.
Message content configuration
Change in User Attribute campaigns support the following variable types:
-
User data variables
You can use any fields from the User Data feed, such as:- Loyalty tier
- Points balance
- Recent activity indicators
- Region, language, or other profile attributes
-
Recommendation blocks
- Use any strategy and set Reconnect App as the page type.
- Contextual strategies can use recent user behavior or attributes to personalize the output.
Best practices
- Avoid overly broad triggers to avoid high message volumes.
- Test on a limited segment before scaling to your full user base.
- Sync your feed regularly to maintain accurate and current trigger logic.
FAQs
Q: What kind of attribute changes can be used as triggers?
A: Any change in a string or number value from the User Data feed.
Q: Can I use feeds that don’t use CUID as the identifier?
A: No. Only User Data feeds that use the section’s primary identifier (CUID) are supported for this campaign type.
Q: Can I define multiple trigger conditions in a single campaign?
A: No. Each campaign supports one attribute change condition, but you can layer additional audience filters.
Q: What happens if a user’s attribute changes multiple times in a single day?
A: Only one change per attribute per user is evaluated each day, based on the final state at the time of evaluation.