Elaine templates turn governed data, reusable content, and decision logic into recipient-level messages. They support real-time hyperpersonalization at scale: content can be resolved for one interaction or individualized efficiently across campaigns involving millions of recipients.
From a layout to a decision-ready template
A template is more than an HTML shell. It defines which parts remain fixed, which parts editors can change, where reusable articles can be inserted, and which content is selected for an individual recipient. Elaine Markup Language (EML) adds this structure and logic to channel-specific markup such as email HTML.
- Composing boxes define managed content areas.
- Articles package reusable or inline content.
- Widgets expose selected text, links, images, lists, and other properties to editors while preserving the surrounding design.
- Placeholders insert recipient, event, transaction, product, recommendation, or contextual values.
- Conditions select complete content blocks for an individual situation.
- Language variants, tracked links, web views, and testing variants are part of the same rendering model.
Connect multiple data sources at render time
Template decisions can combine profile and CRM fields with transaction or event context, Datastore values, product and content information, recommendations, intent signals, and values prepared by Business Rules. JSON-valued fields can also transport structured context into the wider personalization process. The exact fields and access patterns depend on the tenant and integration design.
Depending on the use case, additional data can be resolved only when Elaine renders the message. A source may be queried live, prepared before rendering, or served through intelligent caching. This allows architects to balance freshness, rendering latency, throughput, resilience, and load on connected systems rather than applying one access pattern to every campaign.
Realtime and high-volume execution
The same template and decision model supports fine-grained transactional messages and high-throughput campaign execution. Elaine can apply recipient-level conditions and content combinations in real time while retaining the scalable processing required for audiences of millions. Fallbacks remain essential when a source is missing, delayed, or temporarily unavailable.
Controlled editing
Complex EML articles can expose only the properties that a content editor should change. For example, an editor can update a headline, rich-text area, tracked link, or image without modifying the responsive layout or brand-critical HTML. This separates template engineering from day-to-day campaign production and makes sophisticated personalization reusable.
Privacy-aware personalization
Every data source used by a template must be permitted for the intended purpose. Privacy Admission Control, PAC flags, consent-aware processes, tenant and permission separation, suppression, and privacy-aware defaults help ensure that hyperpersonalization uses governed data. Organizations remain responsible for their legal basis, notices, retention, and configuration.
Technical implementation
Use EML to define template structure, editable widgets, placeholders, conditions, multilingual variants, tracking, and content tests. Start with the technical reference and validate every generated template against the fields and conventions configured for the target tenant.