Integrate Commerce with Infinity

This integration establishes a common data ingestion framework for collecting product behavioral data.

This topic explains how the Commerce and Infinity integration establishes a common data ingestion framework for collecting product behavioral data.

To integrate Oracle Infinity with Commerce, events are used as starting point. There are a lot of events which are published from the current store front framework whenever an event takes place in the store user interface. The events used in the integration revolve around actions such as Registration, Login, Cart events, Search, Products viewed, Order placement, and others. These events are subscribed to and are used to send data to Infinity whenever they occur. Specific examples of the data that can be collected include the following:

• Page analytics data (URL, referrer, time on page, browser, device operating system, etc.)
• Commerce specific data
• Products viewed
• Products added to cart
• Categories viewed
• Search terms used
• Order data
• Wish list data

Note: The integration collects data for both account-based and anonymous shoppers.

To collect this data, the presence of an Infinity tag in a site page initiates the download of an Infinity JavaScript. For that to occur, the Infinity tag has to be in a "require" dependency. Infinity provides a long list of event parameters which can accept Commerce data and send it to the Infinity API. Commerce then subscribes to a particular set of these events and provides the mappings to send the data to Infinity.

In summary, the integration works as follows:

• Commerce loads Infinity JavaScript to site pages through a "require" dependency from the Infinity viewmodel.
• Commerce subscribes to particular Infinity events. These are then tracked and bound with methods.
• Commerce data is mapped with Infinity parameters in the methods and this is sent to Infinity for collection.

A new setting for the Infinity integration is provided under the Integrations tab available to Commerce Administrators. After enabling this setting, you must provide the Infinity tag in the Production URL field required for this setting.

A new viewmodel, infinity.js, is also provided. The Infinity viewmodel loads the Infinity script into the browser. Subscriptions to the events to be tracked are added in this viewmodel along with their corresponding methods for correct data mapping. The methods are kept as prototype methods which makes them extendable if you want to add more parameters apart from the provided mappings.

For more complete details on using Infinity and its capabilities, refer to the Oracle Infinity documentation.