Send your event data from RudderStack to Variance.
4 minute read
The Variance customer growth platform makes your product, marketing, and sales data operational. It lets you to create, access, and manage intent-based signals across all stages of your customers’ journey.
RudderStack lets you add Variance as a destination to which you can seamlessly send your event data.
Once you have confirmed that the source platform is supported by Variance, perform the steps below:
Configure the data source in RudderStack.
From the list of destinations, select Variance.
Then, assign a name to the destination and click Next.
Select the data source and click Next. You will then see the following Connection Settings page:
Enter the Variance Webhook URL and Authorization Header Value to configure the destination.
To transform your event data before sending it to this destination, click Create New Transformation. Otherwise, click Next.
That’s it! Your Variance destination is now configured and enabled.
Identify
The identify call lets you associate a visiting user to their actions as well as record their traits.
As a best practice, make sure that the identify call is made at the start of every session or page load for logged-in users, if possible. This will ensure allir latest traits are captured.
The group call lets you associate a particular identified user with a group, such as a company, organization, or an account. It also lets you record the custom traits associated with that group, such as the name of the group, number of employees, etc.
Many destination platforms need an explicit alias call for mapping the already identified users to a new user identifier that you may want to use, to track them in the future. The alias call lets you implement this functionality.
A sample alias call is as shown:
rudderanalytics.alias("new_user_id");
Account mapping
Variance offers a few different ways of mapping your users to accounts/companies. Here’s an overview:
Group
If you already use the group call to indicate the Account, then you do not need to fill in anything. Variance will extract the Account automatically, and you’re good to go.
Identify with custom traits
Choose this option if you include some information about the Account/Company/Organization as a trait in each identify call. When you choose this option you’ll need to let Variance know the name of the trait you use.
For instance, if you pass something like {'company':{'id':1,'name':'Awesome Inc.'}} , you could add company.id as the Account ID trait and company.name as the Account Name trait.
Identify email trait domain extraction (fallback)
If you don’t use either of the methods above, Variance can extract the domain from the email trait and use that as the Account name.
How do I get the Variance Webhook URL/Authorization Header Value?
Head to the Integrations - RudderStack page in Variance and then add a RudderStack connection. For more information, check the Variance docs for RudderStack.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.