Skip to content

Commit c76105c

Browse files
Brenden MulliganBrenden Mulligan
Brenden Mulligan
and
Brenden Mulligan
authored
Fixes all "segment.com/help/contact/", protocols, & getting started guide related 404s (segmentio#895)
Co-authored-by: Brenden Mulligan <brenden.mulligan@brendens-mbp.lan>
1 parent 3a6e457 commit c76105c

File tree

17 files changed

+27
-26
lines changed

17 files changed

+27
-26
lines changed

src/_includes/content/warehouse-sync-sched.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Your data will be available in Warehouses between 24 and 48 hours from your first sync. Your warehouse then syncs once, or twice a day depending on your [Segment Plan](segment.com/pricing).
1+
Your data will be available in Warehouses between 24 and 48 hours from your first sync. Your warehouse then syncs once, or twice a day depending on your [Segment Plan](https://segment.com/pricing).
22

33
Segment allows Business Tier (BT) customers to schedule the time and frequency of warehouse data syncs.
44

src/connections/destinations/catalog/personas-display-video-360/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ Once you accept, Google changes your back-end settings to give Segment the acces
8484
To create audiences based on website browsing events, set up the Segment-to-Google cookie-syncing feature. This step allows Segment to retrieve the Google user id using our client-side Analytics.js library.
8585

8686
1. Create a “[Javascript Website](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/)” source in Segment.
87-
2. Follow [the Analytics.js Quickstart guide](https://segment.com/docs/connections/sources/catalog/website/javascript/quickstart/).
87+
2. Follow [the Analytics.js Quickstart guide](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/).
8888
3. In your workspace, click **Catalog**, and search for **DoubleClick Floodlight**.
8989
4. Connect the destination to the source you created in the first step, and leave all settings blank.
9090

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Sometimes, when the sync job fails due to an unhandled error or is mysteriously
8383

8484
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.
8585

86-
Please [let us know](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.
86+
Please [let us know](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.
8787

8888
### What questions can you answer with data from cloud, web, and mobile sources combined in a single warehouse?
8989

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ This tutorial gets you started sending data from your iOS app to Segment. When y
77

88
If you want to dive deeper at any point, check out the [iOS Library Reference](/docs/libraries/ios/).
99

10-
_Note: At the moment Segment does not support tracking watchkit extensions for the Apple watch. [Contact us](segment.com/help/contact) if you're interested in a watchkit SDK. For now we recommend tracking watch interactions using the native iPhone app code._
10+
_Note: At the moment Segment does not support tracking watchkit extensions for the Apple watch. [Contact us](https://segment.com/help/contact) if you're interested in a watchkit SDK. For now we recommend tracking watch interactions using the native iPhone app code._
1111

1212

1313
## Step 1: Install the SDK

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Given the power you have in your downstream tools to create cohorts based on the
7676

7777
Now that you are tracking who your users are, you can work on what they're doing on your website or in your app with a `.track()` call. Tracking customer events lets you learn about your customers, measure the impact of your marketing efforts and product decisions, and proactively engage your customers in a meaningful way that drives sales.
7878

79-
[Read our event tracking guide to learn more about tracking the right events.](/docs/protocols/what-to-track/)
79+
[Read our event tracking guide to learn more about tracking the right events.](/docs/protocols/tracking-plan/best-practices/)
8080

8181
E-commerce businesses, unlike SaaS or consumer apps that optimize for product engagement, focus on directing users down their funnels to a conversion goal, like purchasing a product. To best understand why customers convert, it's important to track and measure all key funnel events.
8282

src/connections/test-connections.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -55,4 +55,4 @@ The Event Tester is only accessible to users with write access in their Segment
5555

5656
**The Event Tester experienced an error when sending my event. Why did this happen?**
5757

58-
If you experience an error, [let us know](segment.com/help/contact/) and we'll help you troubleshoot the issue.
58+
If you experience an error, [let us know](https://segment.com/help/contact/) and we'll help you troubleshoot the issue.

src/connections/warehouses/catalog/azuresqldb/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ hidden: true
44
---
55

66
> info ""
7-
> Our Azure SQL Database connector is in limited beta. Please [contact us](segment.com/help/contact/) for more information.
7+
> Our Azure SQL Database connector is in limited beta. Please [contact us](https://segment.com/help/contact/) for more information.
88
99

1010
<!--

src/getting-started/02-simple-install.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ When you create a new library source, you can find the write key in the **Settin
4949
![](/docs/connections/images/find_writekey.png)
5050

5151
> info ""
52-
> [Cloud-sources](/docs/guides/sources/about-cloud-sources/) do not have write keys, as they use a token or key from your account with that service. Cloud sources have other considerations, and aren't part of this tutorial.
52+
> [Cloud-sources](/docs/connections/sources/about-cloud-sources/) do not have write keys, as they use a token or key from your account with that service. Cloud sources have other considerations, and aren't part of this tutorial.
5353
5454
Make note of or write down your write key, as you'll need it in the next steps.
5555

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ If your organization sells a product or services to other businesses, you might
6565

6666
#### Ecommerce Spec
6767

68-
If your organization sells products online, the E-commerce Spec covers the customer's journey as they browse your store, click on promotions, view products, add those products to a cart, and complete a purchase. It also provides recommendations about off-page interactions, including interactions with email promotions, coupons, and other systems. You can read more about [why companies need an Ecommerce Spec](https://segment.com/blog/2014-08-28-ecommerce-analytics-story/), read more about [Ecommerce tracking plans](/docs/protocols/data-quality/ecommerce-tracking-plan/), and dive directly into our [Ecommerce Spec](/docs/connections/spec/ecommerce/v2/).
68+
If your organization sells products online, the E-commerce Spec covers the customer's journey as they browse your store, click on promotions, view products, add those products to a cart, and complete a purchase. It also provides recommendations about off-page interactions, including interactions with email promotions, coupons, and other systems. You can read more about [why companies need an Ecommerce Spec](https://segment.com/blog/2014-08-28-ecommerce-analytics-story/), read more about [Ecommerce tracking plans](/docs/connections/spec/ecommerce-tracking-plan/), and dive directly into our [Ecommerce Spec](/docs/connections/spec/ecommerce/v2/).
6969

7070
#### Mobile Spec
7171

src/getting-started/04-full-install.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Consider using Identify and traits when:
6767

6868
## How to Call Identify
6969

70-
You can call Identify from any of Segment’s device-based or server-based libraries, including [Javascript](/docs/connections/sources/catalog/website/javascript/), [iOS](/docs/connections/sources/catalog/mobile/ios), [Android](/docs/connections/sources/catalog/mobile/android), [Ruby](/docs/connections/sources/catalog/server/ruby/), and [Python](/docs/connections/sources/catalog/server/python/).
70+
You can call Identify from any of Segment’s device-based or server-based libraries, including [Javascript](/docs/connections/sources/catalog/libraries/website/javascript/), [iOS](/docs/connections/sources/catalog/mobile/ios), [Android](/docs/connections/sources/catalog/mobile/android), [Ruby](/docs/connections/sources/catalog/libraries/server/ruby/), and [Python](/docs/connections/sources/catalog/libraries/server/python/).
7171

7272
Here are two examples of calling identify from two different libraries:
7373

@@ -123,7 +123,7 @@ The `Page` and `Screen` calls tell Segment what web page or mobile screen the us
123123

124124
### Page and Screen call properties
125125

126-
You can always [override the auto-collected Page/Screen properties](/docs/connections/sources/catalog/website/javascript/#default-properties) with your own, and set additional custom page or screen properties.
126+
You can always [override the auto-collected Page/Screen properties](/docs/connections/sources/catalog/libraries/website/javascript/#default-properties) with your own, and set additional custom page or screen properties.
127127

128128
Some downstream tools (like [Marketo](/docs/connections/destinations/catalog/marketo/)) require that you attach specific properties (like email address) to every `page` call.
129129

@@ -164,7 +164,7 @@ If the presentation of user interface components don’t substantially change th
164164
> note ""
165165
> **Note**: When you trigger a Page call manually, make sure the call happens _after_ the UI element is successfully displayed, not when it is called. It shouldn’t be called as part of the click event that initiates it.
166166
167-
For more info on Page calls, please review [Page spec](/docs/spec/page/) and [Analytics.js docs](/docs/connections/sources/catalog/website/javascript/#page).
167+
For more info on Page calls, please review [Page spec](/docs/spec/page/) and [Analytics.js docs](/docs/connections/sources/catalog/libraries/website/javascript/#page).
168168
169169
### When to call Screen
170170

src/getting-started/05-data-to-destinations.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ There are also a number of Business tier features you can then use with your war
6363

6464

6565
<div class="double">
66-
{% include components/media-icon.html href="/getting-started/04-testing-debugging/" newtab="false" icon="symbols/arrow-left.svg" title="Back: A full Segment implementation" content="Take your plans, and make them real." variant="related" %}
66+
{% include components/media-icon.html href="/getting-started/04-full-install//" newtab="false" icon="symbols/arrow-left.svg" title="Back: A full Segment implementation" content="Take your plans, and make them real." variant="related" %}
6767

6868
{% include components/media-icon.html href="/getting-started/06-testing-debugging/" newtab="false" icon="symbols/arrow-right.svg" title="Next: Testing and Debugging" content="Test your implementation and see where your data is and isn't arriving." variant="related" %}
6969
</div>

src/guides/how-to-guides/cross-channel-tracking.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ But these off-domain and cross-device brand interactions are equally, if not mor
88

99
In this guide, we'll share where and how to track these critical events so that you can understand your customer's journey before they even get to your storefront, as well as their preferred shopping experiences.
1010

11-
_If you're interested in learning about what to track,_ [check out our guide on creating an e-commerce tracking plan](/docs/protocols/ecommerce-tracking-plan/).
11+
_If you're interested in learning about what to track,_ [check out our guide on creating an e-commerce tracking plan](/docs/connections/spec/ecommerce-tracking-plan/).
1212

1313
[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.
1414

src/guides/intro-admin.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Segment contains several ways to see what's going on in your Workspace:
5757
- Last but not least, check out our list of [integration error codes](/docs/connections/integration_error_codes/) for clues about what might be causing an error.
5858

5959
> info ""
60-
> Still stumped? [Contact us](segment.com/help/contact/) for more help troubleshooting!
60+
> Still stumped? [Contact us](https://segment.com/help/contact/) for more help troubleshooting!
6161
6262

6363
<!-- TODO

src/partners/index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The development process is simple:
3434

3535
It's important to understand Segment's [Conceptual Model](/docs/partners/conceptual-model) to begin planning your integration. This will help you understand how data will flow from or into your integration.
3636

37-
### 2. Request Access
37+
### 2. Request Access
3838

3939
During _Developer Preview_, you will need to [request access to Developer Center](https://segment.com/partners/developer-center/). A Segment account is required for this step.
4040

@@ -78,7 +78,7 @@ You can submit your Component in the Developer Center for review. We strive to r
7878

7979
Our team will test your integration and review your documentation and marketing material. In order to keep this review feedback loop short, please make sure that your integration:
8080

81-
- Adheres to the [Segment Spec](/docs/partners/spec/)
81+
- Adheres to the [Segment Spec](/docs/connections/spec/)
8282
- Adheres to your published documentation
8383
- Supports high data volumes
8484
- Meets all [launch requirements](/docs/partners/#launch-requirements)

src/partners/subscriptions/index.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ A Subscription gives you complete control over how you want to store, transform
88

99
## Getting Started
1010

11-
Please review the steps outlined in the [Developer Center Overview](/docs/partners). This document outlines specific details for Step 4 as it relates to building a subscription.
11+
Please review the steps outlined in the [Developer Center Overview](/docs/partners). This document outlines specific details for Step 4 as it relates to building a subscription.
1212

1313
1. Understand Segment's [Conceptual Model](/docs/partners/conceptual-model).
1414
2. Request [access to the Segment Developer Center](https://segment.com/partners/developer-center/).
@@ -22,7 +22,7 @@ Please review the steps outlined in the [Developer Center Overview](/docs/partne
2222

2323
You can subscribe to customer data in two ways:
2424

25-
1. **[Webhook](/docs/partners/build-webhook)**: Build a new HTTP service that receives Webhook POSTs from Segment.
26-
2. **[Functions](/docs/partners/build-functions)**: Write JavaScript functions that run on Segment to translate and send data to your existing API. [Get started...](/docs/partners/build-functions)
25+
1. **[Webhook](/docs/partners/subscriptions/build-webhook)**: Build a new HTTP service that receives Webhook POSTs from Segment.
26+
2. **[Functions](/docs/partners/subscriptions/build-functions)**: Write JavaScript functions that run on Segment to translate and send data to your existing API. [Get started...](/docs/partners/build-functions)
2727

2828
See the [Webhook](/docs/partners/build-webhook) and [Functions](/docs/partners/build-webhook) docs in-depth technical details about building.

src/protocols/tracking-plan/create.md

+5-4
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
22
title: The Protocols Tracking Plan
3-
redirect_from: '/protocols/tracking-plan/'
4-
redirect_from: '/protocols/whats-a-tracking-plan/'
5-
redirect_from: '/protocols/data-quality/whats-a-tracking-plan/'
6-
redirect_from: '/protocols/example-tracking-plan/'
3+
redirect_from:
4+
- '/protocols/tracking-plan/'
5+
- '/protocols/whats-a-tracking-plan/'
6+
- '/protocols/data-quality/whats-a-tracking-plan/'
7+
- '/protocols/example-tracking-plan/'
78
---
89

910
A Tracking Plan is a data spec outlining the events and properties you intend to collect across your Segment Sources. Crafting a comprehensive Tracking Plan takes time and effort across a range of teams within your organization, and a deep understanding of your business objectives. [Learn more about data quality best practices here](/docs/protocols/tracking-plan/best-practices/). Once created though, the Tracking Plan becomes a highly valuable resource for both the engineers instrumenting Segment and all consumers of the data flowing through Segment.

tests/redirects/testPaths.txt

+2-2
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@
2020
/docs/connections/sources/catalog/server/net/quickstart/
2121
/docs/connections/sources/catalog/server/node/quickstart/
2222
/docs/connections/sources/catalog/server/php/quickstart/
23-
/docs/connections/sources/catalog/server/python/quickstart/
24-
/docs/connections/sources/catalog/server/ruby/quickstart/
23+
/docs/connections/sources/catalog/libraries/server/python/quickstart/
24+
/docs/connections/sources/catalog/libraries/server/ruby/quickstart/
2525
/docs/connections/sources/catalog/server/rust/quickstart/
2626
/docs/connections/sources/iterable/
2727
/docs/connections/warehouses/add-users/

0 commit comments

Comments
 (0)