|
| 1 | +--- |
| 2 | +rewrite: true |
| 3 | +title: Variance Destination |
| 4 | +--- |
| 5 | + |
| 6 | +[Variance](https://variance.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) hooks into your customer data and makes it easy to access growth signals across product, marketing, and sales. The platform provides your growth team with clear, intent-based signals, from all stages of a customer's journey. |
| 7 | + |
| 8 | +This destination is maintained by Variance. For any issues with the destination, [contact the Variance Support team ](mailto:[email protected]). |
| 9 | + |
| 10 | +## Getting Started |
| 11 | + |
| 12 | + |
| 13 | +1. From the Destinations catalog page in the Segment App, click **Add Destination**. |
| 14 | +2. Search for "Variance" in the Destinations Catalog, and select the Variance destination. |
| 15 | +3. Choose which Source should send data to the Variance destination. |
| 16 | +4. Go to the [Variance Integrations page](http://app.variance.com/integrations){:target="_blank"} (you'll see it in the main nav under your company name). |
| 17 | +5. Click **Add Connection**. |
| 18 | +6. Give your connection a name. If you use a descriptive name, you can use it as an event filter in Variance. |
| 19 | +7. Choose a method for account matching. You can read more about these methods in the [Account Mapping](#account-mapping) section. |
| 20 | +8. Find and copy the "Secret" and "Webhook URL" fields associated with this project. |
| 21 | +9. Back in the Segment App, enter these as the **API Key** and **Webhook URL** fields in the Variance Destination settings. |
| 22 | + |
| 23 | +## Supported methods |
| 24 | + |
| 25 | +Variance supports the following methods of the [Segment Spec](/docs/connections/spec). |
| 26 | + |
| 27 | +### Page |
| 28 | + |
| 29 | +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: |
| 30 | + |
| 31 | +```js |
| 32 | +analytics.page() |
| 33 | +``` |
| 34 | + |
| 35 | +Segment sends Page calls to Variance as a `Page` Event Type. |
| 36 | + |
| 37 | + |
| 38 | +### Screen |
| 39 | + |
| 40 | +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: |
| 41 | + |
| 42 | +```obj-c |
| 43 | +[[SEGAnalytics sharedAnalytics] screen:@"Home"]; |
| 44 | +``` |
| 45 | +
|
| 46 | +Segment sends Screen calls to Variance as a `Screen` Event Type. |
| 47 | +
|
| 48 | +
|
| 49 | +### Identify |
| 50 | +
|
| 51 | +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: |
| 52 | +
|
| 53 | +```js |
| 54 | +analytics.identify('userId123', { |
| 55 | + |
| 56 | +}); |
| 57 | +``` |
| 58 | + |
| 59 | +Segment sends Identify calls to Variance as a `Contact`. |
| 60 | + |
| 61 | + |
| 62 | +### Track |
| 63 | + |
| 64 | +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: |
| 65 | + |
| 66 | +```js |
| 67 | +analytics.track('Login Button Clicked') |
| 68 | +``` |
| 69 | + |
| 70 | +Segment sends Track calls to Variance as an `Action` Event Type. |
| 71 | + |
| 72 | + |
| 73 | +### Group |
| 74 | + |
| 75 | +Send [Group](/docs/connections/spec/group) to Variance. For example: |
| 76 | + |
| 77 | +```js |
| 78 | +analytics.group("groupId123", { |
| 79 | + name: "Initech", |
| 80 | + industry: "Technology", |
| 81 | + employees: 329, |
| 82 | + plan: "enterprise" |
| 83 | +}); |
| 84 | +``` |
| 85 | + |
| 86 | +Segment sends Group calls to Variance as an `Account` if you've chosen the "Group" Account Mapping method during setup. |
| 87 | + |
| 88 | +## Account Mapping |
| 89 | + |
| 90 | +Variance offers several ways to map your users to accounts or companies, including the following. |
| 91 | + |
| 92 | + - **Group**: If you already use the Group call to indicate the Account, then you don’t need to change anything as Segment automatically extracts the Account name. |
| 93 | + - **Identify with custom traits** (for example `company.id` and `company.name`): Choose this option if you include some information about the Account, Company, or Organization as a trait in each Identify call. When you choose this option, add the name of the trait you use. For example, if you configure the call with the data `{'company':{'id':1,'name':'Awesome Inc.'}}`, add `company.id` as the Account ID trait and `company.name` as the Account Name trait. |
| 94 | + - **Identify email trait domain extraction** (Fallback option): If you don't use the methods above, Segment extracts the domain name from the `email` trait, and uses that value as the Account name. |
| 95 | + |
| 96 | +> info "" |
| 97 | +> If none of these methods work for your configuration, [contact Variance support](mailto:[email protected]) to discuss alternatives. |
0 commit comments