You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
web3modal sends a lot of analytics to Datadog, Segment, LaunchDarkly (originating from dynamic scripts loaded from magic.link, I think) even when analytics are disabled in the config. Previously in V4 it was possible to disable this by setting enableEmail to false. In V5 that parameter was removed and replaced with the auth object, but setting its email field to false has no effect, it only visually disables the email feature.
Here's a screenshot of the 3rd party requests sent by the V5 version from the repro example (thankfully those requests were blocked by adblock):
And here's a similar screenshot but for the V4 version of the same code (with enableEmail: false):
Ideally I want to keep the ability to use email wallets without unnecessary analytics being sent but I'll settle for just being able to disable them both. And I checked, email wallets work fine with all of those requests blocked, so they're definitely not necessary.
(the reproducible example doesn't run in the browser because I assume WalletConnect SDK requests encounter this error: (blocked:NotSameOriginAfterDefaultedToSameOriginByCoep), so you need to download the project code from stackblitz and run it locally)
List of related npm package versions
"@web3modal/ethers": "5.0.3",
"ethers": "6.9.0",
The text was updated successfully, but these errors were encountered:
Link to minimal reproducible example
https://stackblitz.com/edit/web3modal-analytics-repro?file=src%2FApp.tsx
Summary
web3modal sends a lot of analytics to Datadog, Segment, LaunchDarkly (originating from dynamic scripts loaded from magic.link, I think) even when analytics are disabled in the config. Previously in V4 it was possible to disable this by setting
enableEmail
tofalse
. In V5 that parameter was removed and replaced with theauth
object, but setting itsemail
field tofalse
has no effect, it only visually disables the email feature.Here's a screenshot of the 3rd party requests sent by the V5 version from the repro example (thankfully those requests were blocked by adblock):
![](https://private-user-images.githubusercontent.com/4591884/343685567-26b53f32-2905-4c51-b66f-3b372f6e34c0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1ODIwNzksIm5iZiI6MTcyMDU4MTc3OSwicGF0aCI6Ii80NTkxODg0LzM0MzY4NTU2Ny0yNmI1M2YzMi0yOTA1LTRjNTEtYjY2Zi0zYjM3MmY2ZTM0YzAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxMCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTBUMDMyMjU5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTBhOTY3N2E5NmNhNDgxNzc5OGFlMzQzZTE2ZjM5MzdkOTY4MDhhMjJkYzJiNmZiYzFhY2E4YTVkYWU5MDFjZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ._wQ7tWHbUkpsVWGjC-EGR8k-hUUzfWQqAfdBoxU0OIw)
And here's a similar screenshot but for the V4 version of the same code (with
![](https://private-user-images.githubusercontent.com/4591884/343686443-7f78a0f2-7ebb-4521-9a3e-fe7f0108f973.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1ODIwNzksIm5iZiI6MTcyMDU4MTc3OSwicGF0aCI6Ii80NTkxODg0LzM0MzY4NjQ0My03Zjc4YTBmMi03ZWJiLTQ1MjEtOWEzZS1mZTdmMDEwOGY5NzMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxMCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTBUMDMyMjU5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NzRjN2IxNDgyYWExYTJhNWU4ZmNhOTcyY2FhMWRhOTYwYzVkYzBiMGZkMzY2MjQ5MmRlZWRhODVhODVmMzkyYyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.RQnoqiLUkbiX7j_cJGmkIfernwWprDJlhsYUOu3B2Zs)
enableEmail: false
):Ideally I want to keep the ability to use email wallets without unnecessary analytics being sent but I'll settle for just being able to disable them both. And I checked, email wallets work fine with all of those requests blocked, so they're definitely not necessary.
(the reproducible example doesn't run in the browser because I assume WalletConnect SDK requests encounter this error:
(blocked:NotSameOriginAfterDefaultedToSameOriginByCoep)
, so you need to download the project code from stackblitz and run it locally)List of related npm package versions
"@web3modal/ethers": "5.0.3",
"ethers": "6.9.0",
The text was updated successfully, but these errors were encountered: