-
Notifications
You must be signed in to change notification settings - Fork 395
Add herow source #552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Add herow source #552
Changes from 8 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
74822d8
Add herow source
758844a
update markup
79478fa
update title
423c461
update catalog for herow
ac6c7a7
update doc
c36a642
use master dest file
8b146a1
use master dest file
e51d7ea
update doc date
a002614
Update src/connections/sources/catalog/cloud-apps/herow/index.md
sanscontext c1737ee
cut down on marketing speak
ab1f144
Merge branch 'niallb/add_herow_source' of ssh://github.com/segmentio/…
d0bcf0b
cut down on marketing speak
89454f7
Merge branch 'master' into niallb/add_herow_source
sanscontext 441981b
Merge branch 'master' into niallb/add_herow_source
niallzato File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
156 changes: 156 additions & 0 deletions
156
src/connections/sources/catalog/cloud-apps/herow/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,156 @@ | ||
| --- | ||
| title: Herow | ||
| source-type: event | ||
| beta: true | ||
| --- | ||
|
|
||
| [HEROW](https://www.herow.io) 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. | ||
|
|
||
| With HEROW simple, straightforward SaaS platform, mobile marketers and developers can: | ||
|
|
||
| + Better understand how, when and where their app is being used | ||
| + Create user segments based on real-world behaviors and moments | ||
| + Significantly improve engagement through contextual notifications and in-app actions | ||
|
|
||
| Its SaaS platform uses hyper-precise location technology and machine-learning algorithms to provide mobile applications with true user context - a combination of location, behavior, and surroundings. | ||
|
|
||
| The technology benefits all app categories - gaming, social, dating, mobility, music, news, shopping, etc. - and allows HEROW's clients to create better mobile experiences and to build long-lasting relationships with their users. | ||
|
|
||
| This is an [Enrichment Source](https://segment.com/docs/sources/#event-cloud-sources) 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, please [reach out to their team](mailto:[email protected]). | ||
sanscontext marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| _**NOTE:** The HEROW Source is currently in beta, which means that they are still actively developing the source. This doc was last updated on January 29, 2020. If you are interested in joining their beta program or have any feedback to help improve the HEROW Source and its documentation, please [let their team know](mailto:[email protected])!_ | ||
|
|
||
|
|
||
| ## Getting Started | ||
|
|
||
| 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 setup flow to "Add 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 (eg. 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. | ||
|
|
||
| ## Events | ||
|
|
||
| Below is a table of 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 Name | Description | Details| | ||
| | -------- | -------- | -------- | | ||
| | Text | Text | Text | | ||
| |Zone Entered| User enters a geofence zone| A zone is a geofence monitored by our HEROW SDK. Geofence zones are created and activated in HEROW platform.| | ||
| |Zone Exited|User leaves a geofence zone|A zone is a geofence monitored by our HEROW SDK. Geofence zones are created and activated in HEROW platform.| | ||
| |Home Entered|User enters "Home" location|HEROW's proprietary algorithms can automatically detect a users home location after a few days.| | ||
| |Home Exited|User leaves "Home" location|HEROW's proprietary algorithms can automatically detect a users home location after a few days.| | ||
| |Office Entered|User enters "Office" location|HEROW's proprietary algorithms can automatically detect a users work/office location after a few days.| | ||
| |Office Exited|User exits "Office" location|HEROW's proprietary algorithms can automatically detect a users work/office location after a few days.| | ||
| |Commute Started (Coming soon)|User Starts Commute|Once the HEROW platform has defined "Home" and "Work" locations for a user, our SDK will be able to track their commute.| | ||
| |Commute Stopped (Coming soon)|User ends his commute|Once the HEROW platform has defined "Home" and "Work" locations for a user, our SDK will be able to track their commute.| | ||
|
|
||
| ## Event Properties | ||
|
|
||
| Below is a table of events that HEROW sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations. | ||
|
|
||
| **Important note on the user id:** 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 | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user’s location at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
| |geofence_id|string|The ID of the geofence, provided by HEROW.| | ||
| |geofence_name|string|The description of the geofence.| | ||
| |geofence_categories|array of strings (comma separated)| The category of the geofence.| | ||
| |geofence_external_id|string|The external ID of the geofence.| | ||
|
|
||
|
|
||
|
|
||
|
|
||
| ### Zone Exited (Geofence) | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user’s location at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
| |geofence_id|string|The ID of the geofence, provided by HEROW.| | ||
| |geofence_name|string|The description of the geofence.| | ||
| |geofence_categories|array of strings (comma separated)|The category of the geofence.| | ||
| |geofence_external_id|string|The external ID of the geofence.| | ||
| |duration|long|The duration between Geofence Entered and Geofence Exited events, in minutes.| | ||
|
|
||
|
|
||
| ### Home Entered | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
|
|
||
|
|
||
|
|
||
|
|
||
| ### Home Exited | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
|
|
||
|
|
||
| ### Office Entered | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
|
|
||
| ### Office Exited | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
|
|
||
|
|
||
| ### Commute Started (Coming soon) | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
|
|
||
| ### Commute Ended (Coming soon) | ||
|
|
||
| |Property Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |latitude|float|The latitude of the user’s location at the time of the event.| | ||
| |longitude|float|The longitude of the user at the time of the event.| | ||
| |accuracy|float|The accuracy of the user’s location at the time of the event in meters.| | ||
|
|
||
| ### User Traits | ||
|
|
||
| |Attribute Name|Type|Description| | ||
| | -------- | -------- | -------- | | ||
| |herow_home_postal_code|string|The postal code of the user's "Home" location| | ||
| |herow_home_country|string|The country of the user's "Home" location| | ||
| |herow_work_postal_code|string|The postal code of the user's "Office" location| | ||
| |herow_work_country|string|The country of the user's "Office" location| | ||
|
|
||
|
|
||
|
|
||
| ## Adding Destinations | ||
|
|
||
| Now that your Source is set up, you can connect it with Destinations. | ||
|
|
||
| Log into 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 Destination docs for troubleshooting. | ||
|
|
||
| If there are any issues with how the events are arriving to Segment, please [contact the HEROW team](mailto:[email protected]). | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lines 9 through 17 are marketing content and don't belong in the docs. 🤔 Lets please remove these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the marketing content, we good to approve and merge 🤞