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 <> 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 to encourage them to visit. This can be a promotional message or a special offer sent directly to their device.
• Location-targeted campaigns: Send location-based messages to users who are near a specific store or event. This can increase engagement and drive conversions by providing relevant, contextual information.
• Sync user and event data: Automatically sync user attributes and events from Radar to MoEngage. This ensures that you have a unified user profile across both platforms, which you can then use for targeted marketing campaigns.

Integration

Step 1: Configure MoEngage to Radar

To connect MoEngage to Radar, perform the following steps:

1. On the MoEngage UI, navigate to Settings > Account > APIs.
2. Copy the ID under Workspace ID (earlier 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 (if your account is not onhttps://api-01.moengage.com, select the correct API Endpoint).
   After configuration, Radar automatically sends custom events and user attributes to MoEngage in real time.
7. Set the moengage: customer_id metadata to map Radar users to their MoEngage user profiles. For example:

Radar.setMetadata(JSONObject().put("moengage:customer_id", "example@radar.com"))

Radar.setMetadata(["moengage:customer_id": "example@radar.com"])

Send Users and Events to MoEngage

This section outlines the process for sending events and user attributes 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

You can use the Radar Geo APIs to enrich your campaigns with dynamic, location-based information, such as displaying nearby places directly within a campaign message. This process 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.
4. In the API name* box, type a descriptive name for the API (for example, RadarNearbyPlaces).
5. Under Method*, Select GET.
6. In the Url* box, paste the following https://api.radar.io/v1/search/places?near=%7B%7BUserAttribute%5B'Latitude'%5D%7D%7D%2C%7B%7BUserAttribute%5B'Longitude'%5D%7D%7D&chains=starbucks&limit=5  
   The endpoint URL varies depending on your use case. Use the Radar Search Places API to fetch the HTML content of your templates.
7. In the URL Parameters section, specify your chains.
   If your project has a chain mapping, use the mapped ID instead of the chain slug.
8. Under Headers, provide the required key-value pair (for example, add Authorization:<your-api-key>).
   
9. Under the Dynamic values section, define keys and their corresponding values.
10. Click Save.

For more information about Content APIs, refer here.

Step 2: Display places inside MoEngage campaigns

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

1. In step 2 of the campaign, type @.
   The Personalization dialog box appears.
2. In the Select attribute list, click the Radar Nearby Places API you configured in step 1.
3. Use MoEngage's Templating Language to parse the API response and include the content in your campaigns. The following code snippet, written in JINJA, shows how to iterate through the list of places and display their names in your campaigns:
   
   Jinja

   {% 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 view your campaign in real-time personalization.