What are the potential risks and limitations of self-hosting the Salesforce Marketing Cloud Personalization JavaScript Beacon as a solution to prevent the beacon from being blocked by ad blockers?

Hi everyone,

We're currently experiencing an issue with Salesforce Marketing Cloud Personalization (MCP) where the JavaScript beacon fails to load for users with ad blockers enabled (e.g., Brave Browser Shields, uBlock Origin, AdBlock Plus, and similar extensions).

We came across Self-Hosting the JavaScript Beacon as a potential solution. Before proceeding, we'd appreciate some clarification on a few implementation and maintenance aspects.

About Update Process & Versioning

1. How frequently is the JavaScript beacon typically updated by Salesforce MCP?
2. Does Salesforce publish version numbers, release notes, or changelogs for beacon updates so customers can identify what has changed?
3. Is there an API or endpoint available to programmatically check for the latest beacon version, or is the only option to manually download it from the MCP Admin settings?

About Implementation

1. Should we self-host only the synchronous beacon, or should both the synchronous and asynchronous beacon files be self-hosted?
2. Does the hosted file need to retain the original filename (evergage.min.js), or can it be renamed on our CDN?
3. Are there any recommended CDN configurations (such as CORS headers, cache-control settings, MIME types, compression, etc.) required for the beacon to function correctly?

About Limitations & Risks

1. Are there any MCP features, integrations, or capabilities that are not supported or may behave differently when using a self-hosted beacon?
2. Has Salesforce observed any increase in tracking issues, data loss, or event collection discrepancies in customer environments using self-hosted beacons?
3. If a newly released beacon version introduces an issue, does Salesforce provide access to previous versions or recommend a rollback strategy?

About Support & Best Practices

1. Is self-hosting the beacon an officially supported deployment model by Salesforce Support, or is it considered a customer-managed implementation?
2. Are there any customer implementation examples, reference architectures, or documented best practices for self-hosting the beacon?
3. What is the recommended approach for validating a new beacon version before promoting it to production (e.g., sandbox testing, staged rollout, canary deployment)?

We'd appreciate any guidance, documentation, or implementation experience that the community can share.   

@* Marketing Cloud Intelligence * @* Marketing Cloud Engagement *