Experiments by Growthhackers Destination

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 their team.

NOTE: The Experiments 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 Experiments by Growthhackers Destination and its documentation, let their team know!

Getting Started

Before you start, make sure Experiments by GrowthHackers supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Experiments by Growthhackers” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in 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 track event.

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 Segment Personas to this destination as a user property. To learn more about Personas, contact us for 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 indicade membership. For example, when a user first completes an order in the last 30 days, Personas 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), Personas sets that value to false.

When you first create an audience, Personas 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.


Segment lets you change these destination settings from the Segment app without having to touch any code.


Integrations > Segment > Settings

Adding Experiments by GrowthHackers to the integrations object

To add Experiments by GrowthHackers to the integrations JSON object (for example, to filter data from a specific source), use one of the following valid names for this integration:

  • NorthStar by Growthhackers

  • Experiments by GrowthHackers

This page was last modified: 12 Jun 2020

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account