Radar

​

Introduction

Radar is a comprehensive location platform that offers geofencing, geocoding, and maps to power location-based experiences across millions of devices worldwide. Its core products include Geofences, Trip Tracking, and Geo APIs.

​

MoEngage and Radar

The integration between MoEngage and Radar leverages the power of location-based data to enhance your marketing campaigns. You can use Radar’s Geo APIs to show nearby places in MoEngage campaigns, providing users with relevant and contextual information. With this integration, you can:

• Send location-triggered and location-targeted messages to increase engagement and conversion.
• Synchronize user attributes and events from Radar to MoEngage.
• Automate campaigns when a user is near a physical store.
• Track a user’s journey to trigger campaigns based on their trip data.

​

Use cases

Integrating Radar with MoEngage helps you solve the following use cases:

• Location-triggered engagement: When users enter or exit a geofence around your physical store, trigger a personalized campaign — such as a promotional message or a special offer — that encourages them to visit.
• Location-targeted campaigns: Send location-based messages to users who are near a specific store or event to drive engagement and conversion with relevant, contextual information.
• Sync user and event data: Automatically sync user attributes and events from Radar to MoEngage. This gives you a unified user profile across both platforms that you can use for targeted marketing.

​

Integration

​

Step 1: Configure MoEngage in Radar

To connect MoEngage to Radar, perform the following steps:

1. On the MoEngage UI, navigate to Settings > Account > APIs.
2. Copy the value under Workspace ID (formerly App ID).
3. In the API keys section, copy the API key on the Data tile.
4. On the Radar dashboard, navigate to the Integrations page and click MoEngage.
5. Set the Enabled option to Yes, then paste your Workspace ID and Data API Key into their respective fields.
6. Select the API Endpoint that matches your MoEngage data center (for example, if your account is not on https://api-01.moengage.com, choose the correct endpoint). After this configuration, Radar automatically sends custom events and user attributes to MoEngage in real time.
7. Set the moengage:customer_id metadata key on each Radar user to map them to the corresponding MoEngage user profile:
   Android

   iOS

   Radar.setMetadata(JSONObject().put("moengage:customer_id", "[email protected]"))
   

​

Send Users and Events to MoEngage

This section outlines how user attributes and events flow from Radar to MoEngage.

​

User Attribute Mapping

The following table shows how Radar user fields map to MoEngage user attributes:

​

Event Attribute Mapping

The following tables show how Radar event fields map to MoEngage user attributes: Event Mapping

[Radar] Geofence Entered

If Regions is enabled, Radar sends the following attributes:

[Radar] Geofence Exited

If Regions is enabled, Radar sends the following attributes:

[Radar] Dwelled in Geofence

If Regions is enabled, Radar sends the following attributes:

[Radar] Place Entered

If Regions is enabled, Radar sends the following attributes:

[Radar] Place Exited

If Regions is enabled, Radar sends the following attributes:

[Radar] Country Entered

[Radar] Country Exited

[Radar] State Entered

[Radar] State Exited

[Radar] DMA Entered

[Radar] DMA Exited

[Radar] Started Trip

[Radar] Updated Trip

[Radar] Approaching Trip Destination

[Radar] Arrived at Trip Destination

[Radar] Stopped Trip

[Radar] Beacon Entered

[Radar] Beacon Exited

​

Display Nearby Places in MoEngage Campaigns

Use the Radar Geo APIs to enrich your campaigns with dynamic, location-based information — such as displaying nearby places directly inside a campaign message. This involves setting up a MoEngage Content API that calls the Radar Search Places API.

​

Step 1: Set up a MoEngage Content API

To set up a MoEngage Content API, perform the following steps:

1. On the MoEngage UI, navigate to Settings > Advanced settings > Content API.
2. Click + Add content API in the upper-right corner. The Add content API dialog box appears.
3. Configure the API endpoint URL:
   1. In the API name box, type a descriptive name for the API (for example, RadarNearbyPlaces).
   2. Under Method, select GET.
   3. In the URL box, paste the Radar Search Places endpoint with the user’s latitude and longitude as parameters:
      https://api.radar.io/v1/search/places?near={{UserAttribute['Latitude']}},{{UserAttribute['Longitude']}}&chains=starbucks&limit=5
      
      The endpoint URL varies depending on your use case. For all supported parameters, see the Radar Search Places API reference.
4. In the URL Parameters section, specify your chains.
   If your project has a chain mapping, use the mapped ID instead of the chain slug.
5. Under Headers, provide the required key-value pair (for example, Authorization: <your-api-key>).
6. Under the Dynamic values section, define keys and their corresponding values.
7. Click Save.

For more information about Content APIs, see Content APIs.

​

Step 2: Display Places Inside MoEngage Campaigns

After setting up the Content API, use it in your campaigns to display nearby places:

1. In step 2 of campaign creation, type @. The Personalization dialog box appears.
2. In the Select attribute list, click the Radar Nearby Places Content API you configured in the previous step.
3. Use the MoEngage Templating Language to parse the API response and include the content in your campaign. The Jinja snippet below iterates through the list of places and prints their names:
   {% set response = ContentApi.RadarNearbyPlaces({"params":{"near":"{{UserAttribute['Latitude']}},{{UserAttribute['Longitude']}}","chains":"target,walmart"},"static_params":{},"dynamic_params":{},"request_body":{}}) %}
   {% for place in response.places %}
   {{ place.name }}
   {% endfor %}
   
4. Click Preview to see your campaign rendered with real-time personalization.