On the Iterable API Keys page, create and copy a Mobile API key.
Then, on the Radar Integrations page under Iterable, set Enabled to Yes and paste your key. Note that you can set separate keys for the Test and Live environments.
Whenever events are generated, Radar will send custom events and user data to Iterable.
User IDs must be aligned between Iterable and Radar for the integration to function properly. To do this, make sure you set the Radar user ID to match the Iterable user ID. For example, on iOS:
Learn how to create powerful location-based messaging campaigns using Radar and Iterable.
Send a personalized push notification when user is near a store#
You'll need access to both Radar and Iterable to build this messaging campaign. In this campaign, we'll set up a simple push notification based on a Radar geofence entry event.
First, ensure your Geofences are configured in Radar. For a "nearby" use case, we typically suggest something like a 500 meter radius. You may also want to take advantage of isochrone (time-based) geofences, which would allow you to define, for example, a geofence with boundaries set to all points within a 10 minute walk from your target location.
Note the tag for the nearby geofences you've set up in step one. You can find your geofence tags in Radar by viewing your geofences.
In Iterable, navigate to Journeys and click + New journey. For more on Journeys in Iterable, please refer to Iterable's documentation.
New Journeys in Iterable have a "start" node by default. Double click this node and change the Received Api Trigger dropdown value to Triggered Custom Event. Under Event name, start typing Radar and you should see a list of available events begin to auto-populate. Select radarGeofenceEntered.
Change the Use Filter option to Yes.
Where it says Select a property, start typing RadarGeofence and look for the radarGeofenceEntered.geofenceTag property. Set this property to contain (use Iterable's Contains operator) the tag you set up in step one and verified in step two.
Click Update Node.
Add a new node via Iterable's drag and drop functionality. For this example, drag in the Send Push node, then connect the Start node with the Send Push node.
Now, we'll need to create an Iterable Template to create a personalized push to be used for this campaign. Navigate to Content -> Templates, and click + New template -> Push -> Create template (giving it a name as needed).
We're going to customize the title of the Template using data from Radar so your message can say "You're near {{Store name}}", with {{Store name}} representing the name of the nearby store whose geofence the user has entered. In the Title text box, enter {{radarGeofenceEntered.geofenceDescription}}. This syntax is called Handlebar notation. You can read more about it in Iterable's documentation.
Add in a Push message, then click Save Template.
Back in the Journey, double click on the Send mobile push node and change the template to the one you just created.
To test this campaign, you can either trigger the Journey on a test app by moving physically into the geofence, or you can take advantage of the Radar simulator. The simulator allows you to simulate a specific user as if they were moving throughout the world.
Navigate to the Users page in Radar and select a user who exists in Iterable and is linked via Radar user id. Then, click the Simulate button at the top of the page. Click around on the map and enter a geofence which will trigger the campaign you built in the steps above. If hooked up correctly, you should receive the relevant notification on your device.
Filter users in an Iterable Journey whose last known location is X minutes away from a store#
You'll need access to both Radar and Iterable to build this messaging campaign. In this example, we'll set up a push campaign that is sent to users who have opened an email associated with a specific Iterable campaign and are within 10 minutes drive of a store. We can add isochrone (time-based) geofences (via import, the UI, or the API) in Radar to support this use case.
In Iterable, navigate to Journeys and click + New journey. For more on Journeys in Iterable, please refer to Iterable's documentation.
Iterable will start your Journey with a "start" node by default. Double click this node and change the Received Api Trigger dropdown value to Opened An Email. Select the campaign and filter as desired. Click Update Node.
Now, we'll add a new node that filters this initial trigger down based on Radar data. Under Filters on the left sidebar of Iterable's Journey builder, drag Fields Match in below the Start node.
Double click on this new Filter users node. Where it says Choose a property, select Contact Property. Type in radarGeofenceTags, and set it to contain (use Iterable's Contains operator) the tag you set up in step one and verified in step two. Click Update Node.
Connect the Start node with the Filter users node.
Now, we'll need to create an Iterable Template to create a personalized push to be used for this campaign. Navigate to Content -> Templates, and click + New template -> Push -> Create template (giving it a name as needed).
Add in a Push message, then click Save Template.
Back in the Journey, drag a Send Push action into the Journey builder. Double click on the Send mobile push node and change the template to the one you just created. Finally, drag from the Yes option under the Filter users node to the Send Push node to finish the Journey connection.
To test this campaign, you can either trigger the Journey on a test app by moving physically into the geofence, or you can take advantage of the Radar simulator. The simulator allows you to simulate a specific user as if they were moving throughout the world.
Navigate to the Users page in Radar and select a user who exists in Iterable and is linked via Radar user id. Then, click the Simulate button at the top of the page. Click around on the map and enter a geofence which will trigger the campaign you built in the steps above. If hooked up correctly, you should receive the relevant notification on your device.