Merge branch 'master' into DOC-48_priv-and-stripe-updates

Author: markzegarelli

netlify.toml

@@ -9,3 +9,8 @@
   from = "/docs/assets/docs.bundle.js"
   to = "/assets/docs.bundle.js"
   status = 200
+
+[[plugins]]
+package = "@algolia/netlify-plugin-crawler"
+  [plugins.inputs]
+  branches = ['DOC-65_Algolia-crawl']

src/_includes/content/integration-foot.md

@@ -40,6 +40,7 @@ When you first create an audience, Personas sends an Identify call for every use
 {% endunless %}
 {% endunless %}
 
+{% unless page.hide-settings == true %}
 ## Settings
 
 Segment lets you change these destination settings from the Segment app without having to touch any code.
@@ -52,7 +53,7 @@ Segment lets you change these destination settings from the Segment app without
 
   {% endunless %}
 {% endfor %}
-
+{% endunless %}
 {% if currentIntegration.previous_names.size > 1 %}
 
 ## Adding {{ currentIntegration.display_name }} to the integrations object

src/_sass/vendors/_premonition.scss

@@ -100,7 +100,10 @@
   }
 
   .content {
-    & > *:not(.header) + * {
+    ul {
+      margin-top: 0px;
+    }
+    & > *:not(.header, ul) + * {
       margin-top: 25px;
     }
 

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

@@ -6,11 +6,11 @@ Our Chameleon destination code is open-source on GitHub if you want to [check it
 
 ## Getting started
 
-When you enable the Segment direct destination on the [Chameleon dashboard](https://prehensile.trychameleon.com/integrations) we will immediately start receiving your app's user and event data collected by Segment.
+When you enable the Segment direct destination on the [Chameleon dashboard](https://app.trychameleon.com/settings/integrations) we will immediately start receiving your app's user and event data collected by Segment.
 
 ## Identify
 
-This helps you target product tours to specific (segments of) users. You can read more about how to segmentations work in [Chameleon's docs](https://docs.trychameleon.com/docs/user-identification)
+This helps you target product tours to specific (segments of) users. You can read more about how to segmentations work in [Chameleon's docs](https://help.trychameleon.com/en/articles/1500422-how-to-create-a-target-audience)
 
 At a minimum we suggest sending us:
  - `email`
@@ -36,7 +36,7 @@ You can send us your app's events for two main reasons:
 1. Signal a `conversion` from a product tour (a user successfully completing the action that they were prompted to take with the tour)
 2. Trigger a specific product tour _(coming soon)_
 
-Product tours should lead to user actions and so offer the option of tagging each Chameleon product tour with a 'conversion event' that helps you track how successful your tour is. We collect data about each tour (users starting, completing, conversions) and send this back to your preferred analytics provider. Read more about the [analytics Chameleon tracks](https://docs.trychameleon.com/docs/analytics).
+Product tours should lead to user actions and so offer the option of tagging each Chameleon product tour with a 'conversion event' that helps you track how successful your tour is. We collect data about each tour (users starting, completing, conversions) and send this back to your preferred analytics provider. Read more about the [analytics Chameleon tracks](https://help.trychameleon.com/en/articles/1226450-what-analytics-does-chameleon-provide).
 
 ## Help
-For more information, refer to [Chameleon's docs](https://docs.trychameleon.com) or [email them](mailto:[email protected]).
+For more information, refer to [Chameleon's docs](https://help.trychameleon.com/) or [email them](mailto:[email protected]).

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

@@ -221,23 +221,23 @@ HubSpot requires that you create and define any custom traits in the HubSpot UI
 
 ### How it works: User-Level Traits and Audiences
 
-Personas sends **User-Level data** to HubSpot to update properties on a user (or `contacts` in HubSpot) record, using an **Identify** call to add a standard  `Property`, and using a **Track** call when a trait is computed or an audience is entered or exited.
+Personas sends **User-Level data** to HubSpot to update properties on a user (or `contacts` in HubSpot) record, using an **Identify** call to add or update a standard  `Property` or when a trait is computed, and a **Track** call when an audience is entered or exited.
 
-- **Computed Traits**: When the trait is first computed, Personas sends an **Identify** call to update the records of all users who are included in the computed trait. Each time the trait is computed after that, Personas sends a **Track** call to HubSpot to update the values. For example, if a computed trait counts the number of times a user visits your pricing page, and the user visits your pricing page five times, Segment first sends an Identify call with the property `pricing_page_visits: 5`, then sends a Track call when this number updates. This appears in HubSpot as a `Property` for the contact.
+- **Computed Traits**: When the trait is first computed, Personas sends an **Identify** call to update the records of all users who are included in the computed trait. Each time the trait is computed after that, Personas sends a **Identify** call to HubSpot to update the values. For example, if a computed trait counts the number of times a user visits your pricing page, and the user visits your pricing page five times, Segment first sends an Identify call with the property `pricing_page_visits: 5`, then sends a Identify call when this number updates. This appears in HubSpot as a `Property` for the contact.
 
-- **Audiences**: Personas uses an Identify call to add the name of the audience to the user’s profile as a trait, and includes a boolean value that indicates if the user is a member of the audience. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property `order_completed_last_30days: true`.  When the user no longer satisfies these criteria (for example when it’s been longer than 30 days since the last purchase), Personas uses a Track call to set that value to `false`.  This appears as a `Property` for the contact in HubSpot.
+- **Audiences**: Personas uses an Identify call to add the name of the audience to the user’s profile as a trait, and includes a boolean value that indicates if the user is a member of the audience. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property `order_completed_last_30days: true`.  When the user no longer satisfies these criteria (for example when it’s been longer than 30 days since the last purchase), Personas uses a Identify call to set that value to `false`.  This appears as a `Property` for the contact in HubSpot. If using a **Track** call, events will be sent for `Audience Entered` or `Audience Exited`.
     - When you first create an audience, Personas sends an Identify call for every user in the audience. Later syncs only update users which were added or removed from the audience since the last sync.
-
+ 
 
 ### How it works: Account-Level Traits and Audiences
 
-Personas sends **Account-Level data** to HubSpot using **Identify** calls to add account traits to the users’ profiles, and **Track** calls to update the trait when it recomputes or when the group enters or exits an audience. Users are added to an account using a single **Group** call, which appends a `groupID` to each user within the account.
+Personas sends **Account-Level data** to HubSpot using **Identify** calls to add account traits to the users’ profiles, and **Identify** calls to update the trait when it recomputes, and will send a **Track** call when the group enters or exits an audience. Users are added to an account using a single **Group** call, which appends a `groupID` to each user within the account.
 
 - **Computed Traits**: When you build computed traits with Account-Level data, Personas computes for each account based on traits or aggregated user behavior. You can then export traits for each account, or for each user within an account. Personas adds a new trait (set as the name of the computed trait) to the user profiles for each user in the group, and sets the value of that computed trait.
 
     For example: Imagine you have a computed trait that counts the number of times that users from a specific company visit your pricing page. If five different users visit your pricing page once each, Personas sends an Identify call with the property `pricing_page_visits: 5` to each user in the group.
 
-- **Audiences**: When you build audiences with Account-Level data, Personas returns a set of accounts, or a set of users that match your criteria. Personas adds the name of the audience to the user’s profile as a trait (both for individual users, and users within an account), and sets a boolean value to indicate if the user is in the audience. For example, if users in an account first complete an order in the last 30 days, Personas sends an Identify call with the property `order_completed_last_30days: true`. When the users in this Account no longer satisfy these criteria (for example if it’s been more than 30 days since the last order), Personas sets that value to `false`.
+- **Audiences**: When you build audiences with Account-Level data, Personas returns a set of accounts, or a set of users that match your criteria. Personas adds the name of the audience to the user’s profile as a trait (both for individual users, and users within an account), and sets a boolean value to indicate if the user is in the audience. For example, if users in an account first complete an order in the last 30 days, Personas sends an Identify call with the property `order_completed_last_30days: true`. When the users in this Account no longer satisfy these criteria (for example if it’s been more than 30 days since the last order), Personas sets that value to `false`. If using a **Track** call, events will be sent for `Audience Entered` or `Audience Exited`.
 
     - When you first create the audience, Personas sends an Identify call for *every user in the account in that audience*. Later syncs only send updates for individual accounts and users which were added or removed since the last sync.
     **Note**: For user-level events or traits, you can specify `None of the users`, `Any users`, or `All users` when you build your audience criteria.
@@ -309,7 +309,7 @@ You can also see this in the contact property history for each user record.
 ## HubSpot Personas Quick Info
 
 - **Personas Destination type**: Event Method (data is delivered to this Destination one-by-one on a realtime basis)
-- **Traits and Audiences created by**: Identify calls add traits and audiences as traits on the user, Track calls update the values.
+- **Traits and Audiences created by**: Identify calls add and update traits and audiences as traits on the user, Track calls send events for `Audience Entered` and `Audience Exited`.
 - **Must create audience_name field before Personas can update those values?**: Yes, you must manually create Contact properties in Hubspot before you send Custom Traits or Audiences.
 - **Audience appears as**: A prose-text version of the audience name (for example, `Order Completed 30 Days: Yes`) where `Yes` indicates that the user is in the audience.
 - **Destination rate limit**: Yes. HubSpot’s rate limit depends on what account tier you have in HubSpot, but is *usually* 100 calls per ten seconds, or 10 per second.

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

@@ -148,6 +148,8 @@ You won't see server-side `traits` appear as super-properties on any events you
 
 For Mixpanel People, it's important to `identify` a user before you call `track`. A `track` without an `identify` won't create a user in Mixpanel People.
 
+If you use Cloud-mode, you must explicitly include the grouping value as an event property for any event you want to analyze using Mixpanel's Group Analytics.
+
 ### Register Super Properties
 
 By default, each trait (i.e. properties in an `identify` call) is registered as a super property. This does not require passing a `userId` in the `identify` call. You can pass a `traits` object by itself and it will still register the traits as super properties.