Use your own domain for links in SMS

Loopify's custom SMS links by default are rendered with the domain https://lpy.io. If you want to change this and add your own custom rendering domain, you'd need to add and verify it:

• Go to Settings > SMS > Custom Domain
• In the Your URL field, add your own rendering domain. 
• Click Add. You'll see a CNAME record.

There are three ways to continue, if your domain is managed in Cloudflare you can see step 3 directly. If it is not, use the general Reverse Proxy path for HTTPS.

1. HTTP (simplest)

If you do not require HTTPS, update your DNS records redirecting your domain to link-tracker-elb-1083637486.eu-west-1.elb.amazonaws.com. 

Once the DNS record has propagated, your links will be available at http://sms.yourcompany.com

Note: All traffic to this domain (including a subdomain of your choosing) will be redirected to Loopify and cannot be used for other purposes.
 

2. HTTPS (Reverse proxy)

If you want your own custom domain to use https and your DNS provider does not support redirecting https traffic, you'd want to create a reverse http proxy. Instead of pointing the CNAME record to link-tracker-elb-1083637486.eu-west-1.elb.amazonaws.com, point it to your http proxy server. The server needs a SSL ceritificate to support https. Here's some steps:

• Create a subdomain (like sms.yourcompany.com).
• Set up a reverse proxy (for example Nginx/Apache).
• Install an SSL/TLS certificate for the subdomain and listen on port 443 

Forward all requests to Loopify:

link-tracker-elb-1083637486.eu-west-1.elb.amazonaws.com

• Redirect HTTP to HTTPS (this is optional)
• Verify by visiting https://sms.yourcompany.com.

Ngix example

server {
    listen 443 ssl;
    server_name sms.yourcompany.com;

    ssl_certificate /etc/ssl/certs/yourcompany.crt;
    ssl_certificate_key /etc/ssl/private/yourcompany.key;

    location / {
        proxy_pass http://link-tracker-elb-1083637486.eu-west-1.elb.amazonaws.com;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $remote_addr;
    } 
} 

HTTP > HTTPS redirect 

server {
    listen 80;
    server_name sms.yourcompany.com;
    return 301 https://$host$request_uri;
}

Read more at the described workaround to get some pointers on how to do it on SMS.
 

3. HTTPS with Cloudflare (adding an SSL certificate to your server)

If your domain is on Cloudflare, Cloudflare itself acts as the reverse proxy and handles HTTPS certificate. No separate Nginx/Apache is required.

DNS

Type: CNAME

Value: link-tracker-elb-1083637486.eu-west-1.elb.amazonaws.com

Proxy status: Proxied (orange cloud ON)

SSL/TLS settings

• In SSL/TLS → Overview, set SSL mode = Full (not Flexible).
• In SSL/TLS → Edge Certificates, enable Always Use HTTPS and Automatic HTTPS Rewrites (optional).
• Wait for Cloudflare to issue an edge certificate.

When your SSL certificate is active, you should no longer see security warnings on your domain.

Troubleshooting

• DNS not resolving - Propagation delay or wrong record. Verify with dig / nslookup and ensure the CNAME is correct.
• SSL error - Missing/misconfigured certificate or Cloudflare SSL mode. For Cloudflare use Full.
• 525 Handshake Failed (Cloudflare) - You likely selected Full (Strict). Change to Full.
• Redirect loop - Duplicated redirects (origin + Cloudflare). Keep only one: prefer Cloudflare’s “Always Use HTTPS”.
• 404 / Timeout - Wrong target. Ensure proxy_pass / CNAME points to link-tracker-elb-1083637486.eu-west-1.elb.amazonaws.com

Track Loopify SMS with Google Analytics

In order to do this, you would of course need to have Google Analytics activated for your domain. You would then need to use your own domain to render Loopify SMS and have it fully set up. When you have a tracking code (ID) from Google Analytics, you can then reach us at support@loopify.com so we would help to implement it in the SMS you use, and you can start tracking!

Now render some Loopify SMS with your own domain. Your audience can't wait 🙌