1) Check your CNAME record first. This record is like a digital street sign that directs traffic from your tracker domain (like go.yourcompany.com) to the correct Salesforce server.
Go to your DNS Provider (the company that manages your domain, if you are not sure, speak with your IT network team or hosting provider).
Find the CNAME record for your tracker domain. You can also use third party tools like Google Admin Toolbox Dig or MXToolbox to look up any existing CNAME record for your tracker domain (enter your tracker domain into the search bar).
Make sure the record is pointed correctly to the required go.pardot.com (see documentation for more details. If it is wrong or missing, fix it now.
The CNAME entry is used for initial setup of the tracker domain, as well as the redirect process. It is necessary for SSL refresh, and should remain in your domain’s DNS system indefinitely. If your CNAME record entry has been removed or altered, the refresh will fail, even though the domain still shows as validated.
2) Check your CAA record. The CAA record controls which company (Certificate Authority) is allowed to issue an SSL certificate for your domain. Account Engagement uses Let's Encrypt.
If your root domain (the main part, e.g. yourcompany.com) has any CAA records, you must include an entry for Let's Encrypt.
You can use third party tools like Google Admin Toolbox Dig to search for any existing CAA records on your root domain (enter your root domain into the search bar).
Ask your IT network team to add a CAA record to your root domain for “letsencrypt.org”.
3) Wait 30 Minutes and Re-check the Status in Account Engagement Domain Management. After updating your CNAME or CAA records, you must wait about 30 minutes for the change to spread across the internet.
4) If the status is still 'Processing' after 24 hours, log a support case.
Open a Support Case with Salesforce.
Include your Tracker Domain Name (e.g., go.yourcompany.com).
Confirm in the case description that Steps 1 and 2 from this article (CNAME and CAA checks) are complete and correct.
000380950

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.