Branded Domain

Learn how to configure system and custom domains to generate branded tracking links to boost engagement.

Overview

Branded Domains in CleverTap help you apply your brand to tracking across Email, SMS, WhatsApp, and RCS campaigns.

  • For SMS, WhatsApp, and RCS campaigns: It is used to generate short, branded, trackable links.
  • For Email campaigns: It is used to brand links and open-tracking pixels using a custom domain.

Using branded domains improves user trust and can boost engagement rates.

Private Beta

This feature is currently released in Private Beta. If you want to access the feature, contact your Customer Success Manager.

Domain Types

CleverTap supports two types of branded domains:

DomainDescriptionSupported Channels
SystemCleverTap provides a system domain based on your region, for example, ct3.io. You choose a custom prefix/path called the Adjoiner for easy integration without the need for DNS configuration. It allows you to define the URL structure (Branded URL Schema) and customize 404 error pages.WhatsApp, SMS & RCS
CustomEnables you to use your own domain for complete control over your branding and tracking. To use a custom domain, you need to configure DNS records with your domain provider for proper verification and campaign tracking.Email, SMS

Domain Limit

You can add up to 5 unique custom domains per account per channel.

System Domain

Use this domain to get branded links without DNS configuration.

Add System Domain

You can create a system domain to quickly start using branded links in your WhatsApp/SMS & RCS campaigns without DNS configuration. To add a system domain, enter the following details:

  1. Go to Settings > Set Up > Branded Domain.

  2. Click Add Domain and select the channel.

    Select Channel for Adding Branded Domain

  3. Select Domain Type as System.

  4. Enter the following details:

    Add System Domain

    FieldDescription
    NicknameEnter a name to identify the domain (for example, "Marketing").
    ChannelDisplays the channel for which the branded domain is being created.
    Domain Type
    • A CleverTap-provided system domain that can be customized with your brand prefix.
    • No DNS setup required.
    • This is available only for WhatsApp/SMS & RCS channels.
    DomainThe base domain used for branding and tracking. When adding a system domain, this is auto-filled based on your account region. For more information, refer to Domain and Account Region Mapping for WhatsApp/SMS & RCS below the table.
    Branded URL SchemaDefines the structure of the branded tracking URL. This is available for WhatsApp/SMS & RCS channels and is required to add a system domain.
    URL Structure: domain/adjoiner/Shortkey, for example, ct3.io/clevertap/abc123
    This includes the following:
    • Domain: The domain entered above is prepopulated here.
    • Adjoiner: A brand-specific path separator that connects the Domain and Shortkey, helping personalize and group URLs. The Adjoiner can only contain lowercase letters, numbers, and hyphens. It must not start or end with a hyphen, and cannot contain special characters.
    • Shortkey: A unique, auto-generated code added to the branded domain, helping track clicks on links within campaigns.
    Error PageThe page users see if a tracking link is invalid or has expired. You can use CleverTap's system error page or provide a custom URL to maintain brand consistency even in error scenarios. Click Preview Error Page to view and verify the error before the domain becomes active.
  5. Click Save. The status is set to Active immediately.

Domain and Account Region Mapping for WhatsApp/SMS & RCS

Best Practices for System Domain

  • Choose a short and meaningful Adjoiner that clearly represents your brand or campaign type.
  • Use lowercase letters and hyphens (-) if needed (for example, /clevertap/, /new-user/, /sale2024/).
  • Keep it concise: Aim for 5–8 characters in the Adjoiner (excluding the slashes) to avoid long URLs in campaigns.
  • Avoid vague terms such as /track/ or /link/; use something unique to your brand.

Custom Domain

Use this option to use your own subdomain for SMS without managing infrastructure. This option allows you to fully control the branding and tracking for your campaigns.

📘

Custom Domain

You can add up to 5 unique custom domains per account per channel.

Add Custom Domain

