Merge pull request #2527 from segmentio/develop

Release 22.8.1

Author: stayseesong

.github/workflows/grammar-lint.yml

@@ -17,7 +17,11 @@ jobs:
         #   https://github.com/errata-ai/write-good/releases/latest/download/write-good.zip
 
         # Optional
+<<<<<<< HEAD
+        config: https://raw.githubusercontent.com/segmentio/segment-docs/develop/.vale.ini
+=======
         # config: https://raw.githubusercontent.com/errata-ai/vale/master/.vale.ini
+>>>>>>> master
 
         # Optional
         files: __onlyModified

src/_data/sidenav/main.yml

@@ -364,6 +364,8 @@ sections:
       title: Typewriter
     - path: /protocols/apis-and-extensions/anomaly_detection
       title: Anomaly Detection
+  - path: /protocols/schema
+    title: Schema Controls
   - path: /protocols/faq
     title: Protocols FAQs
 - section_title: Segment App

src/connections/destinations/catalog/firebase/index.md

@@ -273,7 +273,7 @@ Then, enter the deep link URL scheme in your Segment Firebase destination settin
 
 ### **Conversion Tracking and Adwords Conversions**
 
-Firebase is now Google's recommended method for reporting conversions to Adwords! To do so, simply track the conversion events as you normally would with Segment and Segment will send them through to Firebase! Follow [this documentation from Firebase to set up your conversions in Firebase and to have them forwarded to Adwords](https://firebase.google.com/docs/adwords/).
+Firebase is Google's recommended method for reporting conversions to Adwords. To use Firebase, track the conversion events as you normally would with Segment and Segment will send them through to Firebase. 
 
 ### Troubleshooting
 

src/connections/destinations/catalog/onesignal-new/index.md

