Salesforce, as a company that caters to the CRM industry, provides a platform for its clients to facilitate seamless customer experiences. This includes recording and processing lead information as captured in several forms on the client’s website, in Salesforce.
Integrating VWO with your Salesforce account can be leveraged in myriad ways. This article focuses on one of them - how to use this integration to draw the campaign information from VWO to create reporting in Salesforce and thereby gauge the impact of experimentation on the quality of the leads.
With VWO, you can easily experiment a change in your website and effectively identify the winning variation that can potentially draw more leads. Integrating VWO with Salesforce further extends this ability, wherein as you run your VWO test campaign, the campaign and the variation information for the leads on your website can be tagged to Salesforce. This enables you to further analyze this information within your Salesforce account.
Steps to Facilitate VWO <> Salesforce Integration
The process of integrating VWO with Salesforce involves the following fundamental steps:
Facilitate the tagging process: Create a hidden input field in forms
In order to avail the tagged campaign information of individual leads from VWO, you need to create a hidden input field in the sign-up forms on your website, with a default null value.
In general, if the VWO SmartCode is available on your website, VWO automatically generates a unique 32-digit hexadecimal code (called the UUID) to uniquely identify every visitor that arrives on the website.
Using the VWO UUID, you can view the campaign and variation information of individual leads. To do so, you need to perform the necessary configuration steps from your end to capture the leads’ VWO UUID in the hidden field, during form submission.
Fetch the experiment data from the tagged information and associate it with the Salesforce record: Trigger VWO REST API
Once the form is submitted by the visitor, along with the form details, the UUID is also sent to Salesforce. Upon receiving the UUID, all you need to do is to trigger VWO’s REST API, which then consumes the UUID as the input and delivers the campaign data as response.
If the visitor is exposed to more than one test campaign, the response in this case will contain the following information for each of the campaigns - Campaign ID, Campaign Name, Variation ID, and Variation Name.
The following REST API URL formats help fetch the campaign information corresponding to the UUID:
For an individual request,
For a bulk request,
!!
Here, the {{accountId}} is the VWO account ID, while {{uuid}} is the unique user ID that is sent through the hidden fields in your signup forms to your Salesforce account. You need to replace {{apiToken}} with your API token.
This REST API can be triggered at a set interval (let’s say after every 2 hours or once a day) as per the requirement.
The following examples help you understand how the data appears in real-time:
Individual Request
Let’s consider a sample account, whose Account ID is 111111. To obtain the data from that account for an individual visitor, whose UUID is D1DD64154AFA4392887A3507585F83127, the corresponding sample REST API URL may appear as follows:
Say the visitor is exposed to multiple test campaigns, then you get a response featuring all of them, as follows:
Here, the visitor is bucketed into the following test campaigns:
Test 1: Multivariate
| Campaign ID | 1 |
| Campaign Name | Campaign 1 |
| Combination ID | 1 |
| Combination Name | Control |
Test 2: A/B
| Campaign ID | 2 |
| Campaign Name | Campaign 2 |
| Variation ID | 1 |
| Variation Name | Control |
Test 3: Personalize
| Campaign ID | 3 |
| Campaign Name | Campaign 3 |
| Experience ID | 2 |
| Experience Name | Variation-1 |
Session Recordings
| Session ID | 1650271551 |
| Shared URL | https://player.vwo.me/visitor-behavior-analysis/dist/recordings?campaignId=4&sessionId=1650532364&uuid=652951979E51A24905742E15054F0306&fetch_url=r3.visualwebsiteoptimizer.com&sig=MzEwOTQxOjY1Mjk1MTk3OUU1MUEyNDkwNTc0MkUxNTA1NEYwMzA2OjE1NzYxZjcwNTlkZjZhNjk3MmIwZWZmMjJlMjg1M2E4OWI1YWRjNGMwODE4ZDgwYzRkOWI2MmEyYTc5NGYwZTE%3D&numOfPages=1&account_id=111111&analyze=1&countryCode=IN&saved=0&nD=1&token=eyJhY2NvdW50ZjMxOwYjIiLCJzY29wZX2lkIJoYXNoIjoiOWZiZTYxOGRiZDZijozMTA5NDEsImV4cGVyaW1lbnRfaWQiOjMzLCJ2aXNpdG9yUmVjb3JkaW5nU2GIyZDkwYzI4ZDI2NjUVzc2lvbklkIjoxNjUwNTMyMzY0LCJjcmVhdGVkX29uIjoxNTczMTQxODMzLCJ0eXBlIjoidmlzaXRvclJlY29yZGluZ3MiLCJ2ZXJzaW9uIjoxLCSI6dHJ1ZSwiZnJuIjpmYWxzZX0= |
Bulk Request
To obtain the data from that account for visitors with UUIDs - D1DD64154AFA4392887A3507585F83127 and FA16F2F293FF4BA7EA434269458EE545, the corresponding sample REST API URL may appear as follows:
The response for the corresponding request will feature the data like this:
Here, the data is presented for the visitors under their respective UUIDs.
After receiving the campaign information, involve your development team to parse through the response to assign the campaign and variation information for the lead to the campaign/experiment level record in your Salesforce account, experiment-wise.
The following is how an experiment-level record will be displayed in Salesforce:
The VWO UUID of the respective lead will be stored in the lead-level record in Salesforce:
This is one way of setting up to leverage the integration. The possibilities of customization are aplenty and you can thus create your own setup tailoring to your requirements.