WHO Targets in Omnichannel Experiences

omnichannel experiences support most who targets that you can use in an experience built for a types of implementations implementation, with the exception of a few that rely on data specific to monetate tag–based integrations in an engine api implementation, information such as ip address, used to determine the location and related information, and user agent, from which device type and operating system are derived, aren't available to monetate and must be provided in the body of the engine api request, as shown in this example example engine api request with events for user agent and ip address { "channel" "a 927c8120/p/example com", "monetateid" "5 275061469 1543777025730", "events" \[ { "eventtype" "monetate\ decision\ decisionrequest", "requestid" "11111", "includereporting" true }, { "eventtype" "monetate\ context\ useragent", "useragent" "mozilla/5 0 (macintosh; intel mac os x 10 13 6) applewebkit/537 36 (khtml, like gecko) chrome/70 0 3538 102 safari/537 36" }, { "eventtype" "monetate\ context\ ipaddress", "ipaddress" "198 51 100 0" } ] }