Merge pull request #129 from segmentio/repo-sync

bot-docsteam · web-flow · commit b4bf241dbe9a · 2021-11-18T09:35:51.000-08:00
repo sync
diff --git a/src/connections/storage/catalog/google-cloud-storage/index.md b/src/connections/storage/catalog/google-cloud-storage/index.md
@@ -9,7 +9,8 @@ redirect_from: '/connections/destinations/catalog/google-cloud-storage/'
 
 The Google Cloud Storage (GCS) destination puts the raw logs of the data Segment receives into your GCS bucket. The data is copied into your bucket at least every hour. You might see multiple files over a period of time depending on how much data is copied.
 
-Keep in mind that GCS works differently from most of our destinations. Using a destinations selector like the [integrations object](https://segment.com/docs/connections/spec/common/#integrations) does not affect events in the case of GCS.
+> warning ""
+> The Google Cloud Storage destination works differently than other destinations in Segment. Segment sends **all** data from a Personas source to GCS during the sync process, not only the connected audiences and traits. Using a destinations selector like the [integrations object](/docs/connections/spec/common/#integrations) doesn't affect the events events sent to GCS.
 
 **Note**: The GCS destination is currently in beta, and does not support product features such as deletions, replays, or surfacing errors in the UI.
 
