Omnichannel Experiences

Target, Event, & Condition Mapping

If your site leverages the Engine API, you must ensure to include in Engine API requests the information necessary for WHO targets and action conditions.
Target Type Mapping
This table contains the WHO target types and their respective associated Engine API events.
Targets: All targets
Engine API events: monetate:context:IpAddress﻿ and monetate:context:Coordinates﻿ 
Send coordinates for greater location precision. You can send both IP address and coordinates in the same request. Send coordinates for greater location precision. You can send both IP address and coordinates in the same request. 
Targets: All targets
Engine API events: monetate:context:IpAddress﻿ and monetate:context:Coordinates﻿﻿
Send coordinates for greater location precision. You can send both IP address and coordinates in the same request. 
Targets: All targets
Engine API events: monetate:context:IpAddress﻿ and monetate:context:Coordinates﻿﻿
Send coordinates for greater location precision. You can send both IP address and coordinates in the same request. 
Targets
Browser
Device type
Operating system
HTML5 capable
Engine API event: monetate:context:UserAgent﻿﻿
﻿
Targets
Screen height
Screen width
Screen resolution
Engine API event: monetate:context:ScreenSize﻿﻿
Targets
Custom variable visitors
Custom variable visitors with multiple values
Engine API event: monetate:context:CustomVariables﻿﻿
The monetate:context:CustomVariables event is also used in place of custom targets because the Engine API doesn't have access to these client-side targets based on cookies, JavaScript variables, and HTML elements. Therefore, you must pass this information using monetate:context:CustomVariables instead.
﻿
Target: New visitors
Engine API event: No event required because a customer matches when monetateId or deviceId isn't present in the request
﻿
Target: Returning visitors
Engine API event: No event required because a customer matches when monetateId or deviceId is present in the request
﻿
Targets
Referrer
Past external referrer in past hours contains
Engine API event: monetate:context:Referrer﻿﻿
﻿
Target: Direct navigation visitors
Engine API event: No event required because a customer matches with the absence of monetate:context:Referrer﻿﻿
﻿
Targets
Initial URL query string
Landing page match
Last external landing in past hours contains
Engine API event: monetate:context:PageView﻿﻿
The monetate:context:PageView event references the URL parameter for evaluation.
Targets
Abandoned cart
Amount in abandoned cart
Amount in cart
Attribute of product in cart
Product in abandoned cart
Product in cart
Quantity in cart
Engine API event: monetate:context:Cart﻿﻿
You must also pass a known monetateId or deviceId to sync past session behavior.
﻿
Targets
Attribute of product purchased
Average order size
Days since last purchase
Last order size
Product last purchased
Product purchased
Products purchased in past days
Purchase frequency
Purchased any product
Purchases in past days
Purchased on or after specified date
Engine API event: monetate:context:Purchase﻿﻿
You must also pass a known monetateId or deviceId to sync past session behavior.
﻿
Targets
Attribute of product viewed
Product viewed
Product viewed last visit
Product viewed this visit
Engine API event: monetate:context:ProductDetailView﻿﻿
You must also pass a known monetateId or deviceId to sync past session behavior. Furthermore, a product catalog is required for attribute-based targeting.
﻿
Target: On-site search terms﻿
Engine API event: monetate:context:SearchView﻿﻿
You must also pass a known monetateId or deviceId.
﻿
Targets
Days since last visit
Experiences seen by user
Sessions in past days
Time on site
Visited on or after specified date
Engine API event: No event required because these targets are based on the Monetate session
You must pass a known monetateId or deviceId to sync past session behavior.
Targets: All targets
Engine API event: No event required because lookup is based on the customerId field in the Engine API request
Action Condition Mapping
This table contains the action conditions and their respective associated Engine API events.
Action Condition
Engine API Event
Notes
Page type
﻿monetate:context:PageView﻿﻿
References the pageType parameter
URL
﻿monetate:context:PageView﻿﻿
References the URL parameter
Time
Based on request evaluation time
﻿
Cart value
﻿monetate:context:Cart﻿﻿
﻿
Landing page
Not currently supported
﻿
Page breadcrumb
﻿monetate:context:PageView﻿﻿
References the breadcrumbs parameter
Page category
﻿monetate:context:PageView﻿﻿
References the categories parameter
Product detail page
﻿monetate:context:ProductDetailView﻿﻿
﻿
Product list page
﻿monetate:context:ProductThumbnailView﻿﻿
﻿
Event/Metric Mapping
Events, such as product views, are counted individually. If this information is recorded by both the Monetate tag and the Engine API, which is possible in a hybrid implementation﻿, the event could be counted twice in the experience analytics. See Retracks and the Average Page View Metric﻿ in Page Retracks﻿ for more information.
For pure Engine API implementations, all event reporting must be passed via Engine API requests. This table contains the default metrics and their respective associated Engine API events.
Metric
Engine API Event
Conversion rate
New customer acquisition rate
Revenue per session
Average order value
﻿monetate:context:Purchase﻿﻿
Add to cart rate
Cart abandonment rate
﻿monetate:context:Cart﻿﻿
Bounce rate
Average page views
Not currently supported
Average time on site
Based on the Monetate session
API events
﻿monetate:record:PageEvents﻿﻿
Recommendations impressions
﻿monetate:record:RecImpressions﻿﻿
Recommendations clicks
﻿monetate:record:RecClicks﻿﻿
Using Action Conditions in Omnichannel Experiences
Similar to Monetate tag–based implementations, you can apply action conditions to the actions you configure in Omnichannel experiences.
For example, if you want an action to appear on a particular page type, click ADD CONDITION, expand the options of the Page type category, and then select Page type =.
﻿
To complete the condition, type the page type into the field and then press Enter. The page type is defined by the setPageType data that you pass to Monetate.
Here is an example request with pageType specified in the monetate:context:PageView﻿ event:
Example Request with pageType Specified in monetate:context:PageView
{
"channel": "a-927c8120/p/example.com",
"monetateId": "5.275061469.1543777025730",
"events": [
    {
      "eventType": "monetate:decision:DecisionRequest",
      "requestId": "11111",
      "includeReporting": true
    },
    {
      "eventType": "monetate:context:PageView",
      "pageType": "home",
      "url": "test/foo"
    }
  ]
}
{
"channel": "a-927c8120/p/example.com",
"monetateId": "5.275061469.1543777025730",
"events": [
    {
      "eventType": "monetate:decision:DecisionRequest",
      "requestId": "11111",
      "includeReporting": true
    },
    {
      "eventType": "monetate:context:PageView",
      "pageType": "home",
      "url": "test/foo"
    }
  ]
}
﻿
﻿

Action Condition	Engine API Event	Notes
Page type	monetate:context:PageView	References the pageType parameter
URL	monetate:context:PageView	References the URL parameter
Time	Based on request evaluation time
Cart value	monetate:context:Cart
Landing page	Not currently supported
Page breadcrumb	monetate:context:PageView	References the breadcrumbs parameter
Page category	monetate:context:PageView	References the categories parameter
Product detail page	monetate:context:ProductDetailView
Product list page	monetate:context:ProductThumbnailView

Metric	Engine API Event
Conversion rate New customer acquisition rate Revenue per session Average order value	monetate:context:Purchase
Add to cart rate Cart abandonment rate	monetate:context:Cart
Bounce rate Average page views	Not currently supported
Average time on site	Based on the Monetate session
API events	monetate:record:PageEvents
Recommendations impressions	monetate:record:RecImpressions
Recommendations clicks	monetate:record:RecClicks

Updated 25 Sep 2024

Implement Third-Party Analytics

WHO Targets in Omnichannel Experiences

Target, Event, & Condition Mapping

Target Type Mapping

Location

Weather

US Demographics

Technographics

Landing

Behavior

Datasets

Action Condition Mapping

Event/Metric Mapping

Using Action Conditions in Omnichannel Experiences