Merge branch 'master' into DOC-242_dest-action-filters

Author: markzegarelli

src/_data/sidenav/main.yml

@@ -24,21 +24,21 @@ sections:
   - path: /guides
     title: An introduction to Segment
   - path: /guides/intro-impl
-    title: Segment developer overview
+    title: Segment for developers
   - path: /guides/intro-user
-    title: Segment data user overview
+    title: Segment for data users
   - path: /guides/intro-admin
-    title: Segment workspace admin overview
+    title: Segment for workspace admins
   - path: /guides/filtering-data
     title: Filtering your Segment data
   - path: /guides/duplicate-data
-    title: How does Segment handle duplicate data?
+    title: Handling duplicate data
   - path: /guides/ignore-bots
-    title: How can I ignore internet bots?
+    title: Ignoring internet bots
   - path: /guides/segment-vs-tag-managers
-    title: What is the difference between Segment and tag managers?
+    title: Segment vs. tag managers
   - path: /guides/what-is-replay
-    title: What is Replay?
+    title: Replay
 
   - section_title: How To Guides
     slug: guides/how-to-guides

src/connections/destinations/catalog/actions-amplitude/index.md

@@ -45,6 +45,9 @@ Session tracking is only available when using Segment's new libraries: [Analytic
 Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
 
 
+### Device ID Mappings
+The Amplitude destination requires that each event include either a Device ID or a User ID. If a User ID isn't present, Amplitude uses the a Device ID, and vice versa, if a Device ID isn't present, Amplitude uses the User ID. By default, Segment maps the Segment property `context.device.id` to the Amplitude property `Device ID`. If `context.device.id` isn't available, Segment maps the property `anonymousId` to the Amplitude `Device ID`. This is indicated by the following text in the Device ID field: `coalesce(` `context.device.id` `anonymousId` `)`. 
+
 ### Enable session tracking for Analytics.js 2.0
 
 The session tracking is automatically enabled on Javascript sources.

src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md

@@ -3,7 +3,7 @@ title: Upgrade to Analytics.js 2.0
 strat: ajs
 ---
 
-Analytics.js 2.0 is fully backward compatible with Analytics.js Classic. To upgrade your sources, follow the manual upgrade steps below, or see the schedule for automatic migration. As with all upgrades, Segment recommends that you start development on a non-production source to test the upgrade process and outcome, prior to upgrading your production sources.
+Analytics.js 2.0 is fully backward compatible with Analytics.js Classic when using the default Segment snippet. To upgrade your sources, follow the manual upgrade steps below, or see the schedule for automatic migration. As with all upgrades, Segment recommends that you start development on a non-production source to test the upgrade process and outcome, prior to upgrading your production sources.
 
 ## Manual upgrade
 

src/guides/duplicate-data.md

@@ -1,5 +1,5 @@
 ---
-title: How does Segment handle duplicate data?
+title: Handling duplicate data
 ---
 
 Segment has a special de-duplication service that sits just behind the `api.segment.com` endpoint, and attempts to drop duplicate data. However, that de-duplication service has to hold the entire set of events in memory in order to know whether or not it has seen that event already. Segment stores 24 hours worth of event `message_id`s. This means Segment can de-duplicate any data that appears within a 24 hour rolling window.

src/guides/ignore-bots.md

@@ -1,20 +1,20 @@
 ---
-title: How can I ignore internet bots?
+title: Internet bots
 ---
 
-## But wait, I don't even know what a bot is!
+## What's a bot?
 
 If you stumbled onto this page by accident and don't know what a bot is or are just curious to learn more, the following Wikipedia article provides an awesome summary: [https://en.wikipedia.org/wiki/Internet\_bot](https://en.wikipedia.org/wiki/Internet_bot).
 
 Surprisingly, more than half of all web traffic is made up of bots. While a fraction of them are good bots with a regulated pattern, and therefore beneficial to all online businesses, the majority of them have malicious intents and are mostly unregulated.
 
-## Got it! So is it possible to ignore bad bots?
+## Is it possible to ignore bad bots?
 
-Now that we're level-set on what a bot is, unfortunately Segment does not offer any out-of-the-box feature to filter/ignore bot traffic.
+Segment doesn't offer any out-of-the-box feature to filter or ignore bot traffic.
 
 As such, you generally have two options:
 
