Target, Event, & Condition Mapping

if your site leverages the engine api, you must ensure to include in engine api requests the information necessary for https //docs monetate com/docs/types of who targets and https //docs monetate com/docs/action conditions target type mapping this table contains the who target types and their respective associated engine api events location targets all targets engine api events docid\ ucail fi7yejd8vuctl9v and docid\ jqhwkd5f0toptc0rtog31 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 weather targets all targets engine api events docid\ ucail fi7yejd8vuctl9v and docid\ jqhwkd5f0toptc0rtog31 send coordinates for greater location precision you can send both ip address and coordinates in the same request us demographics targets all targets engine api events docid\ ucail fi7yejd8vuctl9v and docid\ jqhwkd5f0toptc0rtog31 send coordinates for greater location precision you can send both ip address and coordinates in the same request technographics targets browser device type operating system html5 capable engine api event docid\ ngmnvrdcuytmtldlguyyr targets screen height screen width screen resolution engine api event docid\ y7cey7c6d5n9hymz0ftwk landing targets custom variable visitors custom variable visitors with multiple values engine api event docid\ qwxoawfdbwnx4zarj hah the monetate\ context\ customvariables event is also used in place of https //docs monetate com/docs/create targets for web experiences 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 docid\ dqvbbtiobbxpkzsgqvzo9 target direct navigation visitors engine api event no event required because a customer matches with the absence of docid\ dqvbbtiobbxpkzsgqvzo9 targets initial url query string landing page match last external landing in past hours contains engine api event docid 0s1uvo4ctyzdyzrpvevdn the monetate\ context\ pageview event references the url parameter for evaluation behavior 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 docid\ cclzbgzdajwm9hubh3fbi 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 docid 1wbw8jiq4stq8kcorsh2n 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 docid 0qyzqpap6dhh9e bnp6iy 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 docid 7zmq7 m ntbvwl6ksow8w yo u must als o 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 datasets 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 https //docs monetate com/docs/action conditions#available action conditions and their respective associated engine api events action condition engine api event notes page type docid 0s1uvo4ctyzdyzrpvevdn references the pagetype parameter url docid 0s1uvo4ctyzdyzrpvevdn references the url parameter time based on request evaluation time cart value docid\ cclzbgzdajwm9hubh3fbi landing page not currently supported page breadcrumb docid 0s1uvo4ctyzdyzrpvevdn references the breadcrumbs parameter page category docid 0s1uvo4ctyzdyzrpvevdn references the categories parameter product detail page docid 0qyzqpap6dhh9e bnp6iy product list page docid 9vi5lbvf0klh3qj6xa2 e custom variable docid\ qwxoawfdbwnx4zarj hah 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 docid\ zfxs45ymf6aicwwkkgxcc , the event could be counted twice in the experience analytics see docid\ z7zs1bulqpt 0z1coyhww in docid\ z7zs1bulqpt 0z1coyhww 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 docid 1wbw8jiq4stq8kcorsh2n add to cart rate cart abandonment rate docid\ cclzbgzdajwm9hubh3fbi bounce rate average page views not currently supported average time on site based on the monetate session api events docid\ x7k8z81a g9bobqmny0hb recommendations impressions docid\ vgkez dw5gcpo7dpqfw41 recommendations clicks docid\ mb dqxgu5doqcbjiqrlqy 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 = callout of the 'page type = option' in the 'page type' category of the action conditions selector for an omni json action template in the monetate platform 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 docid 0s1uvo4ctyzdyzrpvevdn 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" } ] }