Unsubscribe & Shortlink

Fast Track offers an intuitive and seamless Unsubscription Landing Page to help you provide a smooth opt-out experience for your players.

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 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.
​

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

  1. A user clicks to unsubscribe via email or SMS.
  2. They are directed to the Unsubscription Landing Page provided by Fast Track.
  3. 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.
    1. Endpoint required: POST /userconsents/:userid
  4. After processing the update, your system should send a User Consents real-time event back to Fast Track.
  5. Fast Track will then send a GET request to your user consents endpoint to retrieve the most recent subscription preferences for that player.
    1. Endpoint required: GET /userconsents/:userid
​

Alternative Flow (If You’re Using Your Own Unsubscription Solution)

If you choose to manage unsubscriptions outside of Fast Track, the flow would be as follows:
  1. When a player unsubscribes using your own solution, your platform should send a User Consents real-time event to Fast Track.
  2. 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.
    1. Endpoint required: GET /userconsents/:userid