NorthStar by Growthhackers Destination
NorthStar by Growthhackers provides a project management tool for growth teams, allowing companies to create and prioritize ideas, run experiments and gather data to learn upon!
This destination is maintained by NorthStar by Growthhackers. For any issues with the destination, please reach out to their team.
NOTE: The NorthStar by Growthhackers Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on June 26, 2019. If you are interested in joining their beta program or have any feedback to help improve the NorthStar by Growthhackers Destination and its documentation, please let their team know!
The first step is to make sure NorthStar by Growthhackers supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “NorthStar by Growthhackers” within the Destinations Catalog and confirm the Source you’d like to connect to.
- Drop in the “API Key” into your Segment Settings UI which you can find following the path: “Integrations” > “Segment” > “Settings”.
If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:
analytics.track('Clicked Login Button')
Track calls will be sent to NorthStar by Growthhackers as a
Once the integration is completed, your events will always be available in your cards, all you have to do is select the ones that best help you validate your hypothesis. For further information and visual guidance of how it’s going to look like, please check this article.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Segment lets you change these destination settings from your Segment dashboard without having to touch any code.
Integrations > Segment > Settings
Questions? Problems? Need more info? Contact us, and we can help!