## TL;DR

It needs the applicationKey set in your Sentry bundler plugin config, and it does not work with the loader script or CDN bundles (the SDK itself looks third-party there). ignoreErrors: ["fb\_xd\_fragment", /^Exact Match$/] drops known junk by message. Strings are partial matches; use regex for exact matches. This is for recurring known noise, not for errors you have not classified.

## When to use

You are seeing this: Open a few noisy issues and look at the stack frames. Use this skill when you run into "Diagnose: issue stream full of third-party and extension noise".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Step 1: confirm the source

Open a few noisy issues and look at the stack frames. Frames from `chrome-extension://`, injected wallet scripts, or ad widgets mean the error is not your code. Filtering these is safe; they will never be actionable.

## Step 2: filter by origin

```js
Sentry.init({
  allowUrls: [/https?:\/\/((cdn|www)\.)?example\.com/],
});
```

`allowUrls`/`denyUrls` match against stack frame origins, not the page URL. `allowUrls` keeps only errors whose frames come from your domains. This is the cheapest filter and it runs before the event is built.

## Step 3: the third-party filter integration

For bundler builds, `thirdPartyErrorFilterIntegration` marks your files with an `applicationKey` at build time and filters errors by frame marking at runtime. Modes range from dropping errors containing any third-party frame to just tagging them (`third_party_code: true`) so you can filter in the issue search. It needs the `applicationKey` set in your Sentry bundler plugin config, and it does not work with the loader script or CDN bundles (the SDK itself looks third-party there).

## Step 4: message patterns

`ignoreErrors: ["fb_xd_fragment", /^Exact Match$/]` drops known junk by message. Strings are partial matches; use regex for exact matches. This is for recurring known noise, not for errors you have not classified.

## Verify

After deploying the filter, watch the issue stream for a day: the junk categories should stop appearing while your own errors continue. If your own errors vanish too, the allowUrls pattern is too narrow; check it against the actual frame origins in a kept issue.
