Skip to content

Commit ce03c32

Browse files
authored
Merge pull request #52 from segmentio/master
merge to staging. I need to figure out how to do this from the command line.
2 parents d09f2f0 + 80d3afd commit ce03c32

File tree

343 files changed

+936
-790
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

343 files changed

+936
-790
lines changed

_config.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ defaults:
1313
layout: "page"
1414
hidden: false
1515
beta: false
16+
seo-priority: 0.5
17+
seo-changefreq: weekly
1618
- scope:
1719
path: "connections/destinations"
1820
values:

_data/sidenav/default.yml

Lines changed: 31 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1,5 @@
11
---
22
sections:
3-
- section_title: Connections
4-
section:
5-
- path: "/connections/spec"
6-
title: Spec
7-
- section_title: Sources
8-
slug: connections/Sources
9-
section:
10-
- path: "/connections/sources"
11-
title: Overview
12-
- path: "/connections/sources/visual-tagger"
13-
title: "Visual tagger"
14-
- path: "connections/sources/faq"
15-
title: "FAQ"
16-
- path: "/connections/sources/catalog"
17-
title: Sources catalog
18-
- section_title: Destinations
19-
slug: connections/destinations
20-
section:
21-
- path: "/connections/destinations"
22-
title: Overview
23-
- path: "/connections/destinations/destination-filters"
24-
title: Destinations Filters
25-
- path: "/connections/destinations/catalog"
26-
title: Destinations catalog
27-
- section_title: Warehouses
28-
slug: connections/warehouses
29-
section:
30-
- path: "/connections/warehouses"
31-
title: Overview
32-
- path: "/connections/warehouses/choose-warehouse"
33-
title: Choosing a Warehouse
34-
- path: "/connections/warehouses/add-warehouse-users"
35-
title: Add users to a Warehouse
36-
- path: "/connections/warehouses/redshift-faq"
37-
title: "Redshift Best Practices"
38-
- path: "/connections/warehouses/redshift-tuning"
39-
title: "Improving Redshift performance"
40-
- path: "/connections/warehouses/warehouse-errors"
41-
title: "Warehouse Error codes"
42-
- path: "/connections/warehouses/faq"
43-
title: Warehouses FAQs
44-
- path: "/connections/warehouses/catalog"
45-
title: Warehouses Catalog
463
- section_title: Guides
474
section:
485
- path: "/guides"
@@ -174,6 +131,37 @@ sections:
174131
title: How do I find out my usage data?
175132
- path: "/guides/usage-and-billing/volume-and-pricing"
176133
title: How does my event and object volume impact my pricing?
134+
- section_title: Connections
135+
section:
136+
- path: "/connections/spec"
137+
title: Spec
138+
- section_title: Sources
139+
slug: connections/Sources
140+
section:
141+
- path: "/connections/sources"
142+
title: Overview
143+
- path: "/connections/sources/visual-tagger"
144+
title: "Visual tagger"
145+
- path: "/connections/sources/faq"
146+
title: "FAQ"
147+
- path: "/connections/sources/catalog"
148+
title: Sources catalog
149+
- section_title: Destinations
150+
slug: connections/destinations
151+
section:
152+
- path: "/connections/destinations"
153+
title: Overview
154+
- path: "/connections/destinations/destination-filters"
155+
title: Destinations Filters
156+
- path: "/connections/destinations/catalog"
157+
title: Destinations catalog
158+
- section_title: Warehouses
159+
slug: connections/warehouses
160+
section:
161+
- path: "/connections/warehouses"
162+
title: Overview
163+
- path: "/connections/warehouses/catalog"
164+
title: Warehouses catalog
177165
- section_title: Personas
178166
section:
179167
- path: "/personas"