@@ -48,6 +48,9 @@ Segment sends Identify traits as [Player Data Tags](https://documentation.onesig
 
 ![](images/demo.png)
 
+> info "Data Tag Limits"
+> Your OneSignal plan may cap incoming Data Tags. Once you've reached your Data Tag limit, your user traits won't update in your OneSignal destination.
+
 ### Track
 
 Send [Track](/docs/connections/spec/track) calls to update Data Tags. For example:

src/connections/storage/catalog/bigquery/index.md

@@ -105,19 +105,33 @@ from <project-id>.<source-name>.<collection-name>_view
 For early customers using BigQuery with Segment, rather than providing Segment
 with credentials, access was granted to a shared Service Account
 (`[email protected]`). While convenient for early
-adopters, this presented potential security risks that Segment would prefer to address
-proactively.
+adopters, this presented potential security risks.
 
 As of **March 2019**, Segment requires BigQuery customers to
 create their own Service Accounts and provide the app with those credentials instead.
 In addition, any attempts to update warehouse connection settings will also
 require these credentials. This effectively deprecates the shared Service
 Account.
 
-To stay ahead of this change, migrate your warehouse by following
-the instructions in the "Create a Service Account for Segment" section above.
+Migrate your warehouse from a shared Service Account to a dedicated Service Account 
+by creating a new Service Account using the [Create a Service Account for Segment](#create-a-service-account-for-segment) section.
 Then, head to your warehouse's connection settings and update with the
-**Credentials** you created.
+**Credentials** you created. Once you've verified that data is loading properly 
+to your warehouse, [remove access to the shared Service Account](#remove-access-to-the-shared-service-account).
+
+### Remove access to the shared Service Account
+You can remove access to the shared Service Account 
+(`[email protected]`) using the following instructions:
+
+1. Create a [new Service Account for Segment](#create-a-service-account-for-segment) using the linked instructions.
+2. Verify that the data is loading into your warehouse. 
+3. Sign in to the [Google Developers Console](https://console.developers.google.com).
+4. Open the IAM & Admin product, and select **IAM**.
+5. From the list of projects, select the project that has BigQuery enabled.
+6. On the project's page, select the **Permissions** tab, and then click **view by PRINCIPALS**. 
+7. Select the checkbox for the `[email protected]` account and then click **Remove** to remove access to this shared Service Account.
+
+For more information about managing IAM access, see Google's documentation, [Manage access to projects, folders, and organization](https://cloud.google.com/iam/docs/granting-changing-revoking-access).
 
 
 ## Best Practices
@@ -211,4 +225,4 @@ a need for streaming data into BigQuery, [contact Segment support](https://segme
 ### I'm seeing duplicates in my tables.
 
 This behavior is expected. Segment only de-duplicates data in your views. See the
-section on [views](#views) for more details.
+section on [views](#views) for more details.

src/personas/journeys/build-journey.md

@@ -22,9 +22,6 @@ For more information, see [Setting up your Sources](/docs/personas/quickstart/#s
 4. Segment displays the entry condition on the Journey Builder canvas. It may take up to two minutes for Segment to estimate the number of users in the journey.
 5. Click **+** to add the next step and view available step types.
 
-> info ""
-> Users can only enter a Journey once.
-
 ### Using historical data for the entry step
 
 If you select the **Use historical data** option, Segment queries all historical data to generate a list of users who enter the Journey upon publication. If you don't select **Use historical data**, only users who satisfy the entry condition *after* you publish enter the Journey.

src/personas/journeys/journeys-logic.md

@@ -107,7 +107,7 @@ Each step’s membership conditions evaluate in real time, which means that user
 
 ### Can users exit and re-enter a Journey?
 
-No. Users move down the Journey’s branches in sequential order and can't re-enter. Journeys appends a profile trait for each step a user enters. Because the system neither assigns `Audience Exit` events nor removes traits from profiles, users who meet the Journey's entry criteria stay in the Journey permanently.
+Yes. To allow users to re-enter Journeys that they've exited, [enable re-entry](/docs/personas/journeys/build-journey/#journey-re-entry) during initial Journey setup.
 
 ### What happens to traits and audiences when I delete a Journey?
 

src/segment-app/iam/scim.md

@@ -16,7 +16,7 @@ To set up SCIM, you must first create an SSO connection. Once you [create your S
 
 ## Configuration Instructions
 
-Segment officially supports [Okta](#okta-set-up-guide) and [Azure AD](#azure-ad-set-up-guide), and we have plans to support OneLogin soon. Each link includes specific set up instructions for that IdP. You should read the [features](#features) section of this page to understand which features of SCIM Segment supports.
+Segment officially supports [Okta](#okta-set-up-guide), [Azure AD](#azure-ad-set-up-guide), and [OneLogin](#oneLogin-set-up-guide). Each link includes specific set up instructions for that IdP. You should read the [features](#features) section of this page to understand which features of SCIM Segment supports.
 
 You may still be able to use SCIM with another Identity Provider (IdP) by adapting the following instructions.
 

vale-styles/Vocab/Docs/accept.txt

@@ -1,59 +1,60 @@
+(?:C|c)annonical
+(?:G|g)tag
+(?:K|k)laviyo
+(?:L|l)ookback
+(?:P|p)ageviews?\b
+(?:P|p)endo
+(?:P|p)ostgres
+(?:R|r)emarketing
+(?:U|u)nlinks?\b
+(?:U|u)nmaps?\b
+(?:U|u)rls?\b
+Adwords
 allowlist
 Appboy
 blocklist
 boolean
+Chargebee
 CloudFront
 Cocoapods
+Dev
+Doubleclick
+Friendbuy
+ga
+gmail
 Gradle
-HTTP
 http
-HTTPS
+HTTP
 https
+HTTPS
+Hubspot
+ios
+iOS
 Javadoc
 Javadocs
 Javascript
 Kameleoon
 Kissmetrics
+Lightbox
 Littledata
-Middleware
+measurability
 middleware
+Middleware
 Mixpanel
+namespace
 Okta
+Omnichannel
+Optimizely
 performant
 Preact
 Shopify
+Smartly
+Subnet
 Totango
 Twilio
+upsert
 Vero
+viewability
 WebKit
 Wootric
-Zendesk
-iOS
-ios
-Dev
-ga
-(?:G|g)tag
-(?:P|p)ageviews?\b
-(?:R|r)emarketing
-Doubleclick
-(?:C|c)annonical
-(?:U|u)rls?\b
-Optimizely
-Omnichannel
-namespace
-upsert
-viewability
-measurability
-Lightbox
-gmail
-(?:P|p)endo
-(?:K|k)laviyo
-(?:U|u)nmaps?\b
-(?:U|u)nlinks?\b
-(?:P|p)ostgres
-Smartly
-Hubspot
-Friendbuy
-Chargebee
-(?:L|l)ookback
-Subnet
+Zendesk