Tracking conversions
When a customer registers at your gym or makes a purchases you may want to pass information about the conversion to a 3rd party provider. Such information is typically used in ads systems so you can measure the effectiveness of your spend and increase performance. This article runs over how to set that up.
Entering code
Pixels are the most popular way of measuring conversions and major suppliers provide simple code you can drop into your website and 3rd party providers (such as WodBoard) to measure conversions. For maximum results we recommend you add the code to both your website and WodBoard.
Head to Settings -> Business Details and then click into the relevant location. On that page you'll notice a link to add conversion code. This is where you save your pixel code, which is normally done by a simple copy from your supplier and paste into WodBoard.
Once saved the pixel code will fire each time a conversion event occurs in WodBoard (see the table in the section below for a list of cases). Events could fire multiple times for a given user if they, for example, register as a lead and then buy a product at a later point. You should choose the option in your ads provider that allows for multiple events per user.
Note many browsers are adding privacy options that mean pixel code may be blocked. Whilst it will work for some users it won't for others. You should therefore take conversion stats from pixels as a guide for how well things are working rather than a definitive number. The metrics within your WodBoard dashboard should always be the definitive guide.
Variables
To improve conversion effectiveness you can often pass additional information to tracking pixels such as purchase price and unique order references (the later stops duplicate events). Our Tracking javascript variable provides the information you need to pass this along.
On conversion pages a Tracking Javascript variable will be present that contains a type and id attribute. The id is a unique reference for the event and the type will be one of the following:
| Event | Description | When it occurs |
| Subscribe | A customer signups for a membership | For all new customers. For existing customer if they've not been active for 30 days |
| Purchase | a) A customer buys a class packb) A customer pays for a one off item (such as a PT session)c) A customer claims a free item (such as a trial) | a) for all new customers. For existing customer if they've not been active for 30 daysb) if the customer is newc) if the customer is new |
| Register | A customer registers with your business but doesn't buy anything | For all new customers |
| Lead | A lead registers interest with your business (CRM only) | For all leads |
If the event is a Subscribe or Purchase type then some extra attributes are also available in the Tracking variable:
| Attribute | Description |
| productId | A unique reference for the product. Will be the same on subsequent purchases of the product |
| name | The product name |
| amount | The amount of the purchase as a string - eg "125.00" |
| currency | The currency of the purchase - eg "GBP" |
Attributes can be accessed by calling the attribute name on the Tracking variable - for example Tracking.amount
The variables can be used to pass extra information about the event to the 3rd party providers. For details of how to do that see your 3rd party provider documentation.
We send Facebook the Subscribe , Purchase , Lead and CompleteRegistration events under the situations outlined in the table above.
You should include the pixel on your website and fire the ViewContent event there.
iOS 14.5 and later Apple has limited the events that Facebook can track in apps as part of a privacy move. When using apps on iOS a user is presented with a dialog asking if they want to allow tracking across websites (which needless to say they'll nearly always refuse). If they refuse then only limited events from facebook are tracked. As such we recommend you verify your domain in Facebook and prioritise the ViewContent event. This allows for maximum event recording in iOS14.5