Merge pull request #457 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/_data/sidenav/engage.yml

@@ -85,10 +85,10 @@ sections:
   section:
   - path: '/engage/analytics'
     title: Analytics Overview
-  - path: '/engage/analytics/message-events'
-    title: Message Events
-  # - path: '/engage/analytics/custom-events'
-  #   title: Custom Events
+# - path: '/engage/analytics/message-events'
+#   title: Message Events
+# - path: '/engage/analytics/custom-events'
+#   title: Custom Events
 # - section_title: Settings
 #   section:
 #   - path: '/engage/settings/messaging-settings'
@@ -112,4 +112,4 @@ sections:
 #   - path: '/engage/settings/labels'
 #     title: Labels
 path: '/engage/contact'
-title: Support
+title: Support

src/_includes/content/destination-dossier.html

@@ -43,7 +43,12 @@
 <h6>Destination Info</h6>
 <ul class="qi">
   {% if destMethods.size > 0 %}<li>Accepts {% for method in destMethods%}{% if destMethods.size == 1 %}{{method}} calls.{% else %}{% unless forloop.last == true %}{{method}}, {% endunless %}{% if forloop.last == true%}and {{method}} calls{%endif%}{% endif %}{% endfor %}</li>{% endif %}
-  <li>Referred to as <strong>{{previous_names | join: '</strong>, or <strong>' }}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a></li>
+  {% if previous_names.size == 1 or components.size == 0 %}
+    <li>Refer to it as <strong>{{previous_names | join: '</strong>, or <strong>' }}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a></li>
+  {% else %}
+   {% if connectionModes.cloud.web == true or connectionModes.cloud.mobile == true or connectionModes.cloud.server == true %} <li>In Cloud-mode, refer to it as <strong>{{previous_names | join: '</strong>, or <strong>' }}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a></li>{%endif%}
+   {% if connectionModes.device.web == true or connectionModes.device.mobile == true or connectionModes.device.server == true %} <li>In Device-mode, refer to it as <strong>{{previous_names | first}}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a> </li>{%endif%}
+  {% endif %}
   {% if destinationInfo.status == "PUBLIC_BETA" %}<li>This destination is in <span class="release-pill">Beta</span></li>{% endif %}
 </ul>
 {% if components.size > 0%}

src/_includes/content/destination-footer.md

@@ -46,19 +46,7 @@ Segment lets you change these destination settings from the Segment app without
 {% endunless %}
 {% if currentIntegration.previous_names.size > 1 %}
 
-{% unless page.hide-integrations-object == true %}
-## Adding {{ currentIntegration.display_name }} to the integrations object
 
