What you should have completed before starting

In order to test the HEROW SDK, you should have gone through the integration within your app. Check the integration article for more information.

What you will learn in this article

The objective of this article is to explain the different steps required to test the basic HEROW features and validate your integration.

Create your test location and campaigns on HEROW

Step 1: Log on HEROW

Go on https://my.herow.io/#/ and connect to your HEROW account.

Step 2: Select your app’s environment 

Once logged in, make sure you select your app’s environment (green) and not “Discover”, “App Demo” or test environment *if any* (red) to continue the testing procedure.

Step 3: Go to manage to create your test Location

Create a 200m radius location (blue) a couple of blocks away (red: at least 200m away) from your office (green).

Step 4: Create your test Campaign

  • Create a "Notification Campaign" (green) for “all users
  • Pick “Real-Life Moments” and link it to your “test location
  • Keep the basic set up (upon entry, no time limit, no condition) and create your notification (title and description only).- (blue)
  • Launch the campaign - (purple)

Note:
HEROW location cache’s method is updated every 15 minutes on default settings so your “test campaign” will be available at your “test location” 15 minutes after you launched it.

Install your app’s build and test the heatmap and notification

In order to conduct the test in the best conditions, we advise that you carry at least 3 devices of each OS. Make sure your OS versions are 9+ for Android and 12+ for iOS to get representative outcomes. 

To maximize deliverability rates, make sure all devices are charged above 50% (battery savings features could turn on if the condition is not met) and that WIFI is turned on.

Last, Android devices have different behavior in relation to geolocation. Check out: https://dontkillmyapp.com/ to make sure none of your testing devices belong to the “dumbphone” list.

Step 1: Install your app’s build and validate the different permissions

Once past the 15 minutes, install your app’s build on your testing devices. Validate the 3 permissions:

  • GDPR
  • Location
  • Notification

Step 2: Walk towards the test location (location testing)

In order for the HEROW SDK to start making position statements, your device should be moving (we don’t do it if the device is still, to preserve the user’s battery).

It is also important for step 3 that you walk (and not drive or cycle, we saw you coming) to the test location to maximize deliverability rates.

Step 3: Go to the center of the zone

To maximize the chances of reception, one should get as close as possible to the center of the zone. Indeed, staying on the outring might lead the SDK to believe you’re still outside of the zone. 

HEROW’s location features are powerful but might sometimes miss the target due to external factors; low connectivity, old device, restraining device manufacturer.

You should by now have received your test notifications


*Step 3: If it does not work, don’t panic*

Geofencing technology isn’t a 100% hit or miss technology as it relies on countless different factors. Notification rate might not be 100% at first. Do not hesitate to redo the tests one or two times to get a representative reception rate. 

Step 4: Continue your day and come by say hello tomorrow

Notifications and location statements are made in real-time but the display (permission rates, heatmap, location, and notification campaign analytics) will take around 12 hours to be fully available on the platform.


Day +1: enjoy your morning coffee and get all your information available on the HEROW platform, from heatmap to “test location” and “test campaign” analytics!

Did this answer your question?