Where outbound content contains a smart asset, other than a goal or advanced smart asset, content is inserted appropriately in accordance with the smart asset’s content elements list. RPI works through the list of content elements, starting at Content 1 and moving down the list. Each is checked in turn to determine whether a recipient qualifies to receive the content defined at the content element. Content is served by the first content element at which a recipient qualifies to receive it.
Determination of applicability at a content element is carried out in accordance with the smart asset type:
•Attribute smart asset: the content is applicable if the recipient’s attribute value matches one of the content element’s configured attribute values.
•Audience segment smart asset: the content is applicable if the recipient was targeted within an audience segment matching one of the content element’s listed segment names.
•Rule smart asset: the content is applicable if the recipient is targeted by the content element’s selection rule or realtime decision.
•Model smart asset: the content is applicable if the recipient falls within a model project band.
Default content, where provided, is served where no match occurs; if no default content is specified, no content is delivered. If a content element itself is configured with another smart asset, the rules in the nested smart asset are themselves executed to determine asset applicability.
If the smart asset is executed in Batch Outbound mode, content applicability is determined at interaction workflow execution, prior to message delivery. This means, e.g. in the case of an email, that email content will remain the same, no matter how many times viewed by a recipient.
If the smart asset is executed in outbound realtime mode, content applicability is determined using the RPI Realtime service. This means, e.g. in the case of an email, that email content can be varied dynamically when viewed a number of times by a recipient (subject to any stickiness settings).
Note that a runtime validation error will be raised at interaction execution if attempting to execute a workflow containing a smart asset using outbound realtime, when system configuration setting EnableRPIRealtimeServices is set to False, and when RealtimeAPIAddress has not been configured.
Smart assets used in outbound realtime mode are published automatically at interaction execution. When a smart asset contains local image content, that content is published to the Default smart asset location, as defined at an external content provider. If this property has not been set, a runtime validation error is raised.
Note that, if using outbound realtime at an email offer, certain email client applications may by default cache image content. This means that the dynamic variation of such content in the inbox may be compromised. This can be avoided by setting HTTP headers appropriately at the provider at which image content is hosted.