RudderStack is a great way to get your customer data into Variance. Hooking up RudderStack is easy. To start, head to the Integrations > RudderStack page in Variance.
Then you'll Add a RudderStack Connection. You can describe it in any way you want, but we suggest using the name of the RudderStack source you're going to be piping from. We recommend you use one connection per source, as you can then filter by source, but it's up to you.
On the first time you connect a RudderStack integration we ask for a little bit of additional information about how you link users with their companies in your Segment data. You can find the full details of our options on our Account Matching docs page.
If you aren't sure how you do account mapping now, you can check your RudderStack debugger (we're happy to help as well). If none of these work for you or you have any questions at all, please reach out and we're happy to hop on a Zoom and help you get set up.
Once you've added your RudderStack integration, you'll see two pieces of data:
Now head over to RudderStack, choose the Source you are piping data from and then click Add Destination.
From there you'll scroll down and choose the Variance destination and then click Next.
Then you'll name your destination. This really only matters for keeping things organized in RudderStack. You could call it ... Variance.
If you choose on the next page you can also send more Sources to Variance. It's up to you.
Finally, you'll arrive at the Connection Settings page. This is where we're going to add the Webhook URL and the Authorization Header Value that we gave you on the Integrations page. Just copy them into the fields below.
After that you'll choose whether to apply a transformation (that's up to you) and you're all set.
If you want to check the status, just create some events in the source and they should flow through RudderStack to Variance. If you have any problems let us know.
If you aren't sure what properties you're using for identifying accounts, it's easy to go into the RudderStack live events view to to find the payload of a recent `identify` call.
It should look something like this: