When you share content and tracked links, they are visible by default as a leadcamp.io tracked link. Your URL will then look like this: api.leadcamp.io/anywhere.

Using your own URL has several advantages. For example, it allows you to increase email deliverability and protect your domain reputation opposed to using a shared domain. Using a custom domain, your URL will look like: content.example.com/anywhere.

You can change this by adding a CNAME record to your DNS settings.

Where will this custom domain be visible?

  • A tracked link will redirect through your custom domain before reaching the final URL. A recipient will see your custom domain if they hover over a link.

  • It is also used as the path for the tracking pixel to track email message opens.

How to create a custom CNAME record

These steps will vary, so check with your own DNS provider for support.


As an example, here are the basic steps:

  1. Go to the ‘DNS’ section of your DNS provider's management portal

  2. Add a CNAME record for your custom tracking domain

  3. Give the CNAME a Name based on the first part of your custom domain
    e.g. if you want an url like this: content.example.com, use content

  4. Point it at the Leadcamp host domain: http://custom.leadcamp.io

  5. Now go to Leadcamp and give in the CNAME you created.

Here's a list on how to set it up with different providers

Choose to configure SSL (optional)

After you set up a custom domain, URLs will be linked to your domain, but on HTTP rather than HTTPS. The redirect links will now appear as ‘not secure’ on web browsers like Chrome.

SSL (or TLS), is the most widely used way to secure the connection between a server and your browser. It ensures the connection between the server and browser is encrypted and safe, and appears as HTTPS.

Here’s what an SSL-configured website (with HTTPS) typically looks like on the Chrome browser:

This is what it looks like if you’ve visited a website not secured by SSL (without HTTPS):

There are two ways to set up SSL on your custom domain:

  • Use a flexible SSL (using a third party DNS provider like CloudFlare or AWS CloudFront)

  • Use your own SSL certificate (using a TLS Termination Proxy)

If you want to do this, make sure you’ve set up your CNAME with a DNS provider that supports SSL.

If you are unable to use flexible SSL, please make sure to register your custom domain inside Leadcamp on HTTP. Otherwise this will not work.

Troubleshooting

Few things to make sure before you report a potential bug:

  • Are you using a wildcard that forces https on your domain?
    If yes, turn it off unless it also supports flexible SSL.

  • Does your server support flexible SSL?
    If not, do not use HTTPS but HTTP instead for this CNAME

  • Did you create the CNAME at least 4 hours ago? (distribution time)
    If not, give it a little bit more time

  • Did you accidentally leave the . (dot) behind the CNAME url?
    If yes, remove it

  • Is your CNAME pointing to custom.leadcamp.io?
    If not, update the CNAME

Long story short, confirm your url looks like this: http://content.example.com


Did this answer your question?