To add a custom domain for SMS, perform the following steps:

  1. Click Add Domain and select the channel.

  2. Enter the following details:

    Add Custom Domain for WhatsApp/SMS & RCS

    FieldDescription
    NicknameEnter a name to identify the domain (for example, "Marketing").
    ChannelThe channel this branded domain will be used for.
    Domain TypeYour own subdomain (for example, links.yourbrand.com) that requires DNS configuration.
    DomainEnter your own subdomain to be used for branding and tracking.
    Branded URL SchemaDefines the structure of the branded tracking URL. It defines the structure of the branded tracking URL.
  3. Click Save & Generate DNS after adding all the details. The domain status is set to Pending Verification immediately, and DNS Records are generated to add them to your Domain provider dashboard. The generated records include two CNAME records and one TXT record.

Best Practices for Custom Domain

  • Use a subdomain such as links., click., or promo. (for example,links.yourbrand.com, click.yourbrand.com).
  • Keep the Subdomain short, relevant, and easy to remember.
  • Avoid complex words, long phrases, or special characters in the Subdomain name.

Manage Branded Domains

The Domain Listing page allows you to view and manage all your configured domains. You can easily edit domain settings, view DNS records, and make any necessary updates to check if your domains are correctly set up and functioning.

Go to Settings > Set Up > Branded Domains. You can see a list of all your domains (system or custom), including the following details:

Branded Domains Page

ColumnDescription
NicknameA user-defined name to help you identify the domain (for example, "Sales Campaign").
Domain URLDisplays the full URL of the branded domain being used for tracking links in the case of WhatsApp/SMS & RCS campaigns (for example, ct3.io/clevertap/abc123). Displays the branded domain being used for email campaigns (for example, track.yourdomain.com).
Managed ByIndicates who manages the domain infrastructure: CleverTap (CleverTap-managed) or Self (self-managed).
Created ByThe email address of the user who created the domain.
StatusThe current status of the domain. It can be:
  • Active: Domain is verified and ready to be used in campaigns.
  • Pending Verification: Domain is awaiting DNS verification and cannot be used until verified.
  • Failed: Domain verification failed due to incorrect or missing DNS records.


For Self-Managed Domains:
  • Verify that your CloudFront distribution is properly configured and actively serving traffic.
  • Ensure the TXT record is configured with your DNS provider and your CloudFront distribution is set up.
  • Ensure the TXT record is correctly configured. If the TXT record is correct, verify your CloudFront setup.
Last Updated OnThe timestamp when the domain settings were last updated.

After adding the domain, you can perform the following operations by hovering over it:

Manage Branded Domains

  • Set as Default: You can set one verified domain as the default for WhatsApp, SMS, and RCS, and a different verified domain as the default for Email. This domain is automatically used for links in SMS, WhatsApp, RCS, and Email campaigns (including template buttons). You can override it per campaign when creating new ones.

  • Edit: You can change the domain nickname. Additionally, for WhatsApp/SMS & RCS campaigns, you can set a custom 404 error page (except for system defaults).

  • Verify Domain: You can manually verify the domain by checking the status. If the verification fails, you can click the icon next to the domain to retry after making the necessary corrections.

  • View DNS Records: You can access and review the DNS settings associated with your domain. For CleverTap-managed domains, this includes details such as CNAME and TXT records. For self-managed domains, this displays only the TXT record; your CloudFront configuration is managed separately in your AWS account. By viewing these records, you can ensure that the domain is correctly configured with your DNS provider for seamless integration and functionality.

Common Best Practices

The following are some of the common best practices for using a branded domain:

  • Keep the domain short, relevant, and easy to remember.
  • Avoid complex words, long phrases, or special characters in the domain name.
  • Ensure you configure DNS records exactly as shown after setup to avoid delays in verification.

FAQs

Q. Can I switch between path-based and query-based adjoiners?

No, you must choose one format per domain: either path-based (/yourbrand/) or query-based (?key=yourbrand). You cannot mix both formats in a single domain configuration.

