Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Herow


Source Info
  • The Herow is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
  • This integration is partner owned. Please reach out to the partner's support for any issues.
(warning)

This Source is supported in US data processing regions.

This Source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.

HEROW(link takes you to an external page) is a contextual platform for mobile application. Built around everyday behaviors and powered by location intelligence, its one-stop solution allows apps to maximize mobile engagement with their users.

This is an Enrichment Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by HEROW. For any issues with the source, contact the HEROW Support team.

(new)

This document is about a feature in beta

This means the feature is actively being developed, and some functionality may change before it becomes generally available.


Getting started

getting-started page anchor
  1. From your Segment UI's Sources page click on Add Source.
  2. Search for "HEROW" within the Sources Catalog and confirm by clicking Connect.
  3. Give the source a nickname and follow the set up flow to add your source. The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you'll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (for example, HEROW_Prod, HEROW_Staging, HEROW_Dev).
  4. Copy the Write key from the Segment UI and log in to your HEROW account. Navigate to Settings > Integrations > Segment Integration and paste the key to connect.

The following table lists events that HEROW sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations.

Event nameDescriptionDetails
Zone EnteredUser enters a geofence zoneA zone is a geofence monitored by our HEROW SDK. Geofence zones are created and activated in HEROW platform.
Zone ExitedUser leaves a geofence zoneA zone is a geofence monitored by our HEROW SDK. Geofence zones are created and activated in HEROW platform.
Home EnteredUser enters "Home" locationHEROW's proprietary algorithms can automatically detect a users home location after a few days.
Home ExitedUser leaves "Home" locationHEROW's proprietary algorithms can automatically detect a users home location after a few days.
Office EnteredUser enters "Office" locationHEROW's proprietary algorithms can automatically detect a users work/office location after a few days.
Office ExitedUser exits "Office" locationHEROW's proprietary algorithms can automatically detect a users work/office location after a few days.
Commute StartedUser Starts CommuteOnce the HEROW platform has defined "Home" and "Work" locations for a user, our SDK will be able to track their commute.
Commute StoppedUser ends his commuteOnce the HEROW platform has defined "Home" and "Work" locations for a user, our SDK will be able to track their commute.

The following table lists events that HEROW sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations.

(information)

Info

For each of the following events, the user ID will be the custom user ID integrated with our HEROW SDK if applicable, or the device's ID. We recommend using the Custom user ID to match with your own user database.

Zone entered (Geofence) events

zone-entered-geofence-events page anchor
Property nameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user's location at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
geofence_idstringThe ID of the geofence, provided by HEROW.
geofence_namestringThe description of the geofence.
geofence_categoriesarray of strings (comma separated)The category of the geofence.
geofence_external_idstringThe external ID of the geofence.

Zone exited (Geofence)

zone-exited-geofence page anchor
Property nameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user's location at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
geofence_idstringThe ID of the geofence, provided by HEROW.
geofence_namestringThe description of the geofence.
geofence_categoriesarray of strings (comma separated)The category of the geofence.
geofence_external_idstringThe external ID of the geofence.
durationlongThe duration between Geofence Entered and Geofence Exited events, in minutes.
Property nameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
Property NameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
Property nameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
Property nameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
Property nameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
Property nameTypeDescription
latitudefloatThe latitude of the user's location at the time of the event.
longitudefloatThe longitude of the user at the time of the event.
accuracyfloatThe accuracy of the user's location at the time of the event in meters.
Attribute nameTypeDescription
herow_home_postal_codestringThe postal code of the user's "Home" location
herow_home_countrystringThe country of the user's "Home" location
herow_work_postal_codestringThe postal code of the user's "Office" location
herow_work_countrystringThe country of the user's "Office" location

Now that your source is set up, you can connect it to destinations.

Log in to your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the relevant destination docs for troubleshooting.

If you experience any issues with how the events arrive in Segment, contact the HEROW team.