This section introduces how attributes and journeys are defined, surfaced, and managed within the user interface. These updates improve visibility, consistency, and safety when configuring real-time behaviors and personalization logic. This document addresses common questions regarding attribute visibility, batch-to-real-time synchronization, event definitions, and rollback handling.
Batch attributes become visible in the Real-Time UI only after they are explicitly imported into the Real-Time configuration. This ensures that only the most relevant and up-to-date attributes are available, preventing an overwhelming display of all batch data. Only attributes selected during setup (via the “Add Attributes” tab in Data Workbench) will appear in Real-Time Journey or Personalization screens.
Batch attributes refresh when their Parent Segment is updated.
Newly added attributes in batch tables are available after the next synchronization.
Real-time attributes always take precedence for in-session decisions.
Real-Time 2.0 includes validation checks at save time to prevent invalid configurations. If errors occur, users can manually revert to the last saved version. Automatic rollback of attribute or journey configurations is not currently supported, but future enhancements will introduce versioning to facilitate safe recovery from misconfigurations.
Always test configuration changes in a staging environment before deploying to production.
Utilize CI/CD configuration backups for rollback if necessary.
In case of API errors, Real-Time APIs return descriptive error messages (4XX/5XX codes).
Real-Time 2.0 now enables batch attributes to be imported directly into the Real-Time configuration. Once imported, these attributes can be used in personalization payloads or trigger conditions. Their values refresh whenever the Parent Segment refreshes in batch, ensuring consistency between batch and real-time datasets.
Batch attributes are read-only in real-time; updates originate from batch refresh cycles.
Real-time payloads can include both batch and real-time (RT) attributes (up to 20 total).
Importing batch attributes does not affect data latency, as they are refreshed asynchronously.
Event definitions in Real-Time 2.0 offer greater flexibility and support for complex logic. While there is no hard limit on the number of event definitions, the total filter length cannot exceed 1000 characters. Users can define counters, lists, or single-value attributes and configure them directly from the Real-Time UI. These definitions power triggers, journeys, and personalization logic.
Flexible attribute types: single, list, and counter.
Batch backfill support to initialize RT attributes with historical data.
Auto-detection of new event fields for configuration as RT attributes.
Simplified management within the Real-Time configuration UI.
Import only attributes essential for personalization to maintain fast (<100ms) response times.
Validate event definitions to ensure they remain within the 1000-character filter limit.
Employ CI/CD pipelines for consistent configuration across environments.
Future releases will include configuration versioning and rollback support.