Skip to main content
This document covers the helper APIs for reporting impressions and clicks when you fetch personalized experiences through the MoEngage Personalize REST API. Use this page if your app calls the Personalize API directly from your server.
If you are integrating MoEngage Personalize natively from your Android app, use the Personalize SDK instead. The Personalize SDK fetches experiences and tracks impressions and clicks through a single helper, so you don’t need the APIs on this page.

​
Prerequisites

​
SDK version

You must update your Native Android SDK catalog version to 5.2.0 or higher.

​
MoEngage Account Configuration

Ensure your MoEngage workspace is enabled to utilize the Personalize API. Refer to this article for details on setting up Personalize API experiences.

​
Reporting Experience Shown events

The SDK provides helper APIs to track shown events; please refer to the API documentation for more details. Impressions should be reported when an experience is visually presented to the user.

​
Single Experience

To report an impression for a single experience, pass the experience_context of the experience as a map. experience_context is a JSON object that is returned as part of the response of the Personalize API request.

​
Multiple Experiences

To track the experience shown event for multiple experiences, pass the list of experience_context of each experience as a map.

​
Reporting Experience Clicked events

The SDK provides helper APIs to track clicked events; refer to the API documentation for more details. Clicked events should be reported when a user clicks on any element that has been personalized using the response of the Personalize API.

​
Single Experience

To report a click event for a single experience, pass the experience_context of the experience as a map.

​
Multiple Experiences

To track the experience shown event for multiple experiences, pass the list of experience_context of each experience as a map.
You can optionally include a b_id key in the experience_context object to provide additional context about the click. Its value should describe the specific component or interaction within the experience that was clicked. This is particularly useful for experiences composed of multiple interactive elements, helping to distinguish between clicks on different parts of the same overall experience.