Embedded services may contact external providers when a page loads or when a visitor activates them. Review the actual integration and approved requirements rather than assuming an iframe or privacy-branded mode sends no information.
Before you begin
List the pages using video, maps, chat, calendars, or embedded forms. Identify the provider, installation route, purpose, and any alternative way to access important information.
What to do
- Inspect the page before interacting with the embed. Record relevant external requests, storage, and frames present on the fresh visit.
- Activate the service in a coordinated test and compare what loads. Include opening chat or submitting information only where the test is authorized.
- Review provider configuration and the consent manager’s control over that installation. An embed inside an app may require different settings from one pasted into content.
- If an activation placeholder is appropriate, make its explanation and control accessible. Ensure essential information is still available when the service is not loaded.
- Retest initial load, activation, rejection, and later preference changes. Keep the evidence scoped to the exact embed version and pages reviewed.
How to check the result
The visitor should understand what action will load the service, and the observed behavior should match the agreed configuration. A static placeholder should not silently load the same provider behind the scenes.
If you need help
Send the page, provider, and observed timing if a tool loads unexpectedly. Do not replace an important customer function without arranging a usable alternative and confirming the business requirements.
Related help
- Create an inventory of website tracking and embedded tools
- Test what happens when a visitor accepts or rejects cookies
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