-**Handle the filtering at a destination-level:** some of our destination partners, [like Mixpanel](https://help.mixpanel.com/hc/en-us/articles/115004567946-Exclude-Bot-Activity-Web-JavaScript-), filter bots automatically. Whereas others [such as Hubspot](https://knowledge.hubspot.com/getting-started-with-hubspot-v2/how-to-filter-out-traffic-from-your-website-analytics) allow you to set up bot filtering manually. The advantage of filtering bots at a destination level is that it allows you to implement a robust, easy-to-maintain solution. However, as it pertains to Segment, the downside is that bot traffic will _still_ make it to Segment, [affecting your MTU count.](https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/#how-does-segment-calculate-mtus)
+**Handle the filtering at a destination-level:** Some of Segment's destination partners, [like Mixpanel](https://help.mixpanel.com/hc/en-us/articles/115004567946-Exclude-Bot-Activity-Web-JavaScript-), filter bots automatically. Whereas others [such as Hubspot](https://knowledge.hubspot.com/getting-started-with-hubspot-v2/how-to-filter-out-traffic-from-your-website-analytics) allow you to set up bot filtering manually. The advantage of filtering bots at a destination level is that it allows you to implement a robust, easy-to-maintain solution. However, as it pertains to Segment, the downside is that bot traffic will _still_ make it to Segment, [affecting your MTU count.](https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/#how-does-segment-calculate-mtus)
 
 **Write custom logic that suppresses bot activity from being sent to Segment:** if you want to prevent bot traffic from making it to Segment in the first place, another option is to write your own custom code. The logic, in pseudo-code, would look something like this if you know a particular characteristic of the bot traffic to filter out, such as the userAgent:
 
@@ -25,17 +25,17 @@ if ! window.navigator.userAgent in robots
   analytics.track
 ```
 
-The benefit here of course is that you would be able to limit the impact that bots have on your MTU count. However, on the flip side, it's much harder to implement and maintain a custom filter.
+The benefit here is that you would be able to limit the impact that bots have on your MTU count. On the flip side, it's much harder to implement and maintain a custom filter.
 
-## If we see a massive MTU spike because of bots, can we apply for a refund?
+## If I see a massive MTU spike because of bots, can I apply for a refund?
 
-As a matter of policy, we typically do not provide refunds for bot-related MTU spikes, as bot traffic is out of our control. However for extenuating circumstances, [you can petition for a refund](https://segment.com/contact/billing), assuming you're able to provide proof of the bot's effect.
+As a matter of policy, Segment doesn't provide refunds for bot-related MTU spikes, as bot traffic is out of Segment's control. However for extenuating circumstances, [you can petition for a refund](https://segment.com/contact/billing), assuming you're able to provide proof of the bot's effect.
 
-## I'm seeing a lot of browser traffic from Boardman; isn't that from Segment?
+## I'm seeing a lot of browser traffic from Boardman; is that from Segment or a bot?
 
-We do indeed use Amazon's hosting services, which are based in Boardman, Oregon. However [many bots also originate from AWS in Boardman as well](https://productforums.google.com/forum/#!topic/webmasters/Ow5baxkjiPI).
+Segment uses Amazon's hosting services, which are based in Boardman, Oregon. However [many bots also originate from AWS in Boardman as well](https://productforums.google.com/forum/#!topic/webmasters/Ow5baxkjiPI).
 
-One way you can confirm whether or not traffic is coming from Segment vs. a bot is to check the userAgent of the inbound call. Ours is:
+One way you can confirm whether or not traffic is coming from Segment vs. a bot is to check the userAgent of the inbound call. Segment's is:
 
 ```js
 'Mozilla/5.0 (' + deviceModel.slice(0, -3) + '; CPU ' + osName + ' ' +

src/guides/intro-admin.md

@@ -1,5 +1,5 @@
 ---
-title: Segment for Workspace Administrators
+title: Segment for workspace administrators
 ---
 
 If your job is to set up or maintain a Segment Workspace for your organization, or assist other people using the Segment Web App, this guide is for you. If you're more interested in Segment implementation details, see the [developer intro guide](/docs/guides/intro-impl/).

src/guides/intro-impl.md

@@ -1,5 +1,5 @@
 ---
-title: Segment for Developers
+title: Segment for developers
 ---
 
 This guide explains all you need to know to get started with your Segment implementation, and directs you to more resources depending on your specific needs.

src/guides/intro-user.md

@@ -1,5 +1,5 @@
 ---
-title: Segment for Data Users
+title: Segment for data users
 ---
 
 If you aren't involved in setting up your Segment implementation, or are just starting to set up Destinations for your organization's workspace, this guide is for you.

src/guides/segment-vs-tag-managers.md

@@ -1,5 +1,5 @@
 ---
-title: What is the difference between Segment and tag managers?
+title: Segment vs. tag managers
 ---
 
 Tag managers, also known as Tag Management Systems (TMS), were a popular solution before the mainstream adoption of mobile apps. They primarily helped Digital Analytics and Online Marketers manage web tags or "beacons" on a website.

src/guides/usage-and-billing/twilio-developer-plan.md

@@ -0,0 +1,66 @@
+---
+title: Twilio Developer Plan
+hidden: true
+---
+
+
+The Twilio Developer Plan allows you to collect and process your data at scale, consolidating your data from up to 3 sources into a single warehouse for complex querying.
+
+## How is this offer different from Segment’s Free Plan?
+
+The Twilio Developer Plan allows for 10,000 Monthly Tracked Users (MTUs), while Segment’s Free Plan limits MTUs to 1,000.
+
+The Twilio Developer Plan is limited to 1 warehouse destination, while all other Segment plans also allow you to send data in real time to more than 300 destinations (all the analytics, marketing, advertising, and A/B testing tools you already use).
+
+|                              | Twilio Developer Plan | Segment Free Plan          |
+| ---------------------------- | --------------------- | -------------------------- |
+| Monthly Tracked Users (MTUs) | 10,000                | 1,000                      |
+| Destinations                 | 1 warehouse           | More than 300 destinations, including the analytics, marketing, advertising, and A/B testing tools you already use |
+
+
+Need more destinations or more MTUs? Upgrade to the [Team Plan](https://segment.com/pricing) for unlimited destinations and scaled MTU pricing.
+
+## How do I qualify for the Twilio Developer Plan?
+
+You must have an active Twilio account to sign up for the Twilio Developer Plan. Active Twilio users can sign up for the Twilio Developer Plan [here](https://www.segment.com/twilio-developer-plan).
+
+## What is a data source?
+
+In Segment, you create a source for each website, app, or cloud-based tool that you need to collect data from.
+
+For more information about data sources, see the [Sources Overview](/docs/connections/sources/).
+
+
+## Warehouse Destinations
+
+A warehouse is a central repository of data collected from one or more sources. This is what commonly comes to mind when you think about a relational database: structured data that fits into rows and columns. Some examples of data warehouse that are available on Segment are [PostgresSQL](/docs/connections/storage/catalog/postgres/), [Snowflake](/docs/connections/storage/catalog/snowflake/), [BigQuery](/docs/connections/storage/catalog/bigquery/), and [Redshift](/docs/connections/storage/catalog/redshift/).
+
+For more information about warehouses, see the [Data Storage Overview](/docs/connections/storage/).
+
+
+## How are Monthly Tracked Users (MTUs) calculated?
+
+Segment counts the number of **unique** `userId` values, and then adds the number of **unique** `anonymousId` values that were not associated with a `userId` during the billing period. Segment counts these IDs across all calls made from all sources in your workspace, over a billing month. Segment counts each user once per month, even if they perform more than one action or are active across more than one source.
+
+For more information about Monthly Tracked Users, see [What is an MTU?](/docs/guides/usage-and-billing/mtus-and-throughput/#what-is-an-mtu).
+
+
+## Common Questions
+
+### What happens if I exceed the 10,000 MTU limit?
+If you exceed the 10,000 MTU limit once in a 6-month period, Segment locks access to your account, but data still flows through Segment. To unlock your account, you can choose from these options:
+
+- **Option 1**: Wait for a full billing cycle (1 month) to go by without any overages. Segment unlocks your account if the MTU numbers reduce on their own.
+- **Option 2**: Upgrade to the [Team plan](https://segment.com/pricing/). This starts a 2-week free trial that gives you 14 days to fix your implementation to decrease the traffic.
+- **Option 3:** Upgrade to a [Business plan](https://segment.com/pricing/). Business plans are custom built for customers and typically have higher MTU limits than Team plans. [Click here](https://segment.com/demo) to schedule time with a Segment representative to see if a Business plan is a good fit for you.
+
+If you exceed the 10,000 MTU limit twice in a 6-month period, Segment locks access to your account and also stops sending and receiving data. You can unlock your account by following option 2 or 3 above to upgrade your plan.
+
+### How do I get more out of Segment?
+
+Segment helps you simplify data collection, personalize user interactions, protect data integrity, and respect user privacy. Explore the [Destinations Catalog](/docs/connections/destinations/catalog/) to see all the tools you can send data to once you get data into Segment.
+
+On Business plans, Segment also offers two add-on products called [Protocols](/docs/protocols/) and [Personas](/docs/personas/).
+
+- **Protocols** helps you automate and scale the [data quality best practices](/docs/protocols/tracking-plan/best-practices/) to improve data quality and trust across your company.
+- **Personas** is a powerful personalization platform that enables you to create unified customer profiles in Segment, to build and enrich audiences, and to activate audiences across marketing tools.