upgrade-browser-sdk-v7

Automate Datadog Browser SDK migration from v6 to v7 across projects.

150|23|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/datadog-labs/agent-skills --skill upgrade-browser-sdk-v7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-browser-sdk-v7
Source: https://github.com/datadog-labs/agent-skills/tree/main/dd-browser-sdk/upgrade-v7
Command: npx skills add https://github.com/datadog-labs/agent-skills --skill upgrade-browser-sdk-v7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading the Datadog Browser SDK from v6 to v7 to align with removed options, CDN path changes, and API updates across projects.

Core Features & Use Cases

  • Stepwise migration guide covering version bumps, CDN URL updates, removal of deprecated options, API changes, and infrastructure adjustments.
  • Applicable to projects using datadoghq-browser-agent.com CDN with /v6/ paths or affected SDK configurations.

Quick Start

Follow the six-step migration guide to upgrade the Datadog Browser SDK from v6 to v7 and verify all changes using the included checklist.

Frequently Asked Questions about upgrade-browser-sdk-v7

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Datadog Browser SDK from v6 to v7?

To migrate Datadog Browser SDK from v6 to v7, follow a stepwise guide covering version bumps, CDN URL updates, deprecated option removals, and API changes. Verify all infrastructure adjustments using the included checklist.

What changed in Datadog Browser SDK v7 that requires a migration?

Datadog Browser SDK v7 removes deprecated options, updates CDN paths from /v6/, and introduces API changes. These breaking modifications require updating version references and infrastructure configurations to ensure compatibility.

Do I need to update CDN URLs when upgrading the Datadog Browser SDK?

Yes, upgrading the Datadog Browser SDK requires updating CDN URLs. Projects referencing datadoghq-browser-agent.com CDN with /v6/ paths must be updated to align with the new v7 CDN path structure.

What is the best way to handle deprecated options removed in Datadog Browser SDK v7?

The best way to handle deprecated options removed in Datadog Browser SDK v7 is to apply the stepwise migration guide, systematically removing affected configurations and replacing them with updated API equivalents.

Can I use this migration process for projects using the datadoghq-browser-agent CDN?

Yes, this migration process is applicable to projects using the datadoghq-browser-agent.com CDN. It specifically targets configurations referencing /v6/ paths and SDK setups needing updated APIs and options.

Why does my Datadog Browser SDK configuration break after a v7 upgrade?

Your Datadog Browser SDK configuration breaks after a v7 upgrade because v7 removes deprecated options, changes CDN paths, and updates APIs. You must adjust your infrastructure and remove outdated options per the upgrade guide.