In the past, tracked links in Customer.io were served via HTTP. This presented a number of challenges in certain use-cases where HTTPS links were required.
We’re happy to announce that we now support upgrading tracked links to HTTPS as an extra step in the domain verification process!
What benefits do HTTPS links provide?
White labelled track links will work seamlessly
HTTPS link verification means that if your website domain is enforcing HTTP Strict Transport Security (HSTS), you will be able to use white labelled link tracking because the link tracking subdomain is verified with a valid SSL certificate and configuration which passes the HSTS enforcement.
Fully track universal links to your mobile apps
iOS or Android app links are often referred to as “universal” or “deep” links. We didn’t support this before, because universal links require an unbroken chain of HTTPS connections from beginning to end. Now, with HTTPS enabled, you can fully track links to your mobile app from your Customer.io messages!
How to get started with HTTPS link tracking
To get started, head over to the Deliverability tab of the Email & Actions section. You’ll see a new verification status for HTTPS links:
Passing the HTTPS check
Before generating HTTPS tracking links for your account we need to verify two things:
- Does your link tracking subdomain resolve to the Customer.io API?
- Does your link tracking subdomain have a valid HTTPS certificate?
To pass the first check all you would need is the CNAME record we required in the past pointing your subdomain to
Passing the second check requires a valid SSL configuration for your link tracking subdomain. This process is fairly technical and up to your engineering team to determine the best implementation for your environment.
To help point you in the right direction we have tested and documented two methods which you can read about in our Knowledge Base:
Need more information?
Want to learn more about setting up universal links? We have detailed documentation for universal links in our Knowledge Base.
We’ve also updated our documentation for domain authentication to reference the new HTTPS verification steps.
Questions, feedback, or need a hand? We’re here for you at firstname.lastname@example.org.!