diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index a8c0617580..2560e9f9fd 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -3,44 +3,44 @@ sections: - section_title: Getting Started section: - path: /getting-started - title: Getting started with Segment + title: Getting Started With Segment - path: /getting-started/01-what-is-segment title: What is Segment? - path: /getting-started/02-simple-install - title: A simple Segment installation + title: A Simple Segment Installation - path: /getting-started/03-planning-full-install - title: Planning a full installation + title: Planning a Full Installation - path: /getting-started/04-full-install - title: A full Segment installation + title: A Full Segment Installation - path: /getting-started/05-data-to-destinations - title: Sending data to destinations + title: Sending Data to Destinations - path: /getting-started/06-testing-debugging - title: Testing and debugging + title: Testing and Debugging - path: /getting-started/whats-next - title: What's next? + title: What's Next - section_title: Guides section: - path: /guides - title: An introduction to Segment + title: An Introduction to Segment - path: /guides/intro-impl - title: Segment for developers + title: For Developers - path: /guides/intro-user - title: Segment for data users + title: For Data Users - path: /guides/intro-admin - title: Segment for workspace admins + title: For Workspace Admins - path: /guides/filtering-data - title: Filtering your Segment data + title: Filtering your Segment Data - path: /guides/duplicate-data - title: Handling duplicate data + title: Handling Duplicate Data - path: /guides/ignore-bots - title: Internet bots + title: Internet Bots - path: /guides/segment-vs-tag-managers - title: Segment vs. tag managers + title: Segment vs. Tag Managers - path: /guides/what-is-replay title: Replay - - section_title: How To Guides + - section_title: How-to Guides slug: guides/how-to-guides menu_icon: read-more section: @@ -78,15 +78,15 @@ sections: slug: guides/usage-and-billing section: - path: /guides/usage-and-billing/account-management - title: Account management + title: Account Management - path: /guides/usage-and-billing/billing - title: Billing and account FAQs + title: Billing and Account FAQs - path: /guides/usage-and-billing/mtus-and-throughput title: 'MTUs, Throughput and Billing' - path: /guides/usage-and-billing/discounts-for-startups-npos - title: Do you offer discounts or coupons? + title: Discounts or Coupons - path: /guides/usage-and-billing/startup-program - title: What is the Segment Startup Program? + title: Segment Startup Program - section_title: Connections section: - path: /connections @@ -95,7 +95,7 @@ sections: slug: connections/spec section: - path: /connections/spec - title: Spec overview + title: Spec Overview - path: /connections/spec/page title: 'Spec: Page' - path: /connections/spec/screen @@ -113,7 +113,7 @@ sections: - path: /connections/spec/native-mobile-spec title: What is the native mobile spec? - path: /connections/spec/mobile-packaging-sdks - title: Packaging SDKs for mobile destinations + title: Packaging SDKs for Mobile Destinations - path: /connections/spec/semantic title: 'Spec: Semantic Events' - path: /connections/spec/b2b-saas @@ -121,41 +121,41 @@ sections: - path: /connections/spec/ecommerce/v2 title: 'Spec: Ecommerce Events' - path: /connections/spec/ecommerce-tracking-plan - title: 'Ecommerce tracking plans' + title: 'Ecommerce Tracking Plans' - path: /connections/spec/video title: Video Spec - path: /connections/spec/best-practices-identify - title: Best practices for identifying users + title: Best Practices for Identifying Users - path: /connections/spec/best-practices-event - title: Best practices for Event calls + title: Best Practices for Event Calls - section_title: Sources slug: connections/sources section: - path: /connections/sources - title: Sources overview + title: Sources Overview - path: /connections/sources/catalog - title: Sources catalog + title: Sources Catalog menu_icon: read-more - path: /connections/sources/debugger title: Using the Source Debugger - path: /connections/sources/about-cloud-sources - title: All about Cloud Sources + title: Cloud Sources - path: /connections/sources/custom-domains - title: Set up a custom domain proxy in Segment + title: Set Up a Custom Domain Proxy in Segment - path: /connections/sources/visual-tagger title: Visual Tagger - section_title: Destinations slug: connections/destinations section: - path: /connections/destinations - title: Destinations overview + title: Destinations Overview # - path: /connections/destinations/actions # title: Destination Actions # uncomment once fully rolled out - path: /connections/destinations/add-destination - title: Add a destination + title: Add a Destination - path: /connections/destinations/catalog - title: Destinations catalog + title: Destinations Catalog menu_icon: read-more - path: /connections/destinations/destination-filters title: Destination Filters @@ -163,79 +163,79 @@ sections: slug: connections/functions section: - path: /connections/functions - title: Functions overview + title: Functions Overview - path: /connections/functions/source-functions title: Source Functions - path: /connections/functions/destination-functions title: Destination Functions - path: /connections/functions/environment - title: Functions environment + title: Functions Environment - path: /connections/functions/usage - title: Functions usage limits + title: Functions Usage Limits - section_title: Storage Destinations slug: connections/storage section: - path: /connections/storage - title: Storage Destinations overview + title: Storage Destinations Overview - path: /connections/storage/catalog - title: Storage Destinations catalog + title: Storage Destinations Catalog menu_icon: read-more - section_title: Segment Data Lakes slug: connections/storage/data-lakes section: - path: /connections/storage/data-lakes - title: Data Lakes overview + title: Data Lakes Overview - path: /connections/storage/catalog/data-lakes - title: Set up Data Lakes + title: Set Up Data Lakes - path: /connections/storage/data-lakes/sync-reports - title: Sync Reports and error reporting + title: Sync Reports and Error Reporting - path: /connections/storage/data-lakes/comparison - title: Data Lakes vs Warehouses + title: Data Lakes vs. Warehouses - section_title: Data Warehouses slug: connections/storage/warehouses section: - path: /connections/storage/warehouses - title: Warehouses overview + title: Warehouse Overview - path: /connections/storage/warehouses/schema - title: Warehouses schemas + title: Warehouse Schemas - path: /connections/storage/warehouses/selective-sync - title: Warehouse selective sync + title: Warehouse Selective Sync - path: /connections/storage/warehouses/health - title: Warehouse Health dashboards + title: Warehouse Health Dashboards - path: /connections/storage/warehouses/choose-warehouse - title: Choosing a warehouse + title: Choosing a Warehouse - path: /connections/storage/warehouses/faq title: Warehouse FAQs - path: /connections/storage/warehouses/add-warehouse-users - title: How do you add users? + title: Adding Warehouse Users - path: /connections/storage/warehouses/warehouse-errors - title: What does my warehouse error mean? + title: Warehouse Errors - path: /connections/storage/warehouses/redshift-faq - title: Redshift cluster and Redshift connector limitations + title: Redshift Cluster and Redshift Connector Limitations - path: /connections/storage/warehouses/redshift-tuning - title: How do I speed up my redshift queries? + title: Speeding Up Redshift Queries - path: /connections/test-connections - title: Testing connections + title: Testing Connections - path: /connections/data-export-options - title: Data export options + title: Data Export Options - path: /connections/destination-data-control title: Using Schema Controls - path: /connections/event-delivery title: Event Delivery - path: /connections/find-writekey - title: Locate your Write Key + title: Locate Your Write Key - path: /connections/integration_error_codes - title: Integration error codes + title: Integration Error Codes - path: /connections/schema-unique-limits - title: Segment Schema limits + title: Segment Schema Limits - path: /connections/rate-limits - title: Rate limits and SLA + title: Rate Limits and SLA - path: /connections/data-residency - title: Data residency + title: Data Residency - section_title: Personas section: - path: /personas - title: Personas overview + title: Personas Overview - path: /personas/quickstart title: Personas Quickstart Guide - section_title: Personas Identity Resolution @@ -252,9 +252,9 @@ sections: - path: /personas/identity-resolution/identity-resolution-settings title: Settings - path: /personas/identity-resolution/ecommerce-example - title: E-Commerce example + title: E-Commerce Example - path: /personas/identity-resolution/personas-space-set-up - title: Personas Space set up + title: Personas Space Set Up - path: /personas/computed-traits title: Computed Traits - path: /personas/sql-traits @@ -265,7 +265,7 @@ sections: - path: /personas/audiences title: Overview - path: /personas/audiences/account-audiences - title: Account-level Audiences + title: Account-Level Audiences - section_title: Journeys slug: /personas/journeys section: @@ -282,7 +282,7 @@ sections: - path: /personas/journeys/key-terms title: Journeys Glossary - path: /personas/using-personas-data - title: Using Personas data + title: Using Personas Data - path: /personas/warehouses title: Personas and Warehouses - path: /personas/profile-api @@ -296,7 +296,7 @@ sections: - section_title: Privacy section: - path: /privacy - title: Privacy overview + title: Privacy Overview - section_title: Privacy Portal slug: protocols/portal expanded: true @@ -310,42 +310,42 @@ sections: expanded: true section: - path: /privacy/complying-with-the-gdpr - title: Complying with GDPR + title: Complying With GDPR - path: /privacy/user-deletion-and-suppression - title: User deletion and suppression + title: User Deletion and Suppression - path: /privacy/faq title: Privacy FAQs - section_title: Protocols section: - path: /protocols - title: Protocols overview + title: Protocols Overview - section_title: Create a Tracking Plan slug: protocols/tracking-plan section: - path: /protocols/tracking-plan/best-practices - title: Data collection best practices + title: Data Collection Best Practices - path: /protocols/tracking-plan/create title: The Tracking Plan - path: /protocols/tracking-plan/libraries title: Tracking Plan Libraries - - section_title: Validate with violations + - section_title: Validate With Violations slug: protocols/validate section: - path: /protocols/validate/connect-sources - title: Connect Sources to your Tracking Plan + title: Connect Sources to Your Tracking Plan - path: /protocols/validate/review-violations - title: Review and resolve event violations + title: Review and Resolve Event Violations - path: /protocols/validate/forward-violations - title: Forward violations - - section_title: Enforce with data controls + title: Forward Violations + - section_title: Enforce With Data Controls slug: protocols/enforce section: - path: /protocols/enforce/schema-configuration - title: Customize your schema controls + title: Customize Your Schema Controls - path: /protocols/enforce/forward-blocked-events - title: Forward blocked events + title: Forward Blocked Events - path: /protocols/transform - title: Transform to fix bad data + title: Transform to Fix Bad Data - section_title: Protocols Extensions slug: protocols/apis-and-extensions section: @@ -360,31 +360,31 @@ sections: - section_title: Segment App section: - path: /segment-app - title: Introducing the Segment Web App + title: Segment Web App - path: /segment-app/workspace-home title: Workspace Home - section_title: Access Management slug: segment-app/iam section: - path: /segment-app/iam - title: Identity & Access Management overview + title: Identity & Access Management Overview - path: /segment-app/iam/concepts title: Concepts - path: /segment-app/iam/roles title: Roles - path: /segment-app/iam/membership - title: Manage workspace members + title: Manage Workspace Access - path: /segment-app/iam/labels - title: Label-based access control + title: Label-Based Access Control - path: /segment-app/iam/audit-trail - title: Audit trail + title: Audit Trail - path: /segment-app/iam/sso title: Single Sign On - path: /segment-app/iam/mfa title: Multi-Factor Authentication (MFA) - path: /segment-app/iam/secure-password - title: Picking a secure password + title: Picking a Secure Password - path: /segment-app/set-up-envs - title: Prod and Testing environments in Segment + title: Prod and Testing Environments in Segment - path: /segment-app/verify-email-address - title: How do I verify my email address? + title: Verifying Your Email Address diff --git a/src/connections/data-export-options.md b/src/connections/data-export-options.md index 7f9b459c5e..91e409f254 100644 --- a/src/connections/data-export-options.md +++ b/src/connections/data-export-options.md @@ -1,5 +1,5 @@ --- -title: "Data export options" +title: "Data Export Options" --- There are a few ways to export your Segment data. Segment [Business customers](https://segment.com/business) have the most data flexibility, but our self-service customers also have options. diff --git a/src/connections/data-residency.md b/src/connections/data-residency.md index 7a351b4a9a..3f14fee5fd 100644 --- a/src/connections/data-residency.md +++ b/src/connections/data-residency.md @@ -1,5 +1,5 @@ --- -title: Data residency +title: Data Residency --- {% include content/plan-grid.md name="data-residency" %} diff --git a/src/connections/destinations/add-destination.md b/src/connections/destinations/add-destination.md index 39a104209a..55cd8dda9e 100644 --- a/src/connections/destinations/add-destination.md +++ b/src/connections/destinations/add-destination.md @@ -1,5 +1,5 @@ --- -title: Sending Segment data to destinations +title: Sending Segment Data to Destinations --- You've decided how to format your data, and collected it using [Segment Sources](/docs/connections/sources/). Now what do you do with it? You send the data to Destinations! @@ -114,11 +114,11 @@ To connect a source to more than one instance of a destination in the Segment we You must give each instance of the destination connected to the same source a unique name. Segment recommends that you use descriptive names rather than numbers, so other Segment users can understand which Segment destinations are linked to which tool instances. For example, you might use "Amplitude North America" and "Amplitude South America", instead of "Amplitude 1" and "Amplitude 2". You can edit the destination instance name at any time. -If you added the first instance of your destination before multi-instance destinations became available, that instance is automatically named for the destination with no other identifiers, for example "Amplitude". +If you added the first instance of your destination before multi-instance destinations became available, that instance is automatically named for the destination with no other identifiers, for example "Amplitude". Some destinations do not support having multiple instances connected to the same source. In that case, the option to add a second instance of that destination does not appear. -You can create unique destination filters for each destination instance connected to the same source. +You can create unique destination filters for each destination instance connected to the same source. ### Connect to more than one instance of a destination using the Config API @@ -161,7 +161,7 @@ In this example: - Events sent with this `Mixpanel` setting are **not** sent to instances of Mixpanel. - Events sent to any Adobe Analytics destinations with this `Adobe Analytics` setting use the same `marketingCloudVisitorId` value specified. -You can not use the [integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object) to send data to individual destination instances. +You can not use the [integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object) to send data to individual destination instances. ### Multi-instance compatible destinations diff --git a/src/connections/functions/environment.md b/src/connections/functions/environment.md index 0f3a6c077d..a83403078c 100644 --- a/src/connections/functions/environment.md +++ b/src/connections/functions/environment.md @@ -1,5 +1,5 @@ --- -title: The Functions editing environment +title: The Functions Editing Environment --- diff --git a/src/connections/schema-unique-limits.md b/src/connections/schema-unique-limits.md index 4f37ca477c..e13d079c84 100644 --- a/src/connections/schema-unique-limits.md +++ b/src/connections/schema-unique-limits.md @@ -1,5 +1,5 @@ --- -title: Segment Schema limits +title: Segment Schema Limits --- **How many unique events can be logged in my Segment Schema table?** diff --git a/src/connections/sources/about-cloud-sources.md b/src/connections/sources/about-cloud-sources.md index 4c846830be..9fdd4f0fac 100644 --- a/src/connections/sources/about-cloud-sources.md +++ b/src/connections/sources/about-cloud-sources.md @@ -1,5 +1,5 @@ --- -title: All about Cloud Sources +title: Cloud Sources redirect_from: - '/connections/sources/what-are-cloud-sources/' - '/connections/sources/cloud-source-data/' diff --git a/src/connections/spec/best-practices-identify.md b/src/connections/spec/best-practices-identify.md index 92310dd84a..41fa0ad25c 100644 --- a/src/connections/spec/best-practices-identify.md +++ b/src/connections/spec/best-practices-identify.md @@ -1,5 +1,5 @@ --- -title: Best practices in identifying users +title: Best Practices for Identifying Users redirect_from: '/guides/how-to-guides/best-practices-identify/' --- diff --git a/src/connections/spec/mobile-packaging-sdks.md b/src/connections/spec/mobile-packaging-sdks.md index 4da0827e2d..7ab69804f4 100644 --- a/src/connections/spec/mobile-packaging-sdks.md +++ b/src/connections/spec/mobile-packaging-sdks.md @@ -1,5 +1,5 @@ --- -title: Packaging SDKs for mobile destinations +title: Packaging SDKs for Mobile Destinations --- When it comes to Mobile SDKs, we know that minimizing size and complexity is a priority for our customers. That's why our core Mobile SDKs are small and offload as much work as possible in handling destinations to our servers. When you install our light-weight SDK, you have access to our entire suite of server-side destinations. diff --git a/src/connections/storage/warehouses/add-warehouse-users.md b/src/connections/storage/warehouses/add-warehouse-users.md index 42dcad4cb0..821128f910 100644 --- a/src/connections/storage/warehouses/add-warehouse-users.md +++ b/src/connections/storage/warehouses/add-warehouse-users.md @@ -1,5 +1,5 @@ --- -title: How do you add warehouse users? +title: Adding Warehouse Users redirect_from: '/connections/warehouses/add-warehouse-users/' --- diff --git a/src/connections/storage/warehouses/redshift-tuning.md b/src/connections/storage/warehouses/redshift-tuning.md index d3ec69ff05..6b7dd94567 100644 --- a/src/connections/storage/warehouses/redshift-tuning.md +++ b/src/connections/storage/warehouses/redshift-tuning.md @@ -1,5 +1,5 @@ --- -title: How do I speed up my Redshift queries? +title: Speeding Up Redshift Queries redirect_from: '/connections/warehouses/redshift-tuning/' --- diff --git a/src/connections/storage/warehouses/warehouse-errors.md b/src/connections/storage/warehouses/warehouse-errors.md index 4406f6eb6c..81fbdc5386 100644 --- a/src/connections/storage/warehouses/warehouse-errors.md +++ b/src/connections/storage/warehouses/warehouse-errors.md @@ -1,5 +1,5 @@ --- -title: "What does my warehouse error mean?" +title: "Warehouse Errors" redirect_from: '/connections/warehouses/warehouse-errors/' --- diff --git a/src/connections/test-connections.md b/src/connections/test-connections.md index f525783406..a0ad460e84 100644 --- a/src/connections/test-connections.md +++ b/src/connections/test-connections.md @@ -1,5 +1,5 @@ --- -title: "Testing connections" +title: "Testing Connections" --- diff --git a/src/getting-started/02-simple-install.md b/src/getting-started/02-simple-install.md index dca866f6df..8330bd3ddf 100644 --- a/src/getting-started/02-simple-install.md +++ b/src/getting-started/02-simple-install.md @@ -1,5 +1,5 @@ --- -title: A simple Segment installation +title: A Simple Segment Installation --- diff --git a/src/getting-started/03-planning-full-install.md b/src/getting-started/03-planning-full-install.md index fefd39a1df..068cb0d33e 100644 --- a/src/getting-started/03-planning-full-install.md +++ b/src/getting-started/03-planning-full-install.md @@ -1,5 +1,5 @@ --- -title: Planning a full installation +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: diff --git a/src/getting-started/04-full-install.md b/src/getting-started/04-full-install.md index 25be13fd94..d400d1e420 100644 --- a/src/getting-started/04-full-install.md +++ b/src/getting-started/04-full-install.md @@ -1,5 +1,5 @@ --- -title: A full Segment implementation +title: A Full Segment Implementation related: - "/connections/spec/best-practices-event/" - "/connections/spec/best-practices-identify/" diff --git a/src/getting-started/index.md b/src/getting-started/index.md index 7b4c33b5e8..7abb957bd1 100644 --- a/src/getting-started/index.md +++ b/src/getting-started/index.md @@ -1,5 +1,5 @@ --- -title: Getting Started with Segment +title: Getting Started With Segment --- diff --git a/src/getting-started/whats-next.md b/src/getting-started/whats-next.md index cb853c5ace..60b568d763 100644 --- a/src/getting-started/whats-next.md +++ b/src/getting-started/whats-next.md @@ -1,5 +1,5 @@ --- -title: What's next? +title: What's Next --- You're just getting started with Segment, but there's so much more to explore! diff --git a/src/guides/duplicate-data.md b/src/guides/duplicate-data.md index 06edef3ddf..ab9c88b4df 100644 --- a/src/guides/duplicate-data.md +++ b/src/guides/duplicate-data.md @@ -1,5 +1,5 @@ --- -title: Handling 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. diff --git a/src/guides/ignore-bots.md b/src/guides/ignore-bots.md index ed680fd785..231c2989fc 100644 --- a/src/guides/ignore-bots.md +++ b/src/guides/ignore-bots.md @@ -1,5 +1,5 @@ --- -title: Internet bots +title: Internet Bots --- ## What's a bot? diff --git a/src/guides/intro-admin.md b/src/guides/intro-admin.md index 0408c4340e..f8cf7a6965 100644 --- a/src/guides/intro-admin.md +++ b/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/). diff --git a/src/guides/intro-impl.md b/src/guides/intro-impl.md index 3071056f8d..66edb29cf0 100644 --- a/src/guides/intro-impl.md +++ b/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. diff --git a/src/guides/intro-user.md b/src/guides/intro-user.md index b95f84ebc3..dbff29ac80 100644 --- a/src/guides/intro-user.md +++ b/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. diff --git a/src/guides/segment-vs-tag-managers.md b/src/guides/segment-vs-tag-managers.md index ce741d7d11..7159473388 100644 --- a/src/guides/segment-vs-tag-managers.md +++ b/src/guides/segment-vs-tag-managers.md @@ -1,5 +1,5 @@ --- -title: Segment vs. 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. diff --git a/src/guides/usage-and-billing/discounts-for-startups-npos.md b/src/guides/usage-and-billing/discounts-for-startups-npos.md index 86a3655816..bff2432505 100644 --- a/src/guides/usage-and-billing/discounts-for-startups-npos.md +++ b/src/guides/usage-and-billing/discounts-for-startups-npos.md @@ -1,8 +1,8 @@ --- -title: Do you offer discounts or coupons? +title: Discounts or Coupons --- -We do! Segment currently offers coupons on an ongoing basis for: +Segment currently offers coupons on an ongoing basis for: 1. Early-stage startups 2. Participants and alumni of our Accelerator partners diff --git a/src/guides/usage-and-billing/startup-program.md b/src/guides/usage-and-billing/startup-program.md index 4bcb8b2d8f..1ced190e24 100644 --- a/src/guides/usage-and-billing/startup-program.md +++ b/src/guides/usage-and-billing/startup-program.md @@ -1,5 +1,5 @@ --- -title: What is the Segment Startup Program? +title: Segment Startup Program --- Segment offers a **Startup Program** to enable early startups to track data correctly and easily test the marketing and analytics tools necessary to grow their business. The program is open to any early-stage startup that meets the following eligibility requirements: diff --git a/src/segment-app/verify-email-address.md b/src/segment-app/verify-email-address.md index f100baabe5..1770288c41 100644 --- a/src/segment-app/verify-email-address.md +++ b/src/segment-app/verify-email-address.md @@ -1,5 +1,5 @@ --- -title: "How do I verify my email address?" +title: "Verifying Your Email Address" --- Before you can use your Segment account, you first need to verify your email address. We automatically send a verification message to the address you used to sign, but you can re-send the verification email if you didn't receive it.