Embedded third-party analytics/tracking requests

From the investigation:

• The primary application itself is not being blocked.
• During the session workflow, the application initiates requests to external third-party tracking/analytics domains.
• Netskope identifies the traffic under the application context, but the actual blocked request is towards a third-party analytics/tracking endpoint.
• The current policy categorizes the request under a risk/control policy and blocks it, resulting in a user-facing warning/interstitial.

Requirement:

• Allow the application workflow to continue without user interruption.
• Avoid broadly allowing all third-party tracking traffic globally.
• Maintain the existing security posture and policy controls.

Questions:

1. What is the recommended Netskope approach for handling embedded third-party analytics/tracking requests initiated from applications?  embedded third party urls are connect.facebook.net/log/error , facebook.com/tr & www.facebook.com/privacy_sandbox/pixel/register/trigger/
2. Is there a best practice to suppress/block the user interstitial while still logging or controlling the traffic?