appx 50 more

Author: forstisabella

src/connections/sources/about-cloud-sources.md

@@ -17,8 +17,8 @@ Event Cloud Sources can export their data both into Segment warehouses, and into
 
 Object Cloud App Sources can export data and import it directly into a Segment warehouse. You *must* have a Segment warehouse enabled before you enable these. From the warehouse, you can analyze your data with SQL, use [Reverse ETL](/docs/connections/reverse-etl) to extract data, or use Engage SQL Traits to build audiences. Some examples of Object Cloud sources are Salesforce (account information), Zendesk (support cases), and Stripe (payments information).
 
-> note ""
-> In the app, data from website, mobile, and server sources can go to a warehouse **or** to destinations. Object Cloud-App Source data can **only** go to Warehouses.
+> info ""
+> You can send data from website, mobile, and server sources to a warehouse **or** to destinations. You can only send object cloud app source data can **only** go to warehouses.
 
 
 ## How do cloud sources work?
@@ -86,7 +86,7 @@ Sometimes, when the sync job fails due to an unhandled error or is mysteriously
 
 In general, we've focused on pulling all of the collections directly related to the customer experience. We do not automatically pull all collections available from a partner API, since many of them aren't relevant to the customer journey. You can see a list of the collections we pull in the docs [for each cloud source](/docs/connections/sources/catalog/#cloud-apps). Each collection reflects a table in your database.
 
-[Contact Segment Product Support](https://segment.com/help/contact) if you need additional data collected, or to change the schema to do the analysis you want. We'd love to know what analysis you're trying to run, what additional data you need, and we'll share with the product team to evaluate.
+[Contact Segment Product Support](https://segment.com/help/contact){:target="_blank”}  if you need additional data collected, or to change the schema to do the analysis you want. We'd love to know what analysis you're trying to run, what additional data you need, and we'll share with the product team to evaluate.
 
 ### What questions can you answer with data from cloud, web, and mobile sources combined in a single warehouse?
 
@@ -103,8 +103,8 @@ Generally, you need intermediate- to advanced SQL experience to explore and anal
 <!-- LR 4.20.2020 I think these have been missing for a long time. :(
 **Entity Relationship Diagrams** The links to the ER (entity relationship) diagrams [in the documentation](/docs/connections/sources/#cloud-app) will really help you fast track your queries. They show the relationship between each table in a particular source, and how each table can be joined based on particular keys. -->
 
-**Joining IDs** As you start to get into joining across different types of sources, you'll need a way to join user IDs. This [help article](/docs/guides/how-to-guides/join-user-profiles/) explains how to do this in detail.
+**Joining IDs**:  As you start to get into joining across different types of sources, you'll need a way to join user IDs. This [help article](/docs/guides/how-to-guides/join-user-profiles/) explains how to do this in detail.
 
 <!-- LR 7.8.2020 - Community shut down pending ??? so hiding this for now **Getting Started Queries** We've created a number of queries for common use cases to help you get started – you can copy and paste them to start querying your data. Find them in the Warehouse section of the [Segment Community](https://segment.forumbee.com/category/warehouses).-->
 
-**Partner Dashboards** Our BI partners at Mode, Looker, BIME, Periscope, and Chartio have created out of the box dashboards that work on top of our source schemas.
+**Partner Dashboards**: Segment's BI partners at Mode, Looker, BIME, Periscope, and Chartio have created out of the box dashboards that work on top of our source schemas.

src/connections/sources/catalog/cloud-apps/google-ads/index.md

@@ -141,7 +141,7 @@ Currency values in Google Ads are in micros, or one millionth of the smallest un
 
 ### Ads
 
-> note "Returning removed ads"
+> info "Returning removed ads"
 > As of April 2022, the Google Ads source uses the Google Ads API, which returns ads with a status of `REMOVED`. Prior to April 2022, `REMOVED` ads were not returned by the default AdWords API. 
 
 

src/connections/sources/catalog/cloud-apps/looker/index.md

@@ -15,14 +15,14 @@ From Segment's end, you will need to create a Looker source, and copy your write
 
 ### Defining Looks
 
-Using this Source, Looker sends Look (query) results into Segment as `identify` calls. Any user trait that you include as a column in your Look will be included as a user trait on these identify call. 
+Using this Source, Looker sends Look (query) results into Segment as Identify calls. Any user trait that you include as a column in your Look will be included as a user trait on these Identify calls. 
 
-> note ""
-> **NOTE:** Segment doesn't support arrays. Segment supports properties that are strings or numbers.
+> warning ""
+> Segment supports properties that are strings or numbers. Segment doesn't support arrays.
 
-When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool overrides the existing trait value with the new one.
+When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (for example, "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool overrides the existing trait value with the new one.
 
-Below is an example of a cohort of users in Looker who have been active on toastmates.com (example website) at least once  in the last 30 days.
+Below is an example of a cohort of users in Looker who have been active on toastmates.com (example website) at least once in the last 30 days.
 
 ![looker-screenshot](images/9c12ebdd99f19383111aceabc0ab5de9.png)
 

src/connections/sources/catalog/cloud-apps/sendgrid/index.md

@@ -54,8 +54,8 @@ The source syncs and warehouse syncs are independent processes. Source runs pull
 
 The SendGrid source's streaming component listens in real time for inbound webhooks from SendGrid's Event Notifications. The source batches these events for upload on your next warehouse flush. **These events only append to your warehouse.**
 
-> note ""
-> **NOTE:** If you don't use SendGrid's marketing features, this will be the only data that Segment receives from SendGrid. There isn't a way to retrieve email event history from SendGrid, so you will only have access to data that Segment collected after you successfully enable this component of the source destination.
+> info ""
+> If you don't use SendGrid's marketing features, this will be the only data that Segment receives from SendGrid. There isn't a way to retrieve email event history from SendGrid, so you will only have access to data that Segment collected after you successfully enabled this integration.
 
 
 ## Collections

src/connections/sources/catalog/cloud-apps/zendesk/index.md

@@ -69,7 +69,7 @@ Collections are the groupings of resources Segment pulls from your source.
 
 In your warehouse, each collection gets its own table. Find below a list of the properties Segment automatically fetches for each collection.
 
-> note "Standard properties"
+> info "This list only includes standard properties"
 > The list in this document includes the standard properties only, but doesn't include _your_ custom fields. (Don't worry, they'll be there in your warehouse.)
 
 ### groups

src/connections/sources/catalog/libraries/mobile/android/index.md

@@ -216,8 +216,8 @@ The Segment API calls include:
 
 ### Identify
 
-> note ""
-> **Good to know**: For any of the different methods described in this doc, you can replace the properties and traits in the code samples with variables that represent the data collected.
+> success ""
+> For any of the different methods described in this doc, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
 Identify calls let you tie a user to their actions, and record traits about them.  It includes a unique User ID and any optional traits you know about them.
 

src/connections/sources/catalog/libraries/mobile/android/quickstart.md

@@ -77,10 +77,10 @@ Ensure that the necessary permissions are declared in your application's `Androi
 
 ## Step 5. Identify Users
 
-> note ""
-> **Good to know**: For any of the different methods described in this quickstart, you can replace the properties and traits in the code samples with variables that represent the data collected.
+> success ""
+> For any of the different methods described in this quickstart, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
-The `identify` method is one of our core API methods. It's how you tie one of your users and their actions to a recognizable userId. It also lets you record traits about the user, like their email, name, account type, etc. You can read more about it in the [identify reference](/docs/connections/sources/catalog/libraries/mobile/android#identify).
+The `identify` method is one of Segment's core API methods. It's how you tie one of your users and their actions to a recognizable userId. It also lets you record traits about the user, like their email, name, account type, etc. You can read more about it in the [identify reference](/docs/connections/sources/catalog/libraries/mobile/android#identify).
 
 When and where you call `identify` depends on how your users are authenticated, but doing it in the `onCreate` method of your [Application](http://developer.android.com/reference/android/app/Application.html) class would be most common, as long as you know who your user is. If your user is still anonymous, you should skip this part and we'll attribute the subsequent events to an `anonymousId` instead.
 

src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/optimizely-full-stack-swift.md

@@ -76,8 +76,8 @@ Segment also handles the following mapping:
 
 `revenue` values should be passed as a Segment `property`. The value should be an integer and represent the value in cents, so, for example, $1 should be represented by `100`.
 
-> note ""
-> **Note:** [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags){:target="_blank”} in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export){:target="_blank”} report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example,  arrays).
+> info "Custom Event Tags are not displayed on the Optimizely results page"
+> Optimizely's [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags){:target="_blank"}, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page. However, these tags are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export){:target="_blank"} report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example, arrays).
 
 Segment defaults to identifying users with their `anonymousId`. Enabling "Use User ID" setting in your Segment dashboard means that only `track` events triggered by identified users are passed downstream to Optimizely. You may optionally fall back to `anonymousId` when `userId` is unavailable by setting `fallbackToAnonymousId` to `true`.
 

src/connections/sources/catalog/libraries/mobile/ios/index.md

@@ -10,20 +10,20 @@ With Analytics-iOS, you can send your data to analytics or marketing tool, witho
 <br />
 <br />
 
-> note ""
-> **Note:** Segment does not currently support tracking of watchkit extensions for the Apple Watch. [Email us](https://segment.com/requests/integrations/) if you're interested in a Watchkit SDK. For now we recommend tracking watch interactions using the iPhone app code.
+> info "Watchkit extensions currently unsupported"
+> Segment does not currently support tracking of watchkit extensions for the Apple Watch. [Email Segment](https://segment.com/requests/integrations/){:target="_blank”}. if you're interested in a Watchkit SDK. For now Segment recommends tracking watch interactions using the iPhone app code.
 
 
 > info "Analytics-Swift"
-> The [Analytics-Swift](/docs/connections/sources/catalog/libraries/mobile/swift/) library is in General Availability. If you'd like to migrate to Analytics-Swift, see the [migration guide](/docs/connections/sources/catalog/libraries/mobile/swift/migration/). Segment's future development efforts concentrate on the new Analytics-Kotlin SDK, and will only ship security updates for the Analytics-Android SDK.
+> The [Analytics-Swift](/docs/connections/sources/catalog/libraries/mobile/swift/){:target="_blank”}. library is in General Availability. If you'd like to migrate to Analytics-Swift, see the [migration guide](/docs/connections/sources/catalog/libraries/mobile/swift/migration/){:target="_blank”}.. Segment's future development efforts concentrate on the new Analytics-Kotlin SDK, and will only ship security updates for the Analytics-Android SDK.
 
 ## Analytics-iOS and Unique Identifiers
 
 One of the most important parts of any analytics platform is the ability to consistently and accurately identify users. To do this, the platform must assign and persist some form of identification on the device, so you can analyze user actions effectively. This is especially important for funnel conversion analysis and retention analysis.
 
 Naturally the Analytics SDK needs a unique ID for each user. To protect end-users' privacy, Apple places restrictions on how these IDs can be generated and used. This section explains Apple's policies, and how Segment generates IDs in compliance with these policies.
 
-Before iOS 5 developers had access to `uniqueIdentifier`, which was a hardware-specific serial number that was consistent across different apps, vendors and installs. Starting with iOS 5, however, [Apple deprecated access to this identifier](https://developer.apple.com/news/?id=3212013a). In iOS 6 Apple introduced the `identifierForVendor` which protects end-users from cross-app identification. In iOS 7 Apple [restricted access to the device's MAC address](http://techcrunch.com/2013/06/14/ios-7-eliminates-mac-address-as-tracking-option-signaling-final-push-towards-apples-own-ad-identifier-technology/), which many developers used as a workaround to get a similar device-specific serial number to replace  `uniqueIdentifier`.
+Before iOS 5 developers had access to `uniqueIdentifier`, which was a hardware-specific serial number that was consistent across different apps, vendors and installs. Starting with iOS 5, however, [Apple deprecated access to this identifier](https://developer.apple.com/news/?id=3212013a){:target="_blank”}.. In iOS 6 Apple introduced the `identifierForVendor` which protects end-users from cross-app identification. In iOS 7 Apple [restricted access to the device's MAC address](http://techcrunch.com/2013/06/14/ios-7-eliminates-mac-address-as-tracking-option-signaling-final-push-towards-apples-own-ad-identifier-technology/){:target="_blank”}., which many developers used as a workaround to get a similar device-specific serial number to replace  `uniqueIdentifier`.
 
 Segment's iOS library supports iOS 7+ by generating a UUID and storing it on disk. This complies with Apple's required privacy policies, maintains compatibility, and also enables correct tracking in situations where multiple people use the same device, since the UUID can be regenerated.
 
@@ -86,8 +86,8 @@ configuration.recordScreenViews = YES; // Enable this to record screen views aut
 {% endcodeexampletab %}
 {% endcodeexample %}
 
-> note ""
-> **Note:** Automatically tracking lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and screen views is optional using initialization config parameters, but highly recommended to hit the ground running with core events! See [below](/docs/connections/sources/catalog/libraries/mobile/ios/quickstart/#step-4-track-actions) for more info!
+> info "Lifecycle event tracking optional, but recommended"
+> Automatically tracking lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and screen views is optional using initialization config parameters, but highly recommended to hit the ground running with core events. See [below](/docs/connections/sources/catalog/libraries/mobile/ios/quickstart/#step-4-track-actions) for more info.
 
 And of course, import the SDK in the files that you use it with:
 {% codeexample %}
@@ -222,12 +222,12 @@ configuration.trackDeepLinks = YES;
 {% endcodeexampletab %}
 {% endcodeexample %}
 
-> note ""
-> **Note:** You still need to call the `continueUserActivity` and `openURL` methods on the analytics client.
+> info ""
+> Even with `trackDeepLinks` set to `YES`, you still must call the `continueUserActivity` and `openURL` methods on the analytics client.
 
 ### Flushing
 
-You can set the number of events that should queue before flushing. Setting this to `1` will send events as they come in (i.e. not send batched events) and will use more battery. `20` by default.
+You can set the number of events that should queue before flushing. Setting this to `1` will send events as they come in (for example, not send batched events) and will use more battery. `20` by default.
 
 {% codeexample %}
 {% codeexampletab Swift %}
@@ -268,8 +268,8 @@ Analytics.shared().flush()
 
 Now that the Segment SDK and any accompanying packaged SDKs are installed, you're ready to collect some data!
 
-> note ""
-> **Good to know**: For any of the methods described in this doc, you can replace the properties and traits in the code samples with variables that represent the data collected.
+> success ""
+> For any of the methods described in this doc, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
 ### Identify
 
@@ -278,8 +278,8 @@ Segment's Identify method lets you tie a user to their actions and record traits
 Segment recommends that you call Identify once when you first create the user's account, and only call it again later when they update their traits or you change them.
 
 
-> note ""
-> **Note:** Segment automatically assigns an `anonymousId` to users before you identify them. The `userId` is what connects anonymous activities across devices (for example, iPhone and iPad).
+> success ""
+> Segment automatically assigns an `anonymousId` to users before you identify them. The `userId` is what connects anonymous activities across devices (for example, iPhone and iPad).
 
 Example `identify` call:
 
@@ -672,8 +672,8 @@ Analytics.shared().track("Product Rated", properties: nil, options: ["integratio
 Destination flags are **case sensitive** and match [the destination's name in the docs](/docs/connections/destinations/) (for example "AdLearn Open Platform", "awe.sm", "MailChimp", etc.).
 
 
-> note ""
-> **Note:** Business level customers can filter track calls from the Segment App from the source schema page. Segment recommends that you use this method when possible, because simpler, and can be updated without any code changes in your app.
+> success ""
+> Business Tier customers can filter Track calls from the Segment App from the source schema page. Segment recommends that you use this method when possible, because it is simpler and can be updated without making any code changes in your app.
 
 
 ### Disabled destinations in the debugger
@@ -835,8 +835,8 @@ configuration.enableAdvertisingTracking = YES;
 The same value for IDFA will used across all (device and cloud-mode) integrations.
 
 
-> note ""
-> **Note:** analytics-ios can continue to collect events without the IDFA until user is prompted and only upon user consent the `advertisingId` field is added to the event payload
+> success ""
+> Analytics-ios can continue to collect events without the IDFA until a user is prompted and only upon user consent the `advertisingId` field is added to the event payload.
 
 Ad-tracking affects two keys under the `context` object of every event: