|
|
Complete this tab to configure the desired behaviors for the Real-Time Container.
Is this Container currently active?
Use this setting to specify whether the Real-Time Container is enabled. Choose between:
Yes, this Container will respond to requests - Select this option to enable the Real-Time Container and have it respond to requests.No, this Container will not respond to requests at this time - Select this option to prevent the Real-Time Container from responding to requests. If an inactive Real-Time Container is triggered, it will simply be ignored.Impression Capture
Use this setting to specify the desired impression capture behavior when this Real-Time Container is requested. Choose between:
Captured on retrieval - Select this option to have the Real-Time Container processing API automatically capture an impression before rendering this Container.Captured by channel - Select this option to not capture the impression while rendering the Container. In this case, the channel will need to separately invoke the impression capture API.Click through behavior
Use this setting to specify what should happen when the channel invokes the click-through capture API. Choose between:
Capture click through only - Select this option to simply record a click in Interaction History (IH).Capture click through and initiate offer flow - Select this option to record a click in IH and to initiate the Offer for the customer. If the Offer is already in flight for the specified customer, it is progressed along the Inbound path. If the Offer is not currently in flight for the specified customer, the system instantiates a new Offer and starts executing it.
The click-through URL is configured on the Details tab of the Offer rule form. This URL can also be over-ridden in the Strategy. For proper re-direction, this URL should begin with the protocol prefix - such as http:// or https://.
This section lists the Multi-Channel Campaign work objects that have been associated with this Real-Time Container. The following information displays for each Campaign:
Column Heading |
Description |
| Associated Campaign | Displays the name of the Campaign. Click the name to open the Campaign work object. |
| Enabled | Displays whether this Campaign currently has Container processing enabled on it. |
| Start Date | Displays the date and time when this Container becomes active for this Campaign. |
| End Date | Displays the date and time when this Container stops being active for this Campaign. |
| Status | Displays the current status of the Campaign work object. |
This section displays the NBA configuration that has been associated with this Real-Time Container. Click the link in the Associated NBA column to open the corresponding NBA configuration.
This section displays the Supporting Decision configuration that has been associated with this Real-Time Container. Click the link in the Associated supporting decision column to open the corresponding Supporting Decision configuration.
A Container can have multiple entities - i.e. Campaigns, NBA configuration, or Supporting Decision - associated with it, as long as only one entity is active at any given point in time. While a Container is associated with an NBA configuration or a Supporting Decision, it cannot be used elsewhere since both these constructs are "always-on".
|
About Multi-Channel Campaigns |
About