Loading

Account Engagement Default Domain Changes: Details and FAQs

Udgivelsesdato: Sep 30, 2025
Beskrivelse
Starting April 22, 2022, admins could choose to activate an Account Engagement security update that affects users of the default go.pardot.com domain. This change affects customers who serve Account Engagement forms or other content over the default go.pardot.com domain.

This update was activated automatically for most customers on August 12, 2022. An in-app message on the Dashboard page notifies you whether this update was activated for your account.

If the update hasn't been activated in your org, check your account periodically during August for in-app messages with new details and deadlines. You should continue monitoring the usage report and addressing affected content during this time.

To ensure the uninterrupted use of the affected functionality described, we recommend that you add a custom domain to Account Engagement and serve all Account Engagement content using that custom domain. More on this situation can be found here.
Løsning
What’s changing? What is the impact?
Check out New Limitations on Account Engagement Content and Default Domain for an overview of the changes. 
 

Activating the Security Update

Is the security update activated automatically for my account?
No, but it’s scheduled for automatic activation on August 12, 2022. You can manually activate the security update for your account starting April 22, 2022.

How do I activated the security update for my account?
Visit the Content Served using Default Domain report page, and follow the instructions. This can be found on the Domain Management page of Account Engagement Settings.

Can I deactivate the update after enabling it?
Yes. You can activate and deactivate the update as needed until it’s activated automatically on August 12, 2022. After that date, it can no longer be deactivated.
 

What is Affected

If I’m already using a custom tracker domain for everything, then is there anything I need to do?
No, content served over custom domains aren’t affected by this change.

How do I know which of my content is affected? 
We added a report to Account Engagement Settings, which is updated with affected content as it is accessed by your customers. Check out the Understanding the Content Served using Default Domain Report knowledge article for more information.

Do these changes affect the related campaign or campaign ID? 
No, neither the campaign nor the campaign ID are affected by these changes.

Do these changes affect my tracking code? 
No. Tracking code isn’t affected. You don’t need to make any changes to the Account Engagement tracking code on your web pages.

Do these changes affect my image source URLs?
No. Images using the default domain aren’t affected and continue to work.

Do these changes affect tracking links or custom redirects? 
No. Tracking links and custom redirects aren’t affected and continue to work.

Does changing the domain used in the iframe source affect SEO?
Not really. Iframes don’t generally impact SEO for a page. Because search engines consider the content in iframes to belong to the original embedded page (and not the page with the iframe), changes to the source URL of the iframe should have minimal to zero impact on the page that contains the iframe.

Does this change affect email sending domains? 
No. This change applies to tracker domains only, and no changes to email sending domains are needed.

Do these changes affect form handlers or integrations that utilize form handlers?
No. Form handlers aren’t affected and continue to work.


Making Updates

Do I need to edit each of my forms in Account Engagement and select the new custom tracker domain?
No. A form can always be accessed via the default domain or any configured custom tracker domain, regardless of which tracker domain is selected on the form.

This means that after a custom domain is added to Account Engagement:
The form can immediately be accessed using that custom domain; and
You can immediately start updating any web pages where you’re using the default domain to start using the new custom domain.

Can I change the domain on the form record anyway? 
Yes. You can always change the domain selected on the form. The form will continue to be accessible over both domains.

Does it matter which I do first: update the domain on the form record or update my web pages to use the custom domain?
No, they can be done in any order.

However, only updating your web pages to use the custom domain is required to ensure your forms and other content aren’t impacted by the new limitations on the default domain.

We recommend that you eventually update the domain that is selected on the form record, but it isn’t required for the April 22, 2022 deadline.

Do I need to enable first party tracking for this issue?
No. This change doesn’t require enabling first-party tracking.


Timing and General Information

How long do I have to make these changes?
Until August 12, 2022. The security update is activated automatically on August 12, 2022.

What is happening on April 22, 2022 vs August 12, 2022?
Starting April 22 2022, the security update that puts new limitations on Account Engagement content using the default domain becomes available. Admins can turn on the security update at any time between April 22, 2022 and August 12, 2022. On August 12 2022, the security update will be activated automatically and the new limitations will take effect. At this time, admins can no longer manually activate or deactivate the update.

The new limitations described in this knowledge article and the New Limitations on Account Engagement Content and Default Domain knowledge article do not take effect until the security update is activated in your account.

What happens if I don’t make any changes before the security update is activated?
The form or content continues to be accessible using the default go.pardot.com domain. However, certain included JavaScript no longer functions as expected and could cause issues with form submission or other actions.

Check out 'What’s the impact of this change?' in New Limitations on Account Engagement Content and Default Domain for examples of JavaScript that stops functioning as expected.

What security concerns prompted this change? 
Unfortunately, we can’t comment on the nature of the security issue. We can assure you, however, that we aren't aware of any customer or service being affected by this security issue up to this point.



 
Vidensartikelnummer

000393408

 
Indlæser
Salesforce Help | Article