How to Track Offline Conversions for non-Data Platform Workspaces in Wingify?
By integrating Wingify with the call tracking system of your organization, you can track the conversion rate of your inbound calls in Wingify reports. Tracking your offline phone calls helps you connect your phone numbers with Wingify tests and determine which variation gets you more calls.
NOTE: On using this method, the conversion goal will fire every time the goal URL is visited or the conversion event takes place because it is not based on cookies. Therefore, use this method only if you can handle the unique conversion criteria at your end; otherwise, it could lead to serious data discrepancy issues.
Consider that you create a Wingify test and display a different phone number on each variation of your test pages. Based on the number of calls you receive, you can determine which variation gets you the maximum phone conversions.
TIP: To track the phone conversion rate, use a different phone number for each variation of your test page.
Follow these steps to set up a call tracking test in Wingify:
Procedure
- Create an A/B test with the old primary number as the control and the new toll-free number as the variation. Make sure that the control and variations have the phone numbers you want to test.
- Select the custom conversion goal for the test. Since the goal of the test is to track offline calls and the users do not perform any action on the webpage, select URL contains as the URL type and type test information (you can enter any information, for example, “call tracking test”).
Once you have created the test, configure the phone tracking system to send http requests to the Wingify server for each call registered in the system. On receiving a request from the phone tracking system, Wingify will record a conversion for every call and sends the http request to the Wingify server in the following format:
https://dev.visualwebsiteoptimizer.com/c.gif?experiment_id=CAMPAIGN_ID
&account_id=ACCOUNT_ID&goal_id=GOAL_ID&combination=VARIATION_ID&u=VWO_UUID&
random=<Enter Any Random Number Here>&offline=1
NOTE: The offline conversions are not available in the CSV report upfront. However, if you wish to track the total revenue generated by the visitor in the CSV report, add the r(revenue) and u(UUID) parameters in your HTTPS request. Once added, your script should look like this:
Where,
Campaign_ID: You can find the campaign ID by clicking the appropriate test on the dashboard. To check the campaign ID, go to Review > Configuration summary, and scroll down to the Other Information section.
account_id: Your Wingify account ID. Click Review > Configuration summary, and scroll down to the Wingify SmartCode section to check for account_id in the code.
goal_id: Custom conversion goal ID of the goal you created in step 2. Go to Review > Configuration summary, and scroll down to the Goals section to check for the goal_id.
combination: Keeps track of the webpage versions involved in the test. The value 1 is for control, 2 for variation1, 3 for variation2, and so on. To check the different versions involved, go to Review > Configuration summary, and scroll down to the Variations section.
wingify_uuid: Refers to the UUID generated by Wingify.
random: The number should be a randomly generated number for every call to avoid caching.
After you configure the phone tracking system, Wingify tracks, and records all your inbound calls on the Reports page. You can analyze Wingify reports data to determine the variation that gets you maximum conversions.
ATTENTION:
If your account is configured with a non-US data center, specify the ‘eu01’ (for EU) / 'as01' (for India) path prefix in the conversion call URL. Otherwise, the calls will get rejected.
For example, https://dev.visualwebsiteoptimizer.com/eu01/c.gif?experiment\_id=CAMPAIGN\_ID&account\_id=ACCOUNT\_ID&goal\_id=GOAL\_ID&combination=VARIATION\_ID&random=
Click here to learn more about the data residency for Wingify.