WebConnector Configuration Enhanced Pages

Use the Enhanced Pages page to map page-specific settings to a URL pattern. For example, you might set up a page mapping such that any incoming URL containing the text "index.htm" displays your general welcome page, with specific page load events and interaction points defined for that mapping.

Note: Configuration settings on this page correspond to the pageMapping section of the jsconnector.xml configuration file.

To use the Enhanced Pages page to create a new page mapping, click the Add a Page link and complete the necessary information for the mapping.

Page Info

The Page Info configuration options for the page mapping define the URL pattern that acts as the trigger for this mapping, plus some additional settings for the way this page mapping is handled by Unica Interact.
Setting Description Equivalent setting in jsconnector.xml
URL contains

This is the URL pattern that the Web Connector should watch for in the incoming page request. For example, if the requesting URL contains "mortgage.htm" you might match that to your mortgage information page.

 <urlPattern>
Friendly name for this page or set of pages

A meaningful name for your own reference that describes what this page mapping is for, such as "Mortgage Information Page".

 <friendlyName>
Also return offers as JSON data for JavaScript use

A drop-down list to indicate whether you want the Web Connector to include the raw offer data in JavaScript™ Object Notation (http://www.json.org/) format at the end of the page content.

 <enableRawDataReturn>

Events to fire (onload) when a visit is made to this page or set of pages

These set of configuration options for the page mapping define the URL pattern that acts as the trigger for this mapping, plus some additional settings for the way this page mapping is handled by Unica Interact.

Note: Configuration settings in this section correspond to the <pageLoadEvents> section of the jsconnector.xml.
Setting Description Equivalent setting in jsconnector.xml
Individual events

A list of events that are available for this page or set of pages. The events in this list are those that you have defined in Unica Interact, Select one or more events that you want to occur when the page is loaded.

The sequence of Unica Interact API calls is the following:

  1. startSession

  2. postEvent for each individual page load event (provided you have defined the individual events in Unica Interact)

  3. For each Interaction Point:

    • getOffers

    • postEvent(ContactEvent)

 <event>

Interaction Points (offer display locations) on this page or set of pages

These set of configuration options for the page mapping allow you to select which Interaction Points appear on the pageUnica Interact.

Note: Configuration settings in this section correspond to the <pageMapping> | <page> | <interactionPoints> section of the jsconnector.xml.
Setting Description Equivalent setting in jsconnector.xml
Interaction Point name checkbox

Each Interaction Point that has been defined in the configuration file appears in this section of the page. Selecting the checkbox next to the name of the Interaction Point displays a number of options available for that Interaction Point.

 <interactionPoint>
HTML Element ID (Unica Interact will set the innerHTML)

The name of the HTML element that should receive the content for this Interaction Point. For example, if you specified <div id="welcomebanner"> on the page, you would enter welcomebanner (the ID value) in this field.

 <htmlElementId>
HTML Display Type

A drop-down list that allows you to select the HTML Display Type (the HTML snippets, or .flt files, defined on a previous Web Connector configuration page) to use for this Interaction Point.

 <htmlSnippet>
Maximum number of offers to present (if this is a carousel or flipbook) The maximum number of offers that the Web Connector should retrieve from the Unica Interact server for this Interaction Point This field is optional, and applies only for an Interaction Point that regularly updates the offers presented without reloading the page, as in the carousel scenario where multiple offers are retrieved so that they can be made available one at a time. <maxNumberOfOffers>
Event to fire when the offer is presented The name of the contact event to be posted for this Interaction Point. <contactEvent>
Event to fire when the offer is accepted The name of the accept event to be posted for this Interaction Point at the time that the offer link is clicked. <acceptEvent>
Event to fire when the offer is rejected

The name of the reject event to be posted for this Interaction Point.

Note: At this time, this feature is not yet used
 <rejectEvent>