Use Custom Domains For Landing Pages Pro

1. Feature Overview

By default, landing pages created using Landing Pages Pro are hosted on a LeadSquared subdomain. To maintain brand consistency, you can instead publish landing pages on your own custom domain (e.g., pages.yourcompany.com).

This article explains how to configure a custom domain and map it to your Landing Pages Pro environment.

2. Prerequisites

• You are an Admin user in your LeadSquared account.
• You have access to the Landing Pages Pro feature (contact your account manager if not enabled).
• You must first list the domain on the Website & Landing Page Domains page. For details, see Adding More Website Domains (refer to section 4 & 5 in the article).
• Access to your Domain Name Service (DNS) provider’s account (GoDaddy, Hostgator, Bluehost, etc.).

3. How It Works

To publish landing pages on your custom domain securely (over HTTPS), you’ll need to configure two CNAME records in your DNS provider:

• One CNAME record sets up an HTTPS certificate using LeadSquared’s certificate manager.
• The second CNAME record maps your custom domain (e.g., pages.mybusiness.com) to LeadSquared’s CDN endpoint for content delivery.

You’ll switch between the Landing Pages Pro domain settings in LeadSquared and your DNS provider’s dashboard during the setup.

Here’s a quick overview of the steps involved. The following sections explain each in detail:

1. Configure the subdomain in Landing Pages Pro.

LeadSquared will generate a Name and Value pair for the first CNAME record.
This record sets up HTTPS to secure your landing pages.

2. Add and verify the first CNAME record in your DNS provider’s dashboard.

Use the values provided by LeadSquared on your DNS’s provierds dashboard and then verify. This confirms that the HTTPS certificate has been issued and is active.

3. After verification, add the CDN URL from LeadSquared on your provider’s dashboard.

This is used to serve your landing pages efficiently. Add the second CNAME record in your DNS provider. Use your custom domain as the host and the CDN URL as the value.

Once this is complete, your landing pages will be securely accessible via your custom domain.

4. Configure the Subdomain in Landing Pages Pro

To configure your subdomain on Landing Pages Pro –

1. Navigate to Marketing>Landing Pages Pro.
2. Under More Actions select Manage Subdomains.
3. Click the gear icon against the subdomain.

In the SSL setup, click Generate CNAME.

LeadSquared will now generate the CNAME Name and Value. Copy these values.

5. Create and Verify CNAME Record for HTTPS Certificate

In this step, you’ll create a CNAME record in your DNS that connects your domain to a Certificate Manager and sets up an SSL certificate. This ensures your landing pages are secure and served over HTTPS.

Here is some documentation for popular DNS providers –

1. GoDaddy: Add a CNAME record
2. Namecheap: How to Create a CNAME Record For Your Domain
3. Dreamhost: Adding a Custom DNS record
4. Bluehost: DNS Management: How to Add, Edit, or Delete DNS Entries

Log in to your Domain Name Service provider’s account (GoDaddy, Hostgator, Bluehost, etc.).

1. Click on the DNS settings for the selected URL and create a new CNAME record entry. Paste the above values in the Name (or host) and Value (or Target) fields, respectively.
2. Select the minimum TTL value available.
3. Save the record.
4. Successful configurations may take some time to reflect.

Here’s an example from a Cloudflare account –

Navigate back to your LeadSquared account and on the Landing Page Pro Subdomain page, click Verify.

6. Create and Verify CNAME record for the Sub-Domain

7. FAQs

1. Why isn’t my SSL setup getting verified?
If your SSL (HTTPS) setup is not verifying, review the following potential issues:

• Domain mapped to .leadroot.com – If you’re using GoDaddy or Hostinger, ensure that the domain is not mapped to .leadroot.com. Remove any such CNAME entries, as they can interfere with SSL verification. For example, in the image below, remove .leadroot.com from the CNAME:Name field. 
  • 
• CAA records blocking certificate issuance – Check your domain’s CAA (Certification Authority Authorization) records using a tool like nslookup.io:
  • If no CAA records are found, you can proceed with the SSL setup.
  • If CAA records exist, verify that a record allowing amazon.com is present. Specifically, the CAA record should include the issuewild tag for amazon.com. For details, refer to the AWS documentation: Set up CAA records.
• CNAME record expired (72-hour limit) – If more than 72 hours have passed since the CNAME record was generated in LeadSquared, it may have expired. In this case, you must regenerate the CNAME and update your DNS accordingly.

Any Questions?

Leave us a comment below. We’d love to help you out!