diff --git a/src/_data/nav.yml b/src/_data/nav.yml index 159e2b8972..62fcfb98be 100644 --- a/src/_data/nav.yml +++ b/src/_data/nav.yml @@ -20,7 +20,7 @@ sections: section: - path: "https://segment.com/docs/" title: Documentation - - path: "https://segment.com/docs/config-api/" + - path: "https://segment.com/docs/api/public-api/" title: Segment API - path: "https://segment.com/partners/developer-center/" title: Build on Segment diff --git a/src/connections/destinations/catalog/selligent-marketing-cloud/index.md b/src/connections/destinations/catalog/selligent-marketing-cloud/index.md index feb8ce1ec0..95799b66b9 100644 --- a/src/connections/destinations/catalog/selligent-marketing-cloud/index.md +++ b/src/connections/destinations/catalog/selligent-marketing-cloud/index.md @@ -17,7 +17,7 @@ Before you enable Selligent Marketing Cloud in your Destination page, validate w 1. Login into your *Selligent Marketing Cloud* environment. 2. Within the *Selligent Marketing Cloud* module click the wheel icon at the bottom-left corner to access the general configuration panel: ![1](images/1.png) -1. Navigate tothe "Access Management" tab and select "Service Accounts": +1. Navigate to the "Access Management" tab and select "Service Accounts": ![2](images/2.png) 4. To create a new account click on the "New" icon: ![3](images/3.png) @@ -40,7 +40,7 @@ You can then proceed to configure your destination. ## Identify -If you haven't had a chance to review the Segment spec, please take time to review and to understand what the [`identify` method](/docs/spec/identify/) does. +If you haven't had a chance to review the Segment spec, please take time to review and to understand what the [`identify` method](/docs/connections/spec/identify/) does. An example call can look like: @@ -57,7 +57,7 @@ Identify calls will be sent to *Selligent Marketing Cloud* as an `identify` even ## Track -If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`track` method](/docs/spec/track/) can do. +If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`track` method](/docs/connections/spec/track/) can do. An example call can look like: @@ -73,7 +73,7 @@ Track calls will be sent to *Selligent Marketing Cloud* as a `track` event. ## Group -If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`group` method](/docs/spec/group/) can do. +If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`group` method](/docs/connections/spec/group/) can do. An example call can look like: @@ -100,7 +100,7 @@ Segment sends Group calls to *Selligent Marketing Cloud* as a `group` event. The ## Alias -If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`alias` method](/docs/spec/alias/) can do. +If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`alias` method](/docs/connections/spec/alias/) can do. An example call can look like: @@ -112,7 +112,7 @@ Track calls will be sent to *Selligent Marketing Cloud* as a `alias` event. ## Page -If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`page` method](/docs/spec/page/) can do. +If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`page` method](/docs/connections/spec/page/) can do. An example call can look like: ```js @@ -125,7 +125,7 @@ Track calls will be sent to *Selligent Marketing Cloud* as a `page` event. ## Screen -If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`screen` method](/docs/spec/screen/) can do. +If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`screen` method](/docs/connections/spec/screen/) can do. An example call in Objective C can look like: diff --git a/src/connections/destinations/repeater-migration.md b/src/connections/destinations/repeater-migration.md index b44099c774..38b0a52c8a 100644 --- a/src/connections/destinations/repeater-migration.md +++ b/src/connections/destinations/repeater-migration.md @@ -46,7 +46,7 @@ You can create a QA instance of your destination to verify that it is configured 1. If you created a QA instance of the Repeater and you created a QA destination instance, you can test this process before you use production data. -2. You can disable the repeater and enable the new destination instance manually in the Segment web app, or by using the [Segment Public API](/docs/-api/). +2. You can disable the repeater and enable the new destination instance manually in the Segment web app, or by using the [Segment Public API](/docs/public-api/). - **If the destination can de-duplicate events**, enable the new instance of the destination, and _then_ disable the Repeater. - **If the destination does not de-duplicate events**, you can disable the Repeater and then enable the new instance of the destination. diff --git a/src/connections/spec/mobile.md b/src/connections/spec/mobile.md index 3ecf1be547..962ad960e7 100644 --- a/src/connections/spec/mobile.md +++ b/src/connections/spec/mobile.md @@ -1,5 +1,7 @@ --- title: 'Native Mobile Spec' +redirect_from: + - '/spec/mobile' --- One of the core components of the Segment [Spec](/docs/connections/spec/) is the [`track`](/docs/connections/spec/track) method. It records any arbitrary event that the user has triggered. For Mobile tracking, in addition to `screen` calls, you'll want to send **specific event names** that Segment recognizes semantically. That way, we can transform them correctly before sending them off to downstream destinations. @@ -19,20 +21,38 @@ These events pair nicely with Segment's [ecommerce spec](/docs/connections/spec/ The Segment Native Mobile Spec includes the following semantic events: **Application Lifecycle Events** -- [Application Installed](#application-installed) -- [Application Opened](#application-opened) -- [Application Updated](#application-updated) -- [Application Backgrounded](#application-backgrounded) -- [Application Crashed](#application-crashed) -- [Application Uninstalled](#application-uninstalled) +- [Overview of events](#overview-of-events) +- [Lifecycle events](#lifecycle-events) + - [Application Installed](#application-installed) + - [Application Opened](#application-opened) + - [Application Backgrounded](#application-backgrounded) + - [Application Updated](#application-updated) + - [Application Uninstalled](#application-uninstalled) + - [Application Crashed](#application-crashed) +- [Campaign events](#campaign-events) + - [Install Attributed](#install-attributed) + - [Push Notification Received](#push-notification-received) + - [Push Notification Tapped](#push-notification-tapped) + - [Push Notification Bounced](#push-notification-bounced) + - [Deep Link Opened](#deep-link-opened) + - [Deep Link Clicked](#deep-link-clicked) **Campaign Events** -- [Push Notification Received](#push-notification-received) -- [Push Notification Tapped](#push-notification-tapped) -- [Push Notification Bounced](#push-notification-bounced) -- [Install Attributed](#install-attributed) -- [Deep Link Clicked](#deep-link-clicked) -- [Deep Link Opened](#deep-link-opened) +- [Overview of events](#overview-of-events) +- [Lifecycle events](#lifecycle-events) + - [Application Installed](#application-installed) + - [Application Opened](#application-opened) + - [Application Backgrounded](#application-backgrounded) + - [Application Updated](#application-updated) + - [Application Uninstalled](#application-uninstalled) + - [Application Crashed](#application-crashed) +- [Campaign events](#campaign-events) + - [Install Attributed](#install-attributed) + - [Push Notification Received](#push-notification-received) + - [Push Notification Tapped](#push-notification-tapped) + - [Push Notification Bounced](#push-notification-bounced) + - [Deep Link Opened](#deep-link-opened) + - [Deep Link Clicked](#deep-link-clicked) Segment recommends using the above event names if you're going to be integrating the events yourself. This will ensure that they can be mapped effectively in downstream tools. diff --git a/src/connections/spec/page.md b/src/connections/spec/page.md index d3f9c68203..b0e33871ba 100644 --- a/src/connections/spec/page.md +++ b/src/connections/spec/page.md @@ -1,5 +1,7 @@ --- title: 'Spec: Page' +redirect_from: + - '/spec/page' --- The `page` call lets you record whenever a user sees a page of your website, along with any optional properties about the page. Calling `page` or [`screen`](/docs/connections/spec/screen/) in a Segment [source](/docs/connections/sources/) is one of the first steps to getting started with Segment. diff --git a/src/connections/spec/screen.md b/src/connections/spec/screen.md index 69e3e8a5fb..aca9f02033 100644 --- a/src/connections/spec/screen.md +++ b/src/connections/spec/screen.md @@ -1,5 +1,7 @@ --- title: 'Spec: Screen' +redirect_from: + - '/spec/screen' --- The `screen` call lets you record whenever a user sees a screen, the mobile equivalent of `page`, in your mobile app, along with any properties about the screen. Calling `page` or [`screen`](/docs/connections/spec/screen/) in one of Segment's [sources](/docs/connections/sources/) is one of the first steps to getting started with Segment. diff --git a/src/partners/enable-with-segment.md b/src/partners/enable-with-segment.md index 1efa44ac35..d63d8bc6a3 100644 --- a/src/partners/enable-with-segment.md +++ b/src/partners/enable-with-segment.md @@ -2,10 +2,7 @@ title: Enable with OAuth --- -> info "" -> If you're a customer who just wants to build a simple script or app against a single workspace, you may want to use [Workspace Access Tokens](/docs/config-api/authentication). - -Enable with OAuth, supported with the [Public API](/docs/api), allows partners to build seamless flows for customers to implement and enable integrations within their workspace. This is a [post-launch requirement](/docs/partners/#post-launch) for a partner to graduate from public beta to public. +Enable with OAuth, supported with the [Public API](/docs/api/public-api), allows partners to build seamless flows for customers to implement and enable integrations within their workspace. This is a [post-launch requirement](/docs/partners/#post-launch) for a partner to graduate from public beta to public. ## Concepts @@ -191,7 +188,7 @@ If you created an App with a more permissive scope, you have access to more APIs - With the `workspace` scope you can change all resources - With the `workspace:read` you can read all resources, but not change them -A full list of APIs are here: https://segment.com/docs/config-api/ +A full list of APIs are here: https://segment.com/docs/api/public-api/ The example below shows how you would get a users workspace if you had any of the above scopes: @@ -309,4 +306,4 @@ When the app was installed, you should have received a Segment `workspace` and ### OK I managed to create an App. How do I use your APIs? -See [the API docs](https://segment.com/docs/config-api/), and the Postman API reference collection that you can run as-is https://reference.segmentapis.com/#51d965d3-4a67-4542-ae2c-eb1fdddc3df6. +See [the API docs](/docs/api/public-api/).