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 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
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
              }
            ]
          }
        ]
      }
    ]
  }
}
{
  "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.

Updated 25 Sep 2024

Engine API and Caching Rules

Target, Event, & Condition Mapping