-To add {{ currentIntegration.display_name }} to the `integrations` JSON object (for example, [to filter data from a specific source](/docs/guides/filtering-data/#filtering-with-the-integrations-object)), use one of the following valid names for this integration:
-{% if page.name-override %}
-{% assign currentIntegration = site.data.catalog.overrides.items | where: "slug", currentSlug | first %}
-{% endif %}
-
-{% for valid_name in currentIntegration.previous_names %}
-- {{ valid_name }}
-{% endfor %}
-
-{% endunless %}
 {% endif %}
 
 {% endif %}

src/connections/destinations/catalog/algolia-insights/index.md

@@ -1,7 +1,6 @@
 ---
 title: Algolia Insights Destination
 rewrite: true
-layout: dest-test
 beta: true
 redirect_from: '/connections/destinations/catalog/algolia/'
 id: 5d373a350abf930001a6b70f

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

@@ -85,6 +85,16 @@ analytics.group("groupId123", {
 
 Segment sends Group calls to Variance as an `Account` if you've chosen the "Group" Account Mapping method during setup.
 
+### Alias
+
+If you're not familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like this:
+
+```js
+analytics.alias('123456')
+```
+
+If there is an existing user with that `userId` in Variance that matches the `previousId` passed with the alias, that user will be merged into the "123456" user identified in the alias. If there is only one user with the `previousId` and no user with the `userId`, that user will have their Variance `externalId` updated to match the current `userId` passed in the alias.
+
 ## Account Mapping
 
 Variance offers several ways to map your users to accounts or companies, including the following.

src/connections/spec/ecommerce-tracking-plan.md

@@ -189,6 +189,4 @@ Aside from funnel health, having these key pieces of customer data gives compani
 
 Without taking this critical step of mapping out key customer events, businesses often spend too much time revisiting their data model or analyzing impartial data sets. Instead they could spend that time understanding and addressing customers' needs.
 
-_Want to get started immediately?_ [Download the e-commerce tracking plan template](https://docs.google.com/spreadsheets/d/1TA6qTcDHoZzsG7-C6p5yHGximDxqoNtizguKs7Z0av4/view).
-
 [Talk to a product specialist today](https://segment.com/contact/sales) _about building a clean, high-quality data spec so you can focus on brand engagement and sales growth._

src/engage/analytics/index.md

@@ -2,4 +2,58 @@
 title: Analytics Overview
 layout: engage
 engage: true
----
+---
+
+Twilio Engage provides you with analytics that give you insight into the performance of your [email and SMS campaigns](/docs/engage/campaigns/).
+
+On this page, you'll learn how Engage calculates campaign analytics and which specific messaging events you can view.
+
+## How Engage measures campaign analytics
+
+Understanding when and how Engage measures campaign analytics will help you as you review your analytics reports.
+
+Engage begins tracking campaign performance after you send a campaign. As a result, a campaign's analytics only reflect conversions that occurred after campaign publication. For example, suppose you send an email campaign promoting a sale in your online store. If a customer purchases a qualifying product **before** receiving your campaign, their purchase would not count as a conversion.
+
+Campaign engagement metrics are based only on delivered campaigns. Suppose, for example, you send an email campaign to 20 email addresses but only 10 successfully deliver. Engagement metrics like opens, clicks, and conversions would display as a percentage of the 10 delivered campaigns. In this case, then, if five users opened your campaign, you'd see a 50% total opened rate in the campaign's analytics.
+
+## Access a campaign's analytics
+
+You'll find a campaign's analytics within its parent Journey, using the following instructions:
+
+1. Within your Personas space, select the **Journeys** tab.
+2. From the Journeys table, select the Journey you want to view.
+3. From the Journey overview, select the email or SMS campaign you want to view.
+4. A modal pane appears that displays your campaign's analytics.
+
+## Email messaging events
+
+The following table lists the email campaign events that Engage tracks:
+
+| Event          | Description                                                                                 |
+| -------------- | ------------------------------------------------------------------------------------------- |
+| Sent           | The number of emails campaigns that you sent.                                               |
+| Delivered      | The number of emails campaigns that were accepted by the receiving inbox server.            |
+| Bounced        | The number of email campaigns that bounced instead of being delivered.                      |
+| Total Opened   | The number of times that your email campaigns were opened.                                  |
+| Total Clicked  | The number of times that recipients clicked within your email campaigns.                    |
+| Unique Opened  | The number of unique recipients that opened your email campaigns.                           |
+| Unique Clicked | The number of unique recipients that clicked your email campaign.                           |
+| Unsubscribed   | The number of campaign recipients who chose to unsubscribe from within the email campaigns. |
+| Spam Reported  | The number of recipients who marked your email as spam.                                     |
+| Converted To   | The number of conversions that took place after campaign publication.                       |
+
+SendGrid powers Engage's email campaign event analytics. For more details on email events, view SendGrid's [Marketing Campaigns Statistics Overview](https://docs.sendgrid.com/ui/analytics-and-reporting/marketing-campaigns-stats-overview){:target="_blank"}.
+
+
+## SMS messaging events
+
+The following table lists the SMS campaign events that Engage tracks:
+
+
+| Event       | Description                                                           |
+| ----------- | --------------------------------------------------------------------- |
+| Sent        | The number of SMS campaigns that you sent.                            |
+| Delivered   | The number of SMS campaigns that were accepted by the user's carrier. |
+| Queued      | The number of SMS campaigns queued for delivery, but not yet sent.    |
+| Undelivered | The number of undelivered SMS campaigns.                              |
+| Failed      | The number of SMS campaigns that didn't send.                         |

src/engage/analytics/message-events.md

@@ -2,4 +2,4 @@
 title: Message Events
 layout: engage
 engage: true
----
+---

src/getting-started/03-planning-full-install.md

@@ -2,7 +2,7 @@
 title: Planning a Full Installation
 ---
 
-Now that we've shown you Segment in action, let's step back and think through what a full implementation of Segment for your organization would look like. We know that figuring out what events to track in Segment can feel overwhelming. You should expect this planning process to have the following steps:
+Now that you've seen Segment in action, step back and think through what a full implementation of Segment for your organization would look like. Figuring out what events to track in Segment can feel overwhelming. You should expect this planning process to have the following steps:
 
 <!-- TOC depthFrom:1 depthTo:2 withLinks:1 updateOnSave:1 orderedList:0 -->
 
@@ -36,7 +36,7 @@ Tracking is about learning and taking action. Think about what you want to know
 - How do people discover, start using, and paying for your product?
 - What are the most important steps in a customer's journey?
 
-While it may seem obvious, we highly recommend documenting your high-level business objectives (see [the Goals tab in Google Sheet Tracking Plan](https://docs.google.com/spreadsheets/d/1TA6qTcDHoZzsG7-C6p5yHGximDxqoNtizguKs7Z0av4/view) template). More specifically, ask yourself: what are the measurable business outcomes you want to achieve this year? Do you want to acquire new customers? Generate more new sign-ups, drive more incremental revenue among your current customer base?
+While it may seem obvious, we highly recommend documenting your high-level business objectives. More specifically, ask yourself: what are the measurable business outcomes you want to achieve this year? Do you want to acquire new customers? Generate more new sign-ups, drive more incremental revenue among your current customer base?
 
 The best way to answer this question is to interview stakeholders in your organization who will consume the data.
 
@@ -60,8 +60,6 @@ With your business objectives documented and mapped to user actions, it's time t
 
 When you're first starting out, we recommend that you limit your tracking plan to a few core events, but add lots of properties to provide context about them. We generally see more success with the “less is more” philosophy of tracking data, but you might also decide to take a more liberal “track more and analyze later” approach. Like everything, each alternative has pros and cons that are important to consider especially as it relates to your company's needs.
 
-If you're having trouble starting out, we recommend that you look at our free [Tracking Plan spreadsheet template](https://docs.google.com/spreadsheets/d/1TA6qTcDHoZzsG7-C6p5yHGximDxqoNtizguKs7Z0av4/view) for inspiration. (We'll talk more about Tracking Plans [below](#develop-a-tracking-plan).)
-
 ### Shortcut! Check if a Business Spec meets your needs
 
 Segment maintains several "Business Specs", which are recommendations based on your type of business that give recommendations on what to track, what additional traits or properties to collect, and how to format them. The two most common are the B2B (business-to-business) Spec, Ecommerce Spec, and our Mobile and Video specs.
@@ -100,40 +98,19 @@ Regardless of approach, here are some important best practices to keep in mind:
 
 - **Don't create property keys dynamically:** Avoid creating property names like `"feature_1":"true"`,`"feature_2":"false"` as these are ambiguous and very difficult to analyze
 
-![](/docs/protocols/images/asset_nVdJ3ZyA.png)
+![An image comparing good and bad naming and collection standards](/docs/protocols/images/asset_nVdJ3ZyA.png)
 
 
 Got all that? Great! You're now ready to develop a Tracking Plan.
 
 <!--Source: /docs/protocols/data-quality/whats-a-tracking-plan/ or /docs/protocols/tracking-plan/ -->
 
-## Develop a Tracking Plan
+## Develop a tracking plan
 
-A [tracking plan](https://segment.com/blog/what-is-a-tracking-plan/) clarifies what events to track, where those events live in the code base, and why you're tracking those events (from a business perspective). **A good tracking plan represents the single source of truth about what data you collect, and why.**
+A [tracking plan](https://segment.com/blog/what-is-a-tracking-plan/){:target="_blank"} clarifies what events to track, where those events live in the code base, and why you're tracking those events (from a business perspective). **A good tracking plan represents the single source of truth about what data you collect, and why.**
 
 Your tracking plan is probably maintained in a spreadsheet (unless you use our tracking-plan tool, [Protocols](/docs/protocols/)), and serves as a project management tool to get your organization in agreement about what data to use to make decisions. A tracking plan helps build a shared understanding of the data among marketers, product managers, engineers, analysts, and any other data users.
 
-In the next section, we share how to build a tracking plan from the ground up using a Google Sheet template. Note that you can use any tool to create the tracking plan!
-
-### Using the Tracking Plan Google Sheets template
-
-To help you get started, we developed a Tracking Plan template in [Google Sheets](https://docs.google.com/spreadsheets/d/1TA6qTcDHoZzsG7-C6p5yHGximDxqoNtizguKs7Z0av4/view).
-
-The template includes all of our Business-case ("semantic") Specs (which we mentioned [above](#shortcut-check-if-a-business-spec-meets-your-needs)) as tabs, including [eCommerce](/docs/connections/spec/ecommerce/v2/), [B2B SaaS](/docs/connections/spec/mobile/), [Mobile](/docs/connections/spec/mobile/) and [Video](/docs/connections/spec/video/), and a collection of common properties.
-
-![](images/trackingplans.png)
-
-With your business goals defined, start by defining how you want to track Page/Screen, Identify and Group events. Most customers use [default page tracking](/docs/connections/sources/catalog/libraries/website/javascript/#page) and skip over that tab.
-
-The Identify tab is where you specify which user traits you intend to collect like `first_name`, `last_name`, `email`, etc. Read more about the [identify call below](/docs/protocols/tracking-plan/best-practices/#identify-your-users).
-
-From there, we recommend you specify Track events in the **Track (Custom)** tab. The template includes preexisting events with different numbers of grouped properties (1 Prop Event, 2 Prop Event, etc). While this might be more challenging to work with at first, this structure allows you to use the **Minimize Rows** button at the top to organize and view all events.
-
-Once you complete the tracking plan, you can share the Google Sheet with stakeholders to review, comment, and edit, or simply to share as a reference for implementation.
-
-> success ""
-> **Tip**! If you decide to purchase [Protocols](/docs/protocols/) in the future, you'll be able to upload the tracking plan into Segment [using the Config API](/docs/protocols/apis-and-extensions/#google-sheets-tracking-plan-uploader).
-
 ### Plan your Identify and Group calls
 
 The Identify call updates all records of the user with a set of traits, and so is extremely important for building your understanding of your users. But how do you choose which traits to include?
@@ -188,7 +165,7 @@ An online community, on the other hand, has an entirely different set of actions
 - **Content Produced**
 - **Content Curated**
 
-With these actions tracked, the community can develop metrics around engagement, and understand how users move towards their ultimate conversion events. You can read more in [this article from the online community GrowthHackers](https://segment.com/blog/growthhackers-community-metrics/) about the events they track and why.
+With these actions tracked, the community can develop metrics around engagement, and understand how users move towards their ultimate conversion events. You can read more in [this article from the online community GrowthHackers](https://segment.com/blog/growthhackers-community-metrics/){:target="_blank"} about the events they track and why.
 
 ### Define your Track event properties
 
@@ -234,7 +211,7 @@ Once you have an initial list of the destination tools your organization uses, y
 Additionally, you should check [which connection modes each tool supports](/docs/connections/destinations/cmodes-compare/), so you know ahead of time which destinations may need to be bundled.
 
 > success ""
-> **Tip**: If you know you're looking for a tool for a specific purpose, but haven't chosen one yet, you can also check the [Connection Modes by category page](https://segment.com/docs/connections/destinations/category-compare/) to see which tools might be compatible with the least implementation changes.
+> **Tip**: If you know you're looking for a tool for a specific purpose, but haven't chosen one yet, you can also check the [Connection Modes by category page](https://segment.com/docs/connections/destinations/category-compare/){:target="_blank"} to see which tools might be compatible with the least implementation changes.
 
 
 

src/getting-started/implementation-guide.md

@@ -146,10 +146,8 @@ Segment maintains a number of industry or product-specific specs to help you get
 - [Video](/docs/connections/spec/video/)
 - [Mobile](/docs/connections/spec/mobile/)
 
-Once you're ready to define the events you'd like to track, you can use [this Tracking Plan Template](https://docs.google.com/spreadsheets/d/1TA6qTcDHoZzsG7-C6p5yHGximDxqoNtizguKs7Z0av4/view#gid=1164785081) to help you align your team.
-
 > info "Learn More"
-> - [Data Collection Best Practices](/docs/protocols/tracking-plan/best-practices/#tracking-plan-google-sheets-template)
+> - [Data Collection Best Practices](/docs/protocols/tracking-plan/best-practices/)
 > - [Analytics Academy: How to create a successful data tracking plan](https://segment.com/academy/collecting-data/how-to-create-a-tracking-plan/){:target="_blank"}
 > - [Segment University: Planning your implementation](https://university.segment.com/data-governance-tracking-plans-the-source-of-truth){:target="_blank"}