Experiments by Growthhackers Destination
Experiments by GrowthHackers quick info
Experiments by GrowthHackers accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.
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.
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.
- 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.
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, 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
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: 20 Oct 2020
Questions? Problems? Need more info? Contact us, and we can help!