_includes/content/spec-field-page-name.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,6 @@
22
<td>`name` *optional*</td>
33
<td>String</td>
44
<td>Name of the page
5-
<p> For example, most sites have a Signup page that can be useful to tag, so you can see users as they move through your funnel.</p>
5+
<p> For example, most sites have a "Signup" page that can be useful to tag, so you can see users as they move through your funnel.</p>
66
</td>
77
</tr>
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
Destinations are business tools or apps that you can connect to the data flowing through Segment. Some of our most popular destinations are Google Analytics, Mixpanel, KISSmetrics, Customer.io, Intercom, and KeenIO.
2+
3+
All of these tools run on the same data: who are your customers and what are they doing? But each tool requires that you send that data in a slightly different format, which means that you'd have to write code to track all of this information, again and again, for each tool, on each page of your app or website.
4+
5+
Enter Segment. Do it once!
6+
7+
We eliminate this process by introducing an abstraction layer. You send your data to us, and we understand how to translate it so we can send it along to any destination. You enable destinations from the catalog in the Segment App, and user data immediately starts flowing into those tools. No extra code required!
8+
9+
We support many categories of destinations, from advertising to marketing, email to customer support, CRM to user testing, and even data warehouses. You can view a complete list of our [destinations](/docsv2/connections/destinations/catalog/) or check out our [destination page](https://segment.com/destinations) for a searchable list broken down by category.

_includes/content/whats-a-source.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
In Segment, you create a source (or more than one!) for each website or app you want to track. While it's not required that you have a single Source for each server, site or app, we **highly recommend** creating a Source for each unique source of data.
2+
3+
Sources belong to a workspace, and the URL for a source look something like this:
4+
`https://segment.com/<my-workspace>/sources/<my-source-name>/`
5+
6+
You can create new sources using the button in the workspace view. Each source you create has a write key, which is used to send data to that source. For example, to load [`analytics.js`, the Segment JavaScript library](https://segment.com/docs/sources/website/analytics.js/) on your page, the snippet on the [Quickstart Guide](https://segment.com/docs/sources/website/analytics.js/quickstart/) includes:
7+
8+
```js
9+
analytics.load("YOUR_WRITE_KEY");
10+
```
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
A warehouse is a central repository of data collected from one or more sources. This is what commonly comes to mind you think about a relational database: structured data that fits neatly into rows and columns.
2+
3+
In Segment, a Warehouse is a special type destination. Instead of streaming data to the destination all the time, we load data to them in bulk at a regular intervals. When we load data, we insert and update events and objects, and automatically adjust their schema to fit the data you’ve sent to Segment.
4+
5+
When selecting and building a data warehouse, there are three questions to consider:
6+
7+
1. What type of data will be collected?
8+
2. How many data sources will there be?
9+
3. How will the data be used?
10+
11+
Relational databases are great when you know and predefine the information collected and how it will be linked. This is usually the type of database used in the world of user analytics. For instance, a users table might be populated with the columns "name", "email address", "plan name", etc.
12+
13+
Examples of data warehouses include Amazon Redshift, Google BigQuery, MySQL, and Postgres.
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
A workspace is a group of sources that can be administered and billed together. Workspaces let you collaborate with team members, add permissions, and share sources across your whole team using a shared billing account.
2+
3+
Workspaces help companies manage access for multiple users and data sources. When you are logged in to your Segment account, you can create a new workspace from the menu.

_templates/destinations.example.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11873,7 +11873,7 @@ destinations:
1187311873
required: false
1187411874
string_validators:
1187511875
regexp: ''
11876-
description: To find your API key, log into Pendo and navigate to your user name
11876+
description: To find your API key, log into Pendo and navigate to "your user name"
1187711877
> Site settings > Basic Information > API key. If your account has not fully
1187811878
been set up yet, you can see the API key inside of the code snippet on the Pendo
1187911879
setup page.
@@ -14653,11 +14653,11 @@ destinations:
1465314653
required: true
1465414654
string_validators:
1465514655
regexp: "^.{8,}$"
14656-
description: To find your key, log into Split and navigate to Admin Settings
14657-
> Integrations > select your desired workspace > Segment. There you can
14656+
description: To find your key, log into Split and navigate to "Admin Settings"
14657+
> "Integrations" > select your desired workspace > "Segment". There you can
1465814658
find the key for each configured integration. If you don’t have an integration
14659-
configured, be sure to configure your integration in the section Configure
14660-
as a destination in Segment and click save to generate a key. For more information,
14659+
configured, be sure to configure your integration in the section "Configure
14660+
as a destination in Segment" and click save to generate a key. For more information,
1466114661
learn more in Split’s [integration documentation](https://segment.com/docs/destinations/split/).
1466214662
settings: []
1466314663
- name: catalog/destinations/stitch-data
@@ -15562,7 +15562,7 @@ destinations:
1556215562
required: true
1556315563
string_validators:
1556415564
regexp: "^[a-zA-Z0-9]*$"
15565-
description: Drop in the Integration Key into your Segment Settings UI which
15565+
description: Drop in the "Integration Key" into your Segment Settings UI which
1556615566
you can find on https://businessapp.b2b.trustpilot.com/#/ecommerce/segment
1556715567
settings: []
1556815568
- name: catalog/destinations/tune

connections/destinations/catalog/aboardly/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,3 +18,6 @@ When you `identify` a user, we'll pass that user's information to Aboardly with
1818
## Track
1919

2020
When you `track` an event, we will send that event to Aboardly as a custom event.
21+
22+
23+
{% include content/integration-foot.md %}

connections/destinations/catalog/activecampaign/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,8 @@ This document was last updated on March 27, 2018. If you notice any gaps, outdat
1313

1414
{% include content/connection-modes.md %}
1515

16-
1. From your Segment UI’s Destinations page click on Add Destination.
17-
2. Search for Active Campaign within the Destinations Catalog and confirm the Source you’d like to connect to.
16+
1. From your Segment UI’s Destinations page click on "Add Destination".
17+
2. Search for "Active Campaign" within the Destinations Catalog and confirm the Source you’d like to connect to.
1818
3. Add your API URL and API Key which can be found in your ActiveCampaign UI Settings page under the Developer tab.
1919
4. Since the Segment ActiveCampaign destination integration is 100% handled through Segment, you don't need to install ActiveCampaign site tracking or event tracking Javascript code.
2020

connections/destinations/catalog/adobe-analytics/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -451,7 +451,7 @@ You can either send the property value as a string (ie. `'brady'`) or as an arra
451451

452452
### Merchandising Events
453453

454-
The Merchandising Events settings allow you to set eVars and events on a per-product basis within the products string, and support increment and currency events. This provides robust product string support, which you can read more about [here](https://marketing.adobe.com/resources/help/en_US/sc/implement/products.html).
454+
The Merchandising Events settings allow you to set eVars and events on a per-product basis within the "products" string, and support increment and currency events. This provides robust product string support, which you can read more about [here](https://marketing.adobe.com/resources/help/en_US/sc/implement/products.html).
455455

456456
The setting operates as follows:
457457

connections/destinations/catalog/adobe-target/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ document.addEventListener(adobe.target.event.REQUEST_SUCCEEDED, function() {
121121
### Preventing Page Flicker
122122

123123
Page flicker may occur when default content momentarily displays to a visitor
124-
prior to the A/B activity content replacing it. One approach to preventing
124+
prior to the A/B "activity" content replacing it. One approach to preventing
125125
page flicker in conjunction with Segment would be to create a global mbox. Adobe
126126
will automatically set the HTML body style opacity to 0, which keeps the page
127127
content hidden while allowing the browser to still execute page load. After a

connections/destinations/catalog/adroll/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,8 @@ This document was last updated on January 26, 2018. If you notice any gaps, outd
1717

1818
{% include content/connection-modes.md %}
1919

20-
1. From your Segment UI’s Destinations page click on Add Destination.
21-
2. Search for Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to.
20+
1. From your Segment UI’s Destinations page click on "Add Destination".
21+
2. Search for "Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to.
2222
3. Locate both your AdRoll Advertiser ID and Pixel ID in AdRoll's "Audience" tab, "AdRoll Pixel" section. Click on "View Pixel". Your Advertiser ID will be listed beside `adroll_adv_id` and your AdRoll Pixel will be listed beside `adroll_pix_id`.
2323

2424
![](images/adroll-pixel.png)

connections/destinations/catalog/adtriba/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,3 +56,5 @@ analytics.track('Conversion', {
5656
Track calls will be sent to Adtriba as a `track` event.
5757

5858
Trigger additional events by using [Semantic Events](https://segment.com/docs/spec/semantic/) in order to enrich the Adtriba machine learning process.
59+
60+
{% include content/integration-foot.md %}

connections/destinations/catalog/adwords-remarketing-lists/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,3 +54,5 @@ We attempt to match users in your audience with the identifiers that Google supp
5454
### What Adwords platforms are supported?
5555

5656
This destination supports Search, Gmail, and Youtube ad campaigns. Adwords does not support Display campaigns through remarketing lists.
57+
58+
{% include content/integration-foot.md %}

connections/destinations/catalog/adwords/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,3 +216,6 @@ The following properties are optional, if you'd like to see more, please get in
216216
</table>
217217

218218
Here's Google documentation for the endpoint we hit [for iOS apps](https://developers.google.com/app-conversion-tracking/ios/conversion-tracking-server#reporting_in-app_conversions_from_an_analytics_server) and [for Android Apps](https://developers.google.com/app-conversion-tracking/android/conversion-tracking-server#in-app_conversions). It can take 24-48 hours for conversions to show up in the conversions dashboard.
219+
220+
221+
{% include content/integration-foot.md %}

connections/destinations/catalog/akita/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,3 +50,6 @@ When you call `page`, Segment will send that event to Akita as a `Page View`.
5050
## Track
5151

5252
When you call `track`, Segment will send that event to Akita as an `Event`.
53+
54+
55+
{% include content/integration-foot.md %}

connections/destinations/catalog/alexa/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd
1010

1111
{% include content/connection-modes.md %}
1212

13-
1. From your Segment UI’s Destinations page click on Add Destination.
14-
2. Search for Alexa within the Destinations Catalog and confirm the Source you’d like to connect to.
13+
1. From your Segment UI’s Destinations page click on "Add Destination".
14+
2. Search for "Alexa" within the Destinations Catalog and confirm the Source you’d like to connect to.
1515
3. Fill in your "Account ID" which you can find in the Alexa Javascript snippet. It appears as atrk_acct: 'XXXXXXX'.
1616
4. Fill in your "Domain" which you can find in the Alexa Javascript snippet. It appears as domain: 'example.com'.
1717
5. In about 5-10 minutes the CDN will be updated and the Alexa Javascript snippet will be initialized onto your page.

connections/destinations/catalog/all-aboard/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,3 +40,5 @@ Segment allows you to expose what your users do in your application. This inform
4040
For instance, using our simple example above perhaps you only want to invite customers who completed the registration process to an onboarding call. The `finished_registration: TRUE` trait allows you to quickly identify these customers.
4141

4242
Traits are also useful in helping you have a more personal dialog with your trial customers. More personal call invitations encourage your most qualified customers to schedule a call with you.
43+
44+
{% include content/integration-foot.md %}

connections/destinations/catalog/amazon-lambda/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ While setting up the new role, add the policy you created in the previous step.
133133

134134
Finish with any other setup items you may want (like `tags`). Once that’s complete, search for and click on your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home).
135135

136-
Select the Trust Relationships tab, then click the Edit trust relationship button.
136+
Select the "Trust Relationships" tab, then click the "Edit trust relationship" button.
137137

138138
![](images/LambdaTrustRelationship.png)
139139

@@ -170,7 +170,7 @@ If you have multiple Source’s using this Role, replace the `sts:ExternalId` se
170170

171171
## Configure Segment Lambda Destination
172172

173-
Search for Lambda" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the AWS Lambda settings.
173+
Search for "Lambda" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the AWS Lambda settings.
174174

175175

176176
## FAQ

connections/destinations/catalog/amazon-personalize/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -590,7 +590,7 @@ The "Import user-item interaction data" step is displayed next. To complete this
590590

591591
For the "IAM service role", select "Create a new role" from the dropdown. In the next pop-up, we recommend listing your bucket name in the "Specific S3 buckets" option, but you're free to choose the option that best suits your needs.
592592

593-
Next you will need the location of the CSV file you generated in the earlier steps. This needs to be configured in the Data Location field on this screen.
593+
Next you will need the location of the CSV file you generated in the earlier steps. This needs to be configured in the "Data Location" field on this screen.
594594

595595
![](images/PersonalizeImportJob.png)
596596

@@ -692,7 +692,7 @@ While setting up the new role, add the policy you created in the previous step.
692692

693693
Finish with any other setup items you may want (like `tags`). Once that’s complete, search for and click on your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home).
694694

695-
Select the Trust Relationships tab, then click the Edit trust relationship button.
695+
Select the "Trust Relationships" tab, then click the "Edit trust relationship" button.
696696

697697
![](images/LambdaTrustRelationship.png)
698698

@@ -868,7 +868,7 @@ Enter a name for your Event Tracker.
868868

869869
You will need to configure a role for Personalize to that allows it to execute the tracker. This is the same as the execution role you defined earlier for Personalize:
870870

871-
Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess
871+
Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess"
872872

873873
```
874874
{
@@ -917,7 +917,7 @@ Often this is automatically included as a policy labelled "AmazonPersonalizeFull
917917
}
918918
```
919919

920-
This may be automatically included as policy AmazonPersonalize-ExecutionPolicy-<some-set-of-numbers>
920+
This may be automatically included as policy "AmazonPersonalize-ExecutionPolicy-<some-set-of-numbers>"
921921

922922
```
923923
{
@@ -998,7 +998,7 @@ Your lambda is now ready to receive events from Segment. Next, you will need to
998998

999999
Once your Lambda function is enabled, you can send it events from Segment using the Personalize Destination.
10001000

1001-
Search for Amazon Personalize in our catalog. Connect the destination to the source you created previously. Now you will be presented with the Amazon Personalize Settings.
1001+
Search for "Amazon Personalize" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the Amazon Personalize Settings.
10021002

10031003
We allow you to send each call type to a different Lambda. If you leave the Lambda field blank for a given call type, we won’t attempt to send any of those calls.
10041004

connections/destinations/catalog/appcues/index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,4 +116,6 @@ lifecycle events that can be tracked:
116116
* `coachmarks_completed`
117117

118118
To enable this feature, go to the Integrations Settings in Appcues and
119-
click “Activate” under the Segment integration.
119+
click "Activate" under the Segment integration.
120+
121+
{% include content/integration-foot.md %}

connections/destinations/catalog/appsflyer/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat
1111

1212
{% include content/connection-modes.md %}
1313

14-
1. From your Segment UI’s Destinations page click on Add Destination.
15-
2. Search for AppsFlyer within the Destinations Catalog and confirm the Source you’d like to connect to.
14+
1. From your Segment UI’s Destinations page click on "Add Destination".
15+
2. Search for "AppsFlyer" within the Destinations Catalog and confirm the Source you’d like to connect to.
1616
3. Drop in your `AppsFlyer Dev Key`, which can be retrieved from the App Settings section of your AppsFlyer account.
1717
4. Follow the instructions in the Github repos: [iOS SDK](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android SDK](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration).
1818
5. After you build and release to the app store, we start translating and sending your data to AppsFlyer automatically.

0 commit comments

Comments
 (0)