Merge remote-tracking branch 'upstream/develop' into develop

Author: lopenchi

src/connections/auto-instrumentation/web-setup.md

@@ -357,6 +357,14 @@ Network signals emit when an HTTP Request is made, or an HTTP Response is receiv
 - First party domain (for example, if on `foo.com`, then `foo.com/api/products`, but not `bar.com/api/products`)
 - Contains the content-type: `application/json`
 
+## Troubleshooting
+
+Here are the most common misconfigurations preventing signals from reaching Segment.
+
+- Not enabling signals with the URL parameter: You must start each debug session by appending `?segment_signals_debug=true` to your URL parameters.
+- Running debug mode with an ad blocker: An active ad blocker prevents signals from reaching Segment. Disable your ad blocker and start a new session.
+- Content Security Policies: In addition to the [default Analytics.js Content Security Policies](/docs/connections/sources/catalog/libraries/website/javascript/faq/#does-segment-support-using-strict-content-security-policy-csp-on-the-page), you must add `cdn.jsdelivr.net` to your allowlist, or `https://cdn.jsdelivr.net/npm/@segment/analytics-signals@latest/dist/umd/analytics-signals.umd.js` if your policies require the full path.
+
 ## Next steps
 
 This guide walked you through initial Signals SDK/Auto-Instrumentation setup. Next, read the [Auto-Instrumentation Signals Implementation Guide](/docs/connections/auto-instrumentation/configuration/), which dives deeper into Signals and offers example rules.

src/privacy/user-deletion-and-suppression.md

@@ -43,7 +43,7 @@ The following Segment & Destination Regulations are available:
 
 ## Deletion Support
 
-When you create a `SUPPRESS_WITH_DELETE` and `SUPPRESS_WITH_DELETE_INTERNAL` regulation, Segment begins to suppress new data ingestion for that user, and begins to permanently delete previously ingested data associated with this user from your workspace. This includes scanning and removing all messages related to that `userId` from all data stores that don't automatically expire data within 30 days.
+When you create a Segment-only regulation, Segment begins to suppress new data ingestion for that user, and begins to permanently delete previously ingested data associated with this user from your workspace. This includes scanning and removing all messages related to that `userId` from all data stores that don't automatically expire data within 30 days.
 
 Segment deletes messages with this `userId` from the following warehouses and storage destinations:  
 - Redshift
@@ -129,4 +129,4 @@ Segment creates a `SUPPRESS` regulation, and adds the `userId` to your suppressi
 
 To remove a user from the suppression list, click the ellipses (**...**) icon on the `userId` row, and click **Remove**.
 
-This creates an `UNSUPPRESS` regulation and removes the `userId` from your suppression list. Segment processes most `UNSUPPRESS` regulations within 24 hours.
+This creates an `UNSUPPRESS` regulation and removes the `userId` from your suppression list. Segment processes most `UNSUPPRESS` regulations within 24 hours.