Implement Third-Party Analytics

for monetate tag–based experiences , third party analytics integrations can be set up that execute client side and send reporting labels directly to a vendor (for example, google analytics) only experiences for which third party reporting is enabled have their labels submitted for engine api experiences, no formal third party integrations are available instead, the engine api response can include reporting metadata these labels are made available when the includereporting=true flag is added to the model monetate\ decision\ decisionrequest event the requesting application is responsible for passing the metadata along to the preferred third party analytics provider example decision request with includereporting flag { "channel" "a 12345678/d/example test", "monetateid" "5 977810341 1521134874631", "events" \[ { "eventtype" "monetate\ decision\ decisionrequest", "requestid" "11111", " includereporting" true }, { "eventtype" "monetate\ context\ ipaddress", "ipaddress" "127 0 0 1" }, { "eventtype" "monetate\ context\ pageview", "url" "https //www example test/path" } ] } response { "meta" { "code" 200 }, "data" { "responses" \[ { "requestid" "11111", "actions" \[ { "actiontype" "monetate\ action\ omnichanneljson", "impressionreporting" \[ { "experience label" "omni tpa test 1", "variant label" "b", "is control" false } ] } ] } ] } } the flag tells the engine api to return information about the experiences being served