Customising the Unsubscription Page 📃

You can fully design and manage the landing page directly within your Fast Track environment:
  1. Settings → Manage Unsubscribe Pages → Add New Version

Shortlinking for SMS 📱

Shortlinking helps conserve character space in SMS messages and enables click tracking for better performance insights.

Setting this up 🚀

To set this up, your brand will need to provide the domains to be used—these can be subdomains of your existing domain. For example:
  1. unsubscribe.brand.com → for the unsubscription page
  2. l.brand.com → for SMS shortlinks
These domains must be configured to use a Content Delivery Network (CDN). We recommend Cloudflare with the following settings:
  1. SSL: Full [not Full (strict)]
  2. Proxy Status: Enabled (orange cloud)
Fast Track will supply a load balancer, which you’ll need to point your configured domains to via CNAME.
If you are unable to set SSL as Full, you may use the CloudFlare Page Rule functionality. Here you will be able to set SSL to Full.
The URLs would need to be added as follows in the Page Rule:
  1. unsubscribe.brand.com/*
  2. l.brand.com/*

How the Unsubscription Flow Works (Using Fast Track’s Solution)

User clicks to unsubscribe via Email or SMS.
User is redirected to the Unsubscription Landing Page provided by Fast Track.
Once the user completes the opt-out action, Fast Track sends a POST request to your Operator API’s user consents endpoint to notify you of the change.
POST /userconsents/:userid
Fast Track will detect the source of the player’s unsubscription (Email or SMS) and update the corresponding opted_in status for that communication type in the payload.
After processing the update, your platform should send a User Consents real-time event back to Fast Track.
Once Fast Track receives this User Consent event, FT will then send a GET request to your user consents endpoint to retrieve the most recent subscription preferences for that player.
GET /userconsents/:userid

Alternative Flow (If you are using your own Unsubscription Solution)

If you choose to manage unsubscriptions outside of Fast Track, the flow would be as follows:
When a player unsubscribes using your own solution, your platform should send a User Consents real-time event to Fast Track.
Upon receiving this event, Fast Track will make a GET request to your user consents endpoint to fetch the latest preferences and reflect the update accordingly.
GET /userconsents/:userid