This article covers the following:
- About Offline Conversions
- Track Offline Conversions for the Data360 Model in Wingify
- Things to Consider While Tracking Offline Conversions
- Register a Visitor
- Register a Conversion
About Offline Conversions
Wingify’s capabilities to measure the conversion parameters of your website is not only limited to the transaction occurring online. It can also provide reports for your offline conversions, provided you supply the necessary inputs manually. It’s as easy as setting up a campaign to track online conversions.
Let’s assume that you’re a B2B software company that offers a free trial of a product on your website. Potential customers can sign up for the trial by filling out a form on your website and providing their contact information. However, many of these trial sign-ups eventually convert into paying customers through offline interactions, such as sales calls, demos, and negotiations with the sales team.
Now, you want to accurately measure the effectiveness of your website's free trial sign-up process in driving offline conversions and sales. You can use Wingify's offline conversion tracking to connect online actions with offline outcomes. By integrating their CRM system with Wingify, they can track when trial users from their website become paying customers through offline interactions.
With Wingify's offline conversion tracking, the company can attribute revenue and business outcomes to specific website interactions. This allows them to optimize their website's conversion funnel based on not just immediate online actions, but also the long-term impact on offline conversions. The insights gained from offline conversion data help the company make informed decisions about their marketing strategies and website improvements.
In this scenario, Wingify's offline conversion tracking empowers the B2B software company to understand the full customer journey and make data-driven decisions to enhance their online and offline interactions.
Sometimes, you may want to reach out to your website visitors and engage in a conversation to derive insights or explain to them about your products or services personally with a specific aim in mind. But since this is a strenuous task, you need to identify the potential customers before approaching them. You can do this by running an A/B test campaign in Wingify, where you can target a segment of visitors.
For example, you can put a banner on a webpage indicating an offer or service for a segment of visitors which can be availed by dialling your customer service. As your visitors reach out to your customer service, you can record the outcome of each of the calls and manually send the conversion information to Wingify through a payload. This way, the conversions that happen offline can be tracked in your Wingify campaign report.
Note: Offline conversions can be of various sorts, where the visitors would be converted through an offline mode or on an application, which may be different from the one where the visitor was recorded.
Track Offline Conversions for the Data360 Model in Wingify
If your account is enabled with Data360, you can track the offline conversions for your Wingify campaigns by performing the following:
Create an Offline Conversion Campaign in Wingify
In order to track the offline conversions, you first need to create an A/B test campaign, define your variations and set up a metric correspondingly.
To do these, perform the following steps:
- Refer to How to Create a Campaign in Wingify? to set up your campaign URLs and create variations.
- Once you arrive on the METRICS page, click on Create a new metric.
- In the Create a new metric popup that appears, enter the following details:
| Field | Input |
|---|---|
| Metric Name | Enter the name of the metric |
| Definition |
This allows you to customize the way the conversions are to be accounted for in your reports. This dropdown features the following options: If an event is triggered - Each visitor, upon triggering the event, can be counted as converted only once, irrespective of the number of times the event is triggered by the same visitor. E.g. You can use this option to track if a visitor has clicked on a link. Value of an event property - Calculates the conversion of the event based on the property that you define. This can be used for those events that involve properties with numerical values, such as tracking revenue, and time spent on a page. To apply this, you need to define the event property and its corresponding value type (Sum, Average, Max, Min, First value, and Last value). Note: In case of tracking revenue, select the Format this metric as currency checkbox. This populates the values in the currency (as configured in your account-level campaign settings. Read more) in your reports. Number of times an event is triggered - The event is counted as converted, every single time a visitor triggers it. This way it also populates multiple conversions made by the same visitor. E.g. You can use this option to track the total clicks on a CTA button, such as Add to Cart. |
| for event | Select an event to track from the Custom Events (MY EVENTS) that you have created. |
- Click Create and click Next.
- On the OTHERS page, set up your campaign settings and click Create.
- Click the Start Now button to run your campaign.
Now, you need to report the conversions manually to Wingify by triggering the offline conversion request. But before doing that, it is important first to register the visitor in Wingify. You will need to send the information about the visitor to Wingify by triggering the variationShown event.
Things to Consider While Tracking Offline Conversions
- Since Data360 in Wingify is an event-driven model, it requires an event to register the conversion information of the visitors. You can create and manage your events in Data360 > Events.
- Before sending the offline conversion information, you need to register a ‘variationShown’ event.
- The ‘variationShown’ event must be triggered with a UUID and a ‘session ID’.
- Only one variationShown event will be accepted per UUID.
- For an event, the value of the time property should be greater than the ‘session ID’. Failing this will result in the conversion not getting counted.
Register a Visitor
As a first step to send the conversion information to Wingify, you need to register the visitors by triggering the following code to https://edge.wingify.net/events/t?en=vwo_variationShown&a=<accountId>:
{
"d": {
"visId": <$uuid>,
"event": {
"props": {
"id": <$campaignId>,
"variation": <$variationId>,
"isFirst": 1
},
"name": "vwo_variationShown",
"time": <Epoch Timestamp in ms>
},
"sessionId": <Epoch Timestamp in seconds>
}
}
Here, you need to replace the parameters in the code as follows:
| <accountId> | Your Wingify account ID |
|---|---|
| <$uuid> | The UUID of the visitor |
| <$campaignId> | The ID of the campaign, which the visitor was part of |
| <$variationId> | The ID of the variation, which was shown to the visitor |
| <Epoch Timestamp in ms> | The epoch timestamp (in milliseconds), in which the event was triggered |
| <Epoch Timestamp in seconds> | The epoch timestamp (in seconds), in which the event was triggered |
Note: You can skip this step, if the visitors are already being tracked by Wingify.
For example, let’s say your account ID = 012345. To register a visitor with UUID = ABCDEF0123456789ABCDEF0123456789, who was part of campaign 123, and variation 1, you need to trigger the following code to
https://edge.wingify.net/events/t?en=vwo_variationShown&a=012345:
{
"d": {
"visId": "ABCDEF0123456789ABCDEF0123456789",
"event": {
"props": {
"id": 123,
"variation": "1",
"isFirst": 1,
},
"name": "vwo_variationShown",
"time": 1655985233608
},
"sessionId": 1655985233
}
}
Register a Conversion
Post registering a visitor, you can register the corresponding conversion information by triggering the following offline conversion request to https://edge.wingify.net/events/t?en=<eventName>&a=<accountId>:
{
"d": {
"visId": <$uuid>,
"event": {
"props": {
"<propertyApiName>": "<$propertyvalue>",
"isCustomEvent": true,
"name": <$eventName>,
},
"name": <$eventName>,
"time": <Epoch Timestamp in ms>
},
"sessionId": <Epoch Timestamp in seconds>
}
}
Here, you need to replace the parameters in the code as follows:
| <eventName> | Name of the event |
|---|---|
| <accountId> | Your Wingify account ID |
| <$uuid> | The UUID of the visitor |
| <propertyApiName> | The API name of the event property. NOTE: You can add multiple properties in the same request. |
| <$propertyvalue> | The value of the event property |
| <$campaignId> | The ID of the campaign, which the visitor was part of |
| <Epoch Timestamp in ms> | The epoch timestamp (in milliseconds), in which the conversion occurred |
| <Epoch Timestamp in seconds> | The epoch timestamp (in seconds) of the session, in which the conversion occurred |
For example, let’s say your account ID = 012345. You need to register a visitor with UUID = DA4A69FF770F16670D09342F34977E323, who was part of campaign 74 with the Metric ID = 1 for tracking an event named “revenueTracking”. The event has a property called “revenueAmount”, which carries a value of 20. Now, you can trigger the following code to
https://edge.wingify.net/events/t?en=revenueTracking&a=012345:
{
"d": {
"visId": "DA4A69FF770F16670D09342F34977E323",
"event": {
"props": {
"revenueAmount": "20",
"isCustomEvent": true,
"name": "addRevenue",
},
"name": "revenueTracking",
"time": 1658308157000
},
"sessionId": 1658308157
}
}
Need more help?
For further assistance or more information, contact Wingify Support.