Loading

Account Engagement content in Browser "Has Been Blocked by CORS Policy"

Fecha de publicación: Sep 30, 2025
Descripción
It's possible for Account Engagement assets within Landing Pages or Forms to not load correctly, or for Account Engagement scripts to not execute as expected. Viewing the console error information in the browser reveals an error similar to this example:

"Access to XMLHttpRequest at '<path-to-cross-object-resource>' from origin <'path-of-current-url-origin>' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."

This error is likely being caused by an old "base href" path entry in the underlying HTML for the Account Engagement asset. Old layout templates are often reused, even after new tracker domains are established within Account Engagement , and those older layout templates will still have a "base href" value pointing to https://go.pardot.com. While this didn't cause issues in the past, this CORS policy block is becoming more prevalent as web browsers continue to tighten down default security settings.
Solución
Update your base href entries within your Account Engagement layout templates to point to the correct custom tracker domain. For example, if my custom Account Engagement tracker domain is https://example.com then I would edit the layout template, and update the line within the "head" section from:
base href="https://go.pardot.com"
to
base href="https://example.com"

Then test the resources used by that layout template to ensure they function as expected.

NOTE: After your custom primary tracker domain is established, newly created layout templates automatically contain the correct base href path for that domain.
Número del artículo de conocimiento

000389675

 
Cargando
Salesforce Help | Article