Performance ModifyDrop Traffic• 3 min read
How to Block Third-Party Requests, Analytics, and Trackers
Summary: Block outgoing requests matching specified domains, simulating network drops or testing application resilience when third-party services fail.
Why This Rule Matters for Developers & QA
Third-party tracking scripts and ad servers can fail or slow down web apps. Testing how your application behaves when these services are unreachable is critical for stability.
Step-by-Step Implementation Guide
1
Define Domains to Block
Enter patterns for services you want to block (e.g. `*google-analytics.com*`, `*doubleclick.net*`).
2
Select Drop Action
Choose whether to cancel immediately (`net::ERR_BLOCKED_BY_CLIENT`) or return a synthetic 403 Forbidden.
3
Verify App Graceful Degradation
Confirm your application continues functioning normally even when third-party services are dropped.
Configuration Snippet
How to Block Third-Party Requests, Analytics, and Trackers — proxyceptor-rule.json
JSON
{ "id": "rule_block_trackers", "pattern": "*doubleclick.net*", "action": "block", "blockReason": "Ad Tracker Simulation", "enabled": true}