This article explains how to use the Integrations interface in the Manager.
Many of our customers have needed to integrate Evolv with other services, tools, or applications.
These include:
- Analytics integrations
- Helper functions for variants
- Updates to context to allow for matching audience criteria
- Native mobile
- Server-side APIs
‘Integrations Interface’ is a helpful tools for making these kinds of integrations much easier. Rather than a bunch of custom code, you can deploy integrations from right inside the Evolv Manager using this standardized framework. It allows for creating a custom integration - hooked up to an NPM or Github project. Then the ability to configure and launch it per environment.
The step by steps below should get you going, but if you need more detail, here is a comprehensive video walkthrough.
The three essential steps are:
- Define a new integration at the account level.
- Create a connector for your new integration.
- Add the integration to the appropriate environment.
1. Define a new integration at the account level
First, you will define a new integration at the account level, by going to the Integrations view and selecting New Integration.
Next, give your new integration a name and a description, and input any JSON you need for configuration.
2. Create a connector for your new integration
Next, create a connector for that Integration. This is where you specify the location where the code is located that will power the integration. For example on Github, Gist, or NPM. We use standard NPM import mechanisms, so have a look at that documentation for what to put in the fields.
Ensure the index.js is exporting a module.
Note that you would use a different connector for a mobile experiment than a web experiment, even if wiring them both up to the same analytics platform.
Here’s what it looks like for Github:
And here's NPM (Gist is also supported):
3. Add the integration to the appropriate environment
Finally, you will need to add your integration to a specific Environment. To do this, go to the Environments view and click “add integration”.
Enter any JSON needed for Environment-level configuration and you are good to go. Note that we keep track of changes to existing integrations and you will be prompted here to update to the latest if applicable. Note that Environment-level JSON will override the account-level JSON.