Skip to main content
All CollectionsChange Log
20171206 Custom Scripts and Facebook Conversion Events
20171206 Custom Scripts and Facebook Conversion Events

Custom scripts can now be added to payment pages for the store and memberships. Facebook standard events now triggered after a purchase

Cam Langsford avatar
Written by Cam Langsford
Updated over 7 years ago

We've just release the ability for custom website script to be rendered on your payment pages and we now track Facebook standard events after a successful signup and purchase.

These new features are only available when using the Stripe payment gateway.

Your own Domains on Payment Pages

Previously all payment pages where you clients enter the card details were being hosted on a Training Tilt secure domain https://secure.trainingtilt.com. This was due to the fact that we did not previously offer https on your own custom domains. Now we offer free https via ssl certificates we can host the payment pages on your own custom domains. This applies to the checkout in your online store and the payment pages for your Membership Plans.

If you are using specific urls for your membership plan buttons you can now update them by removing the https://secure.trainingtilt.com and replacing it with your own domain e.g https://yourcoachingbusiness.com or https://yourcoachingbusiness.trainingtiltapp.com

Custom Scripts on Payment Pages

Any custom scripts you currently have like FullStory, Google Analytics, Facebook Pixels etc will now be rendered on your payment pages.

To configure your custom scripts go to the "Website design" tab on the platform settings page.

Facebook Standard Events

If you have installed your Facebook pixel on your Training Tilt site we now send the standard events "AddPaymentInfo" and "Purchase" when a client purchases something from your online store or signs up to a Membership Plan.

This will allow you to track conversions directly against your Facebook Advertising campaigns.

You can find out more about Facebook conversions using Standard Events here 

The events are called under the following circumstances

Online Store

A Purchase in the store triggers the "purchase" standard event and populates the total value and the currency

fbq('track', 'Purchase', { 'value': '9.99', 'currency': 'usd', 'content_type': 'product' });

Payment Requests

A Payment Request triggers the "purchase" standard event and populates the total value and the currency

fbq('track', 'Purchase', { 'value': '279', 'currency': 'usd', 'content_type': 'product' });

Signups

Signups to a membership plan trigger either the AddPaymentInfo event or the Purchase event or both.

A client signs up to a free membership plan

fbq('track', 'Purchase', { 'value': '0', 'currency': 'usd', 'content_type': 'product', 'content_ids': ['basic-free-membership'] });

A client signs up to a paid plan for $99 a month

fbq('track', 'AddPaymentInfo', { 'value': '99', 'currency': 'usd', 'content_type': 'product', 'content_ids': ['basic-free-membership'] });
and
fbq('track', 'Purchase', { 'value': '99', 'currency': 'usd', 'content_type': 'product', 'content_ids': ['gold-membership'] });

A client signs up to a free trial with their card

fbq('track', 'AddPaymentInfo', { 'value': '0', 'currency': 'usd', 'content_type': 'product', 'content_ids': ['gold-membership'] });

Did this answer your question?