Q. What happens if my custom domain becomes unverified?

If a branded domain used for Email moves from Active to Pending Verification or Failed:

  • CleverTap sends an email alert to inform you of the status change.
  • CleverTap automatically falls back to the system domain for email click and open tracking.
  • Email campaigns continue to send without interruption.

Once the domain is verified again, it can be reused in future campaigns.

Q. Will old campaigns use the new branded domain?

No. Campaigns created before you set up a branded domain will continue using the System Domain unless you manually edit or recreate them with the new branded domain.

Q. I configured the DNS records, but my domain has still not been verified. What should I do?

Check the following:

  • DNS records are entered exactly as shown in the CleverTap dashboard.
  • You have entered only the required prefix in the Key field (for example, short, not short.clevertap.com).
  • Wait up to 24 hours, then try refreshing again.

Q. When will a link preview be shown for my branded domain link?

A link preview is generated when the messaging platform (such as SMS, WhatsApp, or RCS) scans the URL included in your message and detects the required Open Graph metadata on the destination page. The following tags must be present and properly configured in the page’s HTML:

  • <meta property="og:title" content="...">
  • <meta property="og:description" content="...">
  • <meta property="og:image" content="...">

If these tags are available and valid, the platform may display a visual preview containing a title, description, and image. A preview may not be shown in the following cases:

  • The Open Graph tags are missing or incorrectly implemented.
  • The domain is blocked by robots.txt or firewalls.
  • The page is inaccessible to external crawlers.

To verify that your Open Graph metadata is implemented correctly, use a metadata testing tool or an Open Graph debugger.

Q. How do link previews work on iOS devices, and why might they not appear?

iOS devices running iOS 10 or later support link previews in the native Messages app. These previews may still appear for SMS-based messages, but several conditions must be met for reliable rendering.

Preview Requirements

  • Only one link should be included in the message. Messages with multiple links will not generate a preview.
  • The link must be the final element in the message. No text, punctuation, or symbols should follow the link.
  • The domain must be served over HTTPS and use a valid SSL certificate. Self-signed, expired, or incomplete certificates will block preview generation.
  • The recipient must tap Tap to Load Preview for metadata to be fetched.

iOS-specific Behaviors and Limitations

  • iOS delays metadata fetching until after the message is delivered, and in some cases, until the user interacts with the message.
  • Devices may display cached metadata even after updates to the page’s Open Graph tags.
  • Certain third-party messaging apps may block previews by default, unless they are explicitly enabled in the settings.

These constraints can lead to inconsistent preview rendering on iOS devices, even when metadata is correctly configured.

Q. Who is responsible for CloudFront and SSL certificates with a self-managed domain?

With a self-managed domain, you are fully responsible for:

  • Setting up and configuring the CloudFront distribution.
  • Configuring cache behaviors and origin settings.
  • Managing and renewing SSL certificates.
  • Ensuring the distribution remains active and properly configured.
  • Monitoring CloudFront and troubleshooting issues.
  • CleverTap is responsible only for link-tracking verification and TXT record validation.

Q. Can I switch from CleverTap-Managed to Self-Managed Domain?

Direct Migration is not currently possible. But you can create a new domain in parallel:

  1. Create a new self-managed domain with a different domain
  2. Set up your CloudFront distribution and SSL certificate for the new domain.
  3. Update campaigns to use the new domain.
  4. Once verified and tested, delete the old CleverTap-managed domain.

Contact your Customer Success Manager for assistance with domain transitions.

Q. What happens if my self-managed domain's CloudFront distribution goes down?

If your CloudFront distribution becomes unavailable:

  • Tracking links will not function properly.
  • Campaign links may return errors or fail to redirect.
  • Email click and open tracking may be affected.

Ensure you have monitoring and alerting in place to quickly identify and resolve any issues.



Did this page help you?
CleverTap Ask AI Widget (CSP-Safe)