Experiments by Growthhackers Destination
- Accepts Track calls.
- Refer to it as NorthStar by Growthhackers, or Experiments by GrowthHackers in the Integrations object
- This destination is in Beta
Experiments 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 Experiments by Growthhackers. For any issues with the destination, contact the Growthhackers Support team.
This document is about a destination which is in beta
This means that the Experiments by Growthhackers Destination is in active development, and some functionality may change before it becomes generally available.
- From the Segment web app, click Catalog.
- Search for “Experiments by Growthhackers” in the Catalog, select it, and choose which of your sources to connect the destination to.
- Enter the “API Key” into your Segment Settings UI which you can find following the path: “Integrations” > “Segment” > “Settings”.
If you’re not familiar with the Segment Specs, 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 Experiments 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, check this article.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property
order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Experiments by Growthhackers may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
This page was last modified: 08 Mar 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!