diff --git a/_includes/content/spec-field-page-name.md b/_includes/content/spec-field-page-name.md index 3eddaad4a6..2099172ea9 100644 --- a/_includes/content/spec-field-page-name.md +++ b/_includes/content/spec-field-page-name.md @@ -2,6 +2,6 @@ `name` *optional* String Name of the page -

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.

+

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.

\ No newline at end of file diff --git a/_includes/content/whats-a-destination.md b/_includes/content/whats-a-destination.md new file mode 100644 index 0000000000..f10166265d --- /dev/null +++ b/_includes/content/whats-a-destination.md @@ -0,0 +1,9 @@ +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. + +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. + +Enter Segment. Do it once! + +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! + +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. diff --git a/_includes/content/whats-a-source.md b/_includes/content/whats-a-source.md new file mode 100644 index 0000000000..2a2a74b958 --- /dev/null +++ b/_includes/content/whats-a-source.md @@ -0,0 +1,10 @@ +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. + +Sources belong to a workspace, and the URL for a source look something like this: +`https://segment.com//sources//` + +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: + +```js +analytics.load("YOUR_WRITE_KEY"); +``` diff --git a/_includes/content/whats-a-warehouse.md b/_includes/content/whats-a-warehouse.md new file mode 100644 index 0000000000..5a4b59546c --- /dev/null +++ b/_includes/content/whats-a-warehouse.md @@ -0,0 +1,13 @@ +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. + +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. + +When selecting and building a data warehouse, there are three questions to consider: + +1. What type of data will be collected? +2. How many data sources will there be? +3. How will the data be used? + +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. + +Examples of data warehouses include Amazon Redshift, Google BigQuery, MySQL, and Postgres. diff --git a/_includes/content/whats-a-workspace.md b/_includes/content/whats-a-workspace.md new file mode 100644 index 0000000000..d1014f19db --- /dev/null +++ b/_includes/content/whats-a-workspace.md @@ -0,0 +1,3 @@ +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. + +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. diff --git a/_templates/destinations.example.yml b/_templates/destinations.example.yml index f7c2d77efc..bd05318323 100644 --- a/_templates/destinations.example.yml +++ b/_templates/destinations.example.yml @@ -11873,7 +11873,7 @@ destinations: required: false string_validators: regexp: '' - description: To find your API key, log into Pendo and navigate to “your user name” + description: To find your API key, log into Pendo and navigate to "your user name" > Site settings > Basic Information > API key. If your account has not fully been set up yet, you can see the API key inside of the code snippet on the Pendo setup page. @@ -14653,11 +14653,11 @@ destinations: required: true string_validators: regexp: "^.{8,}$" - description: To find your key, log into Split and navigate to “Admin Settings” - > “Integrations” > select your desired workspace > “Segment”. There you can + description: To find your key, log into Split and navigate to "Admin Settings" + > "Integrations" > select your desired workspace > "Segment". There you can find the key for each configured integration. If you don’t have an integration - configured, be sure to configure your integration in the section “Configure - as a destination in Segment” and click save to generate a key. For more information, + configured, be sure to configure your integration in the section "Configure + as a destination in Segment" and click save to generate a key. For more information, learn more in Split’s [integration documentation](https://segment.com/docs/destinations/split/). settings: [] - name: catalog/destinations/stitch-data @@ -15562,7 +15562,7 @@ destinations: required: true string_validators: regexp: "^[a-zA-Z0-9]*$" - description: Drop in the “Integration Key” into your Segment Settings UI which + description: Drop in the "Integration Key" into your Segment Settings UI which you can find on https://businessapp.b2b.trustpilot.com/#/ecommerce/segment settings: [] - name: catalog/destinations/tune diff --git a/connections/destinations/catalog/activecampaign/index.md b/connections/destinations/catalog/activecampaign/index.md index ef22ce04c8..5548c63e32 100644 --- a/connections/destinations/catalog/activecampaign/index.md +++ b/connections/destinations/catalog/activecampaign/index.md @@ -13,8 +13,8 @@ This document was last updated on March 27, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Active Campaign” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Active Campaign" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your API URL and API Key which can be found in your ActiveCampaign UI Settings page under the Developer tab. 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. diff --git a/connections/destinations/catalog/adobe-analytics/index.md b/connections/destinations/catalog/adobe-analytics/index.md index 1d82318254..3926d84122 100644 --- a/connections/destinations/catalog/adobe-analytics/index.md +++ b/connections/destinations/catalog/adobe-analytics/index.md @@ -451,7 +451,7 @@ You can either send the property value as a string (ie. `'brady'`) or as an arra ### Merchandising Events -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). +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). The setting operates as follows: diff --git a/connections/destinations/catalog/adobe-target/index.md b/connections/destinations/catalog/adobe-target/index.md index de60095684..934eb30c30 100644 --- a/connections/destinations/catalog/adobe-target/index.md +++ b/connections/destinations/catalog/adobe-target/index.md @@ -121,7 +121,7 @@ document.addEventListener(adobe.target.event.REQUEST_SUCCEEDED, function() { ### Preventing Page Flicker Page flicker may occur when default content momentarily displays to a visitor -prior to the A/B “activity” content replacing it. One approach to preventing +prior to the A/B "activity" content replacing it. One approach to preventing page flicker in conjunction with Segment would be to create a global mbox. Adobe will automatically set the HTML body style opacity to 0, which keeps the page content hidden while allowing the browser to still execute page load. After a diff --git a/connections/destinations/catalog/adroll/index.md b/connections/destinations/catalog/adroll/index.md index f7b0f0347d..8a009cd5df 100644 --- a/connections/destinations/catalog/adroll/index.md +++ b/connections/destinations/catalog/adroll/index.md @@ -17,8 +17,8 @@ This document was last updated on January 26, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to. 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`. ![](images/adroll-pixel.png) diff --git a/connections/destinations/catalog/alexa/index.md b/connections/destinations/catalog/alexa/index.md index 5edfcf5514..4b92458ade 100644 --- a/connections/destinations/catalog/alexa/index.md +++ b/connections/destinations/catalog/alexa/index.md @@ -10,8 +10,8 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Alexa” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Alexa" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Fill in your "Account ID" which you can find in the Alexa Javascript snippet. It appears as atrk_acct: 'XXXXXXX'. 4. Fill in your "Domain" which you can find in the Alexa Javascript snippet. It appears as domain: 'example.com'. 5. In about 5-10 minutes the CDN will be updated and the Alexa Javascript snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/amazon-lambda/index.md b/connections/destinations/catalog/amazon-lambda/index.md index c8a754e805..8c2a6abfaa 100644 --- a/connections/destinations/catalog/amazon-lambda/index.md +++ b/connections/destinations/catalog/amazon-lambda/index.md @@ -133,7 +133,7 @@ While setting up the new role, add the policy you created in the previous step. 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). -Select the “Trust Relationships” tab, then click the “Edit trust relationship” button. +Select the "Trust Relationships" tab, then click the "Edit trust relationship" button. ![](images/LambdaTrustRelationship.png) @@ -170,7 +170,7 @@ If you have multiple Source’s using this Role, replace the `sts:ExternalId` se ## Configure Segment Lambda Destination -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. +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. ## FAQ diff --git a/connections/destinations/catalog/amazon-personalize/index.md b/connections/destinations/catalog/amazon-personalize/index.md index 1ca70ba150..e8eca2f5fa 100644 --- a/connections/destinations/catalog/amazon-personalize/index.md +++ b/connections/destinations/catalog/amazon-personalize/index.md @@ -590,7 +590,7 @@ The "Import user-item interaction data" step is displayed next. To complete this 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. -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. +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. ![](images/PersonalizeImportJob.png) @@ -692,7 +692,7 @@ While setting up the new role, add the policy you created in the previous step. 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). -Select the “Trust Relationships” tab, then click the “Edit trust relationship” button. +Select the "Trust Relationships" tab, then click the "Edit trust relationship" button. ![](images/LambdaTrustRelationship.png) @@ -868,7 +868,7 @@ Enter a name for your Event Tracker. 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: -Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess” +Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess" ``` { @@ -917,7 +917,7 @@ Often this is automatically included as a policy labelled "AmazonPersonalizeFull } ``` -This may be automatically included as policy “AmazonPersonalize-ExecutionPolicy-” +This may be automatically included as policy "AmazonPersonalize-ExecutionPolicy-" ``` { @@ -998,7 +998,7 @@ Your lambda is now ready to receive events from Segment. Next, you will need to Once your Lambda function is enabled, you can send it events from Segment using the Personalize Destination. -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. +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. 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. diff --git a/connections/destinations/catalog/appcues/index.md b/connections/destinations/catalog/appcues/index.md index cc6104bbf8..796c593f82 100644 --- a/connections/destinations/catalog/appcues/index.md +++ b/connections/destinations/catalog/appcues/index.md @@ -116,6 +116,6 @@ lifecycle events that can be tracked: * `coachmarks_completed` To enable this feature, go to the Integrations Settings in Appcues and -click “Activate” under the Segment integration. +click "Activate" under the Segment integration. {% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/appsflyer/index.md b/connections/destinations/catalog/appsflyer/index.md index 4ea4942a3d..e873e43aa6 100644 --- a/connections/destinations/catalog/appsflyer/index.md +++ b/connections/destinations/catalog/appsflyer/index.md @@ -11,8 +11,8 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “AppsFlyer“ within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "AppsFlyer" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `AppsFlyer Dev Key`, which can be retrieved from the App Settings section of your AppsFlyer account. 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). 5. After you build and release to the app store, we start translating and sending your data to AppsFlyer automatically. diff --git a/connections/destinations/catalog/apptimize/index.md b/connections/destinations/catalog/apptimize/index.md index 332f30ea94..33bafe114e 100644 --- a/connections/destinations/catalog/apptimize/index.md +++ b/connections/destinations/catalog/apptimize/index.md @@ -10,8 +10,8 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “Apptimize“ within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "Apptimize" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Apptimize application key, the 31 character key which you can find in your [Apptimize app settings](https://apptimize.com/admin/settings/apps). 4. Depending on the mobile library you've selected, follow the below instructions to complete your setup. diff --git a/connections/destinations/catalog/auryc/index.md b/connections/destinations/catalog/auryc/index.md index 501bef9139..91816a9532 100644 --- a/connections/destinations/catalog/auryc/index.md +++ b/connections/destinations/catalog/auryc/index.md @@ -11,7 +11,7 @@ _**NOTE:** The Auryc Destination is currently in beta, which means that they are {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for Auryc within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. 3. Add your Auryc site id in the destination settings. You can find this in Auryc by navigating to Project Settings > Web > and copying the value found on the line //cdn.auryc.com/auryc_siteid_here/container.js; 4. In about 5-10 minutes the CDN will be updated and Auryc snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/autopilothq/index.md b/connections/destinations/catalog/autopilothq/index.md index 0f07bf0aef..d2c09b0788 100644 --- a/connections/destinations/catalog/autopilothq/index.md +++ b/connections/destinations/catalog/autopilothq/index.md @@ -13,7 +13,7 @@ This document was last updated on October 12, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. + 1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "Autopilot" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your "API Key" from [here](https://login.autopilothq.com/login#settings/app-connections/segment-sync) or go to Autopilot: Settings -> App Connections -> Segment and copy/paste the API key which is listed there. 4. Once enabled 'identify' and 'track' calls will be sent to Autopilot. diff --git a/connections/destinations/catalog/bing-ads/index.md b/connections/destinations/catalog/bing-ads/index.md index a99e81a30d..c3f307710e 100644 --- a/connections/destinations/catalog/bing-ads/index.md +++ b/connections/destinations/catalog/bing-ads/index.md @@ -14,8 +14,8 @@ Before you can track conversions or target audiences, you need to create a UET t Once you have created the Tag ID, you can follow the steps below: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Bing Ads” within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Bing Ads" within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. 3. Drop in your Tag Id 4. In about 5-10 minutes the CDN will be updated and Bing Ads' snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/braze/index.md b/connections/destinations/catalog/braze/index.md index fe809d0e58..e733265f24 100644 --- a/connections/destinations/catalog/braze/index.md +++ b/connections/destinations/catalog/braze/index.md @@ -23,8 +23,8 @@ This document was last updated on June 13, 2018. If you notice any gaps, outdate {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Braze” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Braze" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, add the "API Key" which can be found in your Braze Dashboard under App Settings > Manage App Group. 4. You will also need to setup a new App Group REST API Key in the Braze Dashboard under App Settings > Developer Console > API Settings. Instructions can be found [here](https://www.braze.com/documentation/REST_API/#creating-and-managing-rest-api-keys). **Note:** For this App Group REST API Key, you will only need to select users.track endpoint under "User Data" 5. If you are implementing via Analytics.js, Segment will automatically load the [Braze Web SDK](https://www.braze.com/documentation/Web/). Otherwise, depending on the source you’ve selected, include Braze’s library by adding the following lines to your dependency configuration. @@ -326,7 +326,7 @@ The `inAppMessages` parameter will be an array of [`appboy.ab.InAppMessage`](htt ### Soft Push Prompts -1. Follow [step one](https://www.Braze.com/documentation/Web/#soft-push-prompts) to create a “Prime for Push” in-app messaging Campaign on the Braze dashboard. +1. Follow [step one](https://www.Braze.com/documentation/Web/#soft-push-prompts) to create a "Prime for Push" in-app messaging Campaign on the Braze dashboard. 2. Disable your [Automatically Send In-App Messages Destination setting](https://segment.com/docs/integrations/Braze/#settings). By default, it is enabled when you enable the Braze destination. diff --git a/connections/destinations/catalog/bugherd/index.md b/connections/destinations/catalog/bugherd/index.md index 93047e9aab..e897363217 100644 --- a/connections/destinations/catalog/bugherd/index.md +++ b/connections/destinations/catalog/bugherd/index.md @@ -9,8 +9,8 @@ This document was last updated on November 26, 2018. If you notice any gaps, out {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “BugHerd” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "BugHerd" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `API Key` as retrieved from the Install BugHerd tab on your BugHerd Project page. 4. Our CDN is updated within 5-10 minutes. Then our snippet will start asynchronously loading BugHerd onto your page. This means you should remove BugHerd's snippet from your page. 5. The BugHerd Destination doesn’t utilize any Segment API calls (e.g. identify, track, etc) so, once it's loaded, it’s good to go! Your BugHerd sidebar will begin appearing for your team. diff --git a/connections/destinations/catalog/bugsnag/index.md b/connections/destinations/catalog/bugsnag/index.md index 614c31726d..c3d8ba6086 100644 --- a/connections/destinations/catalog/bugsnag/index.md +++ b/connections/destinations/catalog/bugsnag/index.md @@ -19,8 +19,8 @@ This document was last updated on July 11th, 2018. If you notice any gaps, outda ### Web -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Bugsnag” within the Destinations Catalog and confirm the project you’d like to connect to +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Bugsnag" within the Destinations Catalog and confirm the project you’d like to connect to 3. Add your API key to your connection settings. You can find your API key in your Bugsnag dashboard under "Settings", which is located in the upper left-hand corner 4. We’ll automatically initialize Bugsnag's javascript script with your API key upon loading analytics.js diff --git a/connections/destinations/catalog/clearbit-enrichment/index.md b/connections/destinations/catalog/clearbit-enrichment/index.md index 73832ec2a4..003aca84f8 100644 --- a/connections/destinations/catalog/clearbit-enrichment/index.md +++ b/connections/destinations/catalog/clearbit-enrichment/index.md @@ -16,8 +16,8 @@ This document was last updated on April 20th, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Clearbit Enrichment” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Clearbit Enrichment" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment UI's destination settings, enter your Clearbit **secret** API key (note: it should start with "sk_"). You can find this in the API section of your [Clearbit dashboard](https://dashboard.clearbit.com/api). To verify that the destination has been set up correctly, check the Debugger section of your Segment Source. Assuming everything is as it should be, you should start seeing Clearbit Enrichment data populate in the `identify` events – click on the specific event you're interested in to see Clearbit Enrichment traits. These traits will now be available to other Segment destinations in your account. Notice that all Clearbit Enrichment traits are prefixed with `clearbit_` to ensure they don't conflict with existing traits. diff --git a/connections/destinations/catalog/clearbit-reveal/index.md b/connections/destinations/catalog/clearbit-reveal/index.md index 86fab21860..c2a647f71f 100644 --- a/connections/destinations/catalog/clearbit-reveal/index.md +++ b/connections/destinations/catalog/clearbit-reveal/index.md @@ -17,8 +17,8 @@ This document was last updated on August 29, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} Setup within Segment: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Clearbit Reveal” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Clearbit Reveal" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, enter your Clearbit **secret** API key (note: it should start with "sk_"). You can find this in the API section of your [Clearbit dashboard](https://dashboard.clearbit.com/api). Setup within Clearbit: diff --git a/connections/destinations/catalog/clicky/index.md b/connections/destinations/catalog/clicky/index.md index cf61de2c63..3a8f6180b6 100644 --- a/connections/destinations/catalog/clicky/index.md +++ b/connections/destinations/catalog/clicky/index.md @@ -14,8 +14,8 @@ This document was last updated on July 30th, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Clicky” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Clicky" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Site ID in the settings. You can find your Site ID under the Preferences of your account: ![Clicky Preferences](images/clicky-settings.png) 4. We’ll automatically initialize Clicky's script with your Site ID upon loading analytics.js. diff --git a/connections/destinations/catalog/delighted/index.md b/connections/destinations/catalog/delighted/index.md index db11e8dcce..d3faf5b405 100644 --- a/connections/destinations/catalog/delighted/index.md +++ b/connections/destinations/catalog/delighted/index.md @@ -15,8 +15,8 @@ This document was last updated on January 29, 2019. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your {{integration.name}} "API Key" in Segment's Settings UI. You can retrieve this from your {{integration.name}} Settings > API > Your API Key. It should look like "T8jtGnuYaNerDedVMYrcgn1dRdywfGOl". 4. If you're using Segment's client-side `analytics.js` library, we asynchronously load {{integration.name}}'s Javascript library onto the page and the CDN will be updated in 5-10 minutes. diff --git a/connections/destinations/catalog/drift/index.md b/connections/destinations/catalog/drift/index.md index c5a8153c8f..7ecb522241 100644 --- a/connections/destinations/catalog/drift/index.md +++ b/connections/destinations/catalog/drift/index.md @@ -20,7 +20,7 @@ This document was last updated on January 25, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. + 1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "Drift" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `API Key` and `Embed ID` as obtained from your Drift account (if Drift account not accessible yet, please [email the team](mailto:team@drift.com) to get a link for the Drift account creation). 4. If you're using analytics.js and 'identify' users by default, Drift will work automatically. If you don’t have analytics.js setup, after enabling the Drift destination in Segment, you must 'identify' users in order for Drift to display in your product. diff --git a/connections/destinations/catalog/facebook-app-events/index.md b/connections/destinations/catalog/facebook-app-events/index.md index 1cb9b6ee61..56f1556b07 100644 --- a/connections/destinations/catalog/facebook-app-events/index.md +++ b/connections/destinations/catalog/facebook-app-events/index.md @@ -14,8 +14,8 @@ This document was last updated on October 04, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Facebook App Events” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Facebook App Events" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Facebook App ID which can be retrieved from your [Facebook Apps dashboard](https://developers.facebook.com/apps/). 4. Once you turn on the Facebook App Events integration in your app's Segment project, we'll start sending `track` data to Facebook's App Events endpoints. diff --git a/connections/destinations/catalog/facebook-offline-conversions/index.md b/connections/destinations/catalog/facebook-offline-conversions/index.md index 618b69d899..07f7c85b16 100644 --- a/connections/destinations/catalog/facebook-offline-conversions/index.md +++ b/connections/destinations/catalog/facebook-offline-conversions/index.md @@ -13,9 +13,9 @@ This document was last updated on April 24, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “Facebook Offline Conversions” within the Destinations Catalog and confirm the Source you’d like to connect to. +2. Search for "Facebook Offline Conversions" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Authorize Segment to send data on your behalf by connecting through OAuth: diff --git a/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md b/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md index 103f86e24f..9b123e555a 100644 --- a/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md +++ b/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md @@ -29,7 +29,7 @@ Before we proceed, it’s important to register for these tools and enable them When you send tracking data from your app or website to Segment, Segment will send the same data to all of your tools. Segment also collects key messaging events like Push Notification Opened and Email Opened from AppBoy and Customer.io, respectively, and sends that to other tools. By defining cohorts based on these events, you can create dynamic campaign audiences, to which customers can add and remove themselves. -In each of your destinations—Appboy, Facebook, Customer.io, AdRoll—you can create custom campaigns to show display ads or send emails to a specific segment of users who have performed (or not performed) a given action, or “event.” In this cross-channel re-engagement example, we’ll start with push notifications. +In each of your destinations—Appboy, Facebook, Customer.io, AdRoll—you can create custom campaigns to show display ads or send emails to a specific segment of users who have performed (or not performed) a given action, or "event." In this cross-channel re-engagement example, we’ll start with push notifications. ## 1st Line of Defense: The Push Notification diff --git a/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md b/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md index 96cf79d83c..0da91f0d00 100644 --- a/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md +++ b/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md @@ -34,7 +34,7 @@ Scenarios when this tool will be useful:  ## Where to find it?  -Event Delivery can be accessed within any supported destination in the App. It’s located on the tab under “Settings” for each destination.  +Event Delivery can be accessed within any supported destination in the App. It’s located on the tab under "Settings" for each destination.  ![](../images/asset_rzYZESor.png) diff --git a/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md b/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md index ac1b47dd9f..bcdab6a8a1 100644 --- a/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md +++ b/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md @@ -40,7 +40,7 @@ We’ll conduct a split test (half of the cohort will represent the control grou ## Set it up -First, register for an account with Customer.io and Amplitude. Then, enable Customer.io and enable Amplitude on your Segment project. Finally, go into your Customer.io account and enable “sending data to Segment”: +First, register for an account with Customer.io and Amplitude. Then, enable Customer.io and enable Amplitude on your Segment project. Finally, go into your Customer.io account and enable "sending data to Segment": ![](../images/asset_tps7HAgP.png) @@ -52,13 +52,13 @@ When everything is enabled, customer event data such as `Order Completed` and `P ## Define the cohort in Customer.io -Now we define the specific cohort in Customer.io as per our conditions listed earlier: someone who spends over $20 per order and shops over twice a month. In Customer.io, go to “Segments” and “Create Segment”: +Now we define the specific cohort in Customer.io as per our conditions listed earlier: someone who spends over $20 per order and shops over twice a month. In Customer.io, go to "Segments" and "Create Segment": ![](../images/asset_kTaK5L7l.png) After this cohort is created, then when a customer makes the third purchase in a month and it’s over $20, then she will be added to this segment. -Next, we’ll create a “segment trigger campaign”, where Customer.io will send a message the first time someone enters a segment. The segment in this case will be the one we just created: Coupon Loyalty Experiment. +Next, we’ll create a "segment trigger campaign", where Customer.io will send a message the first time someone enters a segment. The segment in this case will be the one we just created: Coupon Loyalty Experiment. ![](../images/asset_lE6v8cXN.png) diff --git a/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md b/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md index 02a184a93b..825fcf9511 100644 --- a/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md +++ b/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md @@ -17,7 +17,7 @@ Every Push messaging focuses around three key features: ### Choose an destination -It’s best practice to self evaluate when trying to choose the “one” that suits your needs. +It’s best practice to self evaluate when trying to choose the "one" that suits your needs. 1. What’s your user base size? Is it more than 10k? If not, you can try demo versions of mobile marketing automation libraries. 2. Are you looking for a tool only to support push notification or provide an entire marketing suite ? @@ -58,7 +58,7 @@ Test different action words, phrases, message lengths, etc. * Marketing automation -To “auto-enroll” new users into existing campaigns +To "auto-enroll" new users into existing campaigns * Measure the right metrics diff --git a/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md b/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md index f525ce59c0..69aa421e8b 100644 --- a/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md +++ b/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md @@ -51,7 +51,7 @@ Destination receives the **Application Installed** event and attributes the inst Device-Mode Connection -For tools that support this, if you have enabled “Track Attribution Data” in your Segment dashboard, our integration listens to the attribution tool’s SDK for a change in attribution state. **Note**: Not all device-mode attribution tools offer “Track Attribution Data” functionality.  See the settings section for a particular tool in your Segment dashboard for confirmation.  +For tools that support this, if you have enabled "Track Attribution Data" in your Segment dashboard, our integration listens to the attribution tool’s SDK for a change in attribution state. **Note**: Not all device-mode attribution tools offer "Track Attribution Data" functionality.  See the settings section for a particular tool in your Segment dashboard for confirmation.  When there is a change in attribution state, the integration code triggers an **Install Attributed** call to be sent back to your Segment source (and on to all other enabled destinations - in device and cloud mode).   diff --git a/connections/destinations/catalog/firebase/index.md b/connections/destinations/catalog/firebase/index.md index d218d69f31..f07737af13 100644 --- a/connections/destinations/catalog/firebase/index.md +++ b/connections/destinations/catalog/firebase/index.md @@ -10,7 +10,7 @@ To start sending data to Firebase Analytics from your Android project, you’ll - Register your mobile app with Firebase at `https://console.firebase.google.com` -- Once your app is registered, you’ll be prompted to download a `google-services.json` file. Place this in your Application’s “app” folder. This file contains all necessary configurations and cannot be used across multiple apps. If you’re configuring Firebase for other apps, you should create a new view in your Firebase console and download a unique `google-services.json` file for each. +- Once your app is registered, you’ll be prompted to download a `google-services.json` file. Place this in your Application’s "app" folder. This file contains all necessary configurations and cannot be used across multiple apps. If you’re configuring Firebase for other apps, you should create a new view in your Firebase console and download a unique `google-services.json` file for each. ***Module-level build.gradle**: Add the Segment-Firebase SDK and apply the Google Services plugin at the end of the file: @@ -96,7 +96,7 @@ When you call `identify` Segment will map to the corresponding Firebase Analytic You can use these traits to create audiences and views to analyze your users’ behavior. -**Note**: Google prohibits sending PII to Firebase unless [“robust notice” is given to your app users](https://firebase.google.com/policies/analytics/). For iOS apps, you must include the iAD Framework to automatically collect the Age, Gender, and Interests Firebase properties. +**Note**: Google prohibits sending PII to Firebase unless ["robust notice" is given to your app users](https://firebase.google.com/policies/analytics/). For iOS apps, you must include the iAD Framework to automatically collect the Age, Gender, and Interests Firebase properties. Learn more about [Firebase's reporting dashboard here](https://support.google.com/firebase/answer/6317517?hl=en&ref_topic=6317489). @@ -174,7 +174,7 @@ Segment maps the followed Segment specced properties (left) to the corresponding ### Passing Revenue and Currency -Ecommerce events containing “revenue” or “total” must also include the appropriate ISO 4217 “currency” string for revenue data to populate to the Firebase dashboard. If a “currency” value is not included, Segment default to "USD". +Ecommerce events containing "revenue" or "total" must also include the appropriate ISO 4217 "currency" string for revenue data to populate to the Firebase dashboard. If a "currency" value is not included, Segment default to "USD". ```js Properties properties = new Properties() diff --git a/connections/destinations/catalog/flurry/index.md b/connections/destinations/catalog/flurry/index.md index c4cbc8574d..3cd40e6c89 100644 --- a/connections/destinations/catalog/flurry/index.md +++ b/connections/destinations/catalog/flurry/index.md @@ -12,8 +12,8 @@ This document was last updated on January 10, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Flurry” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Flurry" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Flurry "API Key" in Segment's Settings UI. You can retrieve this from your Flurry Admin > Apps > API Key. It should look like "4KKKGS3BAK4WW8WJ93DN". 4. Follow the instructions in the Github repos: [iOS SDK](https://github.com/segment-integrations/analytics-ios-integration-flurry) and [Android SDK](https://github.com/segment-integrations/analytics-android-integration-flurry). 5. Once the Segment library is integrated with your app, toggle Flurry on in your Segment UI. diff --git a/connections/destinations/catalog/foxmetrics/index.md b/connections/destinations/catalog/foxmetrics/index.md index 759de1c28f..81002e7ee9 100644 --- a/connections/destinations/catalog/foxmetrics/index.md +++ b/connections/destinations/catalog/foxmetrics/index.md @@ -10,8 +10,8 @@ This document was last updated on October 15, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “FoxMetrics” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "FoxMetrics" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your FoxMetrics `App ID` 4. When FoxMetrics in enabled in Segment, our CDN will update within 5-10 minutes, and FoxMetrics's javascript will be loaded asynchronously onto your page. Please remember to remove FoxMetrics's snippet from your page. diff --git a/connections/destinations/catalog/freshmarketer/index.md b/connections/destinations/catalog/freshmarketer/index.md index 8519bfdbf2..27e0acdbbc 100644 --- a/connections/destinations/catalog/freshmarketer/index.md +++ b/connections/destinations/catalog/freshmarketer/index.md @@ -14,7 +14,7 @@ _**NOTE:** The Freshmarketer Destination is currently in beta, which means that {% include content/connection-modes.md %} 1. From your Segment UI’s Destinations page click **Add Destination**. -2. Search for “Freshmarketer” in the Destinations Catalog and confirm the Source you’d like to connect to. +2. Search for "Freshmarketer" in the Destinations Catalog and confirm the Source you’d like to connect to. 3. Go to your Freshmarketer dashboard (Admin Settings > API Settings) and copy your API Key. 4. In the Freshmarketer settings in the Segment UI, paste your API Key. diff --git a/connections/destinations/catalog/fullstory/index.md b/connections/destinations/catalog/fullstory/index.md index aca10866ef..c49f76f778 100644 --- a/connections/destinations/catalog/fullstory/index.md +++ b/connections/destinations/catalog/fullstory/index.md @@ -9,8 +9,8 @@ This document was last updated on January 25, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “FullStory” within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "FullStory" within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. 3. Add your `FS Org` in the destination settings. You can find this in FullStory by navigating to `Settings` > `General` > and copying the value found on the line `window['_fs_org'] = 'fullstory_org_here';` 4. In about 5-10 minutes the CDN will be updated and FullStory's recording snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/gainsight-px/index.md b/connections/destinations/catalog/gainsight-px/index.md index 191d9659c2..2839da6390 100644 --- a/connections/destinations/catalog/gainsight-px/index.md +++ b/connections/destinations/catalog/gainsight-px/index.md @@ -14,8 +14,8 @@ This document was last updated on June 14, 2018. If you notice any gaps, outdate {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “Gainsight PX” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "Gainsight PX" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. To find your Gainsight PX key, log into Gainsight PX and navigate to Settings > Products > Web App. If you have not already entered the URL for your web application, do that and click the Generate button. The Tag Key is the value to the right of the URL value. Use the "Copy" button to copy the value to your clipboard. ![](images/TagKey.png) diff --git a/connections/destinations/catalog/gainsight/index.md b/connections/destinations/catalog/gainsight/index.md index 310ddbf0da..30b0d83dd5 100644 --- a/connections/destinations/catalog/gainsight/index.md +++ b/connections/destinations/catalog/gainsight/index.md @@ -13,7 +13,7 @@ This document was last updated on October 18, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for Gainsight within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Copy your Gainsight Access Key and paste it into to the Access Key field in your Segment settings for Gainsight. This key can be generated from the integrations page under the `admin` area in Gainsight. It should be 36 characters long, for reference. If you need more information, please visit the [relevant documentation provided by Gainsight](https://support.gainsight.com/Connectors/API_Integration/Generate_API_Access_Key). 4. Start sending events! diff --git a/connections/destinations/catalog/goedle/index.md b/connections/destinations/catalog/goedle/index.md index 34bdde93e5..72d4cdb213 100644 --- a/connections/destinations/catalog/goedle/index.md +++ b/connections/destinations/catalog/goedle/index.md @@ -11,8 +11,8 @@ This document was last updated on May 16, 2018. If you notice any gaps, outdated {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Goedle” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Goedle" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, enter your goedle.io app key which you received upon [sign up](https://go.goedle.io/signup "Sign up at goedle.io"). 4. After activating, goedle.io will start automatically collecting data from your website, mobile app, or game. However, it will take up to 24 hours for goedle.io to process this data and predict future user behavior - you will receive an email from goedle.io when your data is available. diff --git a/connections/destinations/catalog/google-tag-manager/index.md b/connections/destinations/catalog/google-tag-manager/index.md index 7f380ae077..773d6dab3a 100644 --- a/connections/destinations/catalog/google-tag-manager/index.md +++ b/connections/destinations/catalog/google-tag-manager/index.md @@ -11,8 +11,8 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Google Tag Manager” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Google Tag Manager" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment UI's destination settings, enter your Container ID (note: it should start with "GTM-"). You can find this in the Admin section of your [GTM dashboard](https://tagmanager.google.com/#/admin/). 4. GTM will be loaded on any pages where your Segment snippet is initialized and `analytics.page` gets called in client-side Javascript. Once you've turned on GTM through Segment, you can use Segment `track` events to populate the GTM `dataLayer`. diff --git a/connections/destinations/catalog/heap/index.md b/connections/destinations/catalog/heap/index.md index 8350b1ccfa..0a1d90e1e0 100644 --- a/connections/destinations/catalog/heap/index.md +++ b/connections/destinations/catalog/heap/index.md @@ -10,8 +10,8 @@ This document was last updated on January 29, 2018. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Heap” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Heap" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Heap "App ID" into the connection settings. 4. If you are using Heap via Segment's client-side `analytics.js` library, we asynchronously load Heap's Javascript library onto the page. As such, all native functionality of Heap, including auto-capturing of all events. diff --git a/connections/destinations/catalog/help-scout/index.md b/connections/destinations/catalog/help-scout/index.md index 37d1c1ce08..5699c123c1 100644 --- a/connections/destinations/catalog/help-scout/index.md +++ b/connections/destinations/catalog/help-scout/index.md @@ -10,7 +10,7 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for Help Scout within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Copy your Help Scout API key and paste it into to the API Key field in your Segment settings for Help Scout. You can find your API Key on the Help Scout API keys page by navigating from the [Help Scout Dashboard](https://secure.helpscout.net/). diff --git a/connections/destinations/catalog/hotjar/index.md b/connections/destinations/catalog/hotjar/index.md index 5ce30da06d..dbce3efb42 100644 --- a/connections/destinations/catalog/hotjar/index.md +++ b/connections/destinations/catalog/hotjar/index.md @@ -11,9 +11,9 @@ This document was last updated on April 28, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “Hotjar” within the Destinations Catalog and confirm the Javascript source you’d like to connect to. +2. Search for "Hotjar" within the Destinations Catalog and confirm the Javascript source you’d like to connect to. 3. Add your Hotjar Site ID - which you can find under Settings and Sites & Organizations in our Hotjar dashboard - to your Destination settings. It should be a whole number (e.g. 123456). diff --git a/connections/destinations/catalog/hubspot/index.md b/connections/destinations/catalog/hubspot/index.md index 8ce9acc04d..fb450213d9 100644 --- a/connections/destinations/catalog/hubspot/index.md +++ b/connections/destinations/catalog/hubspot/index.md @@ -11,8 +11,8 @@ This document was last updated on March 30, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “HubSpot” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "HubSpot" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. If you haven't already done so, add your API Key from [HubSpot](https://knowledge.hubspot.com/articles/kcs_article/integrations/how-do-i-get-my-hubspot-api-key) and drop into the "API Key" field within the Segment UI. 4. Navigate to the "Settings" page within the HubSpot UI to find your Hub ID and drop into the "Hub ID" field within the Segment UI. 5. When you activate the destination, our CDN will be updated in about 5-10 minutes and the HubSpot snippet will be initilized and begin recording data. diff --git a/connections/destinations/catalog/inspectlet/index.md b/connections/destinations/catalog/inspectlet/index.md index eb4157d57f..fd37a20c7b 100644 --- a/connections/destinations/catalog/inspectlet/index.md +++ b/connections/destinations/catalog/inspectlet/index.md @@ -10,8 +10,8 @@ This document was last updated on 20th June, 2018. If you notice any gaps, out-d {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “Inspectlet” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "Inspectlet" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Take your Inspectlet WID (website’s ID), you can find it after clicking the Get Install Code button for your site in your Inspectlet dashboard. It will appear near the beginning of your embed code snippet. It should be a series of numbers, like 9492461759. 4. Add the WID in the "Connection Settings" section in Segment. 5. Our CDN is updated within 5-10 minutes. Then our snippet will start asynchronously loading Inspectlet's tracker.js onto your page. This means you should remove Inspectlet's snippet from your page. diff --git a/connections/destinations/catalog/intercom/index.md b/connections/destinations/catalog/intercom/index.md index 72566cc22c..253f8bfa15 100644 --- a/connections/destinations/catalog/intercom/index.md +++ b/connections/destinations/catalog/intercom/index.md @@ -17,8 +17,8 @@ This document was last updated on January 18, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Intercom” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Intercom" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Authorize your Intercom account in Segment and select the Intercom Account you want to sync with Segment. You can choose which account to sync in the drop down menu in the top right. If you have opted to utilize our [server-side sources](https://segment.com/docs/sources/#server), we will begin passing data through our servers once you activate the Destination. For other libraries please continue reading below. 4. Find your "App ID" within the Intercom UI following [the instructions here](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id) or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like this: `9iefb489`. diff --git a/connections/destinations/catalog/iterable/index.md b/connections/destinations/catalog/iterable/index.md index ce4f905b3e..0d06ac6967 100644 --- a/connections/destinations/catalog/iterable/index.md +++ b/connections/destinations/catalog/iterable/index.md @@ -77,7 +77,7 @@ analytics.track("Order Completed", { ## Page -Calling `page` to track pageviews will register as a custom event within Iterable. If you have a page called “shoppingCart” the custom event will be called “shoppingCart page” within Iterable. +Calling `page` to track pageviews will register as a custom event within Iterable. If you have a page called "shoppingCart" the custom event will be called "shoppingCart page" within Iterable. If a user does not already exist in Iterable, calling `page` for a user event will add that user into the system. Be sure to pass in the `email` the first time you call page for a user, since Iterable keys users by `email`. After the first time, you can call page with `userId`. diff --git a/connections/destinations/catalog/kissmetrics/index.md b/connections/destinations/catalog/kissmetrics/index.md index e4cae63a61..e48066f1a3 100644 --- a/connections/destinations/catalog/kissmetrics/index.md +++ b/connections/destinations/catalog/kissmetrics/index.md @@ -11,9 +11,9 @@ This document was last updated on July 3, 2018. If you notice any gaps, out-date When you toggle on KISSmetrics in Segment, this is what happens: -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "KISSmetrics" within the Destinations Catalog and confirm the Source you’d like to connect to. -3. Drop in your KISSmetrics "API Key” into the connection settings. +3. Drop in your KISSmetrics "API Key" into the connection settings. 4. If you are using KISSmetrics via Segment’s client-side analytics.js library, we asynchronously load KISSmetrics Javascript library onto the page. This means you should remove KISSmetrics's snippet from your page. Your KISSmetrics source will start automatically collecting "Visited Site" events and [other automatically tracked events](http://support.kissmetrics.com/article/show/javascript-settings). ## Page diff --git a/connections/destinations/catalog/klaviyo/index.md b/connections/destinations/catalog/klaviyo/index.md index 9b8a4108ea..08a04b0a7c 100644 --- a/connections/destinations/catalog/klaviyo/index.md +++ b/connections/destinations/catalog/klaviyo/index.md @@ -16,8 +16,8 @@ This document was last updated on September 6, 2018. If you notice any gaps, out {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Navigate to your [Account > Settings > API Keys](https://www.klaviyo.com/account#api-keys-tab) in the Klaviyo's UI and copy your "API Key" into the Segment Settings UI. 5. **Note:** Private API Key is required to use the List API. You can find this by going to Klaviyo’s UI and clicking [Account > Settings > API Keys > Create API Key](https://www.klaviyo.com/account#api-keys-tab) in order to generate a Private API Key and copy it into the Segment Settings UI. diff --git a/connections/destinations/catalog/kochava/index.md b/connections/destinations/catalog/kochava/index.md index cbb13fcfb1..bd4cd6b8c5 100644 --- a/connections/destinations/catalog/kochava/index.md +++ b/connections/destinations/catalog/kochava/index.md @@ -15,7 +15,7 @@ This document was last updated on October 8, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} 1. If you have not already, create your app within the Kochava dashboard. Check out Kochava's documentation for information on [creating your app](http://support.kochava.com/create-manage-apps/create-edit-apps). -2. From your Segment UI’s Destinations page click on “Add Destination”. +2. From your Segment UI’s Destinations page click on "Add Destination". 3. Search for "Kochava" within the Destinations Catalog and confirm the Source you’d like to connect to. 4. In the Kochava app, grab your Kochava App GUID (Globally Unique Identifier) 5. Copy the Kochava GUID into the Segment Destinations Settings UI under "API key". diff --git a/connections/destinations/catalog/leanplum/index.md b/connections/destinations/catalog/leanplum/index.md index 8ab59e5e5b..2de9e7f20e 100644 --- a/connections/destinations/catalog/leanplum/index.md +++ b/connections/destinations/catalog/leanplum/index.md @@ -10,8 +10,8 @@ This document was last updated on January 29, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Leanplum” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Leanplum" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Navigate to your "App Settings" within the Leanplum UI and open up your "Keys & Settings" 4. Copy the "App ID" into the Segment Settings UI under "Leanplum Application ID" 5. We recommend creating 2 Leanplum Destinations, 1 for production and 1 for development. diff --git a/connections/destinations/catalog/mailchimp/index.md b/connections/destinations/catalog/mailchimp/index.md index f7a04aea4b..c6a1f0a59c 100644 --- a/connections/destinations/catalog/mailchimp/index.md +++ b/connections/destinations/catalog/mailchimp/index.md @@ -13,8 +13,8 @@ This document was last updated on May 08, 2018. If you notice any gaps, out-date {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “MailChimp” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "MailChimp" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your MailChimp "API key" into the connection settings. It is recommended that you create a brand new API key for the Segment destination. MailChimp restricts each API key to a maximum of 10 concurrent requests, so creating a dedicated one for Segment will ensure maximum throughput for outgoing calls. You can read more about API keys on [MailChimp's docs](http://kb.mailchimp.com/integrations/api-integrations/about-api-keys). 4. Drop in your MailChimp "Audience ID" into your connection settings. diff --git a/connections/destinations/catalog/mailjet/index.md b/connections/destinations/catalog/mailjet/index.md index 10d7d0aaf6..89a50aecec 100644 --- a/connections/destinations/catalog/mailjet/index.md +++ b/connections/destinations/catalog/mailjet/index.md @@ -5,7 +5,7 @@ This destination is maintained by Mailjet. For any issues with the destination, ## Getting Started -Navigate to the “App Connections” page* (Account -> App Connections) and click on the “Segment” destination block to find your Segment Authentication key. * If you do not see the App Connections page for any reason, please contact us at plugins@mailjet.com. Select a Contact list from the drop down menu that you wish to have Segment send contact property data to. +Navigate to the "App Connections" page* (Account -> App Connections) and click on the "Segment" destination block to find your Segment Authentication key. * If you do not see the App Connections page for any reason, please contact us at plugins@mailjet.com. Select a Contact list from the drop down menu that you wish to have Segment send contact property data to. Be sure and note the contact list id inside the field below the chosen list because you will need to paste it into your Segment account so Segment knows where to send the data to. diff --git a/connections/destinations/catalog/mammoth/index.md b/connections/destinations/catalog/mammoth/index.md index 6542786d3b..d28e8b5de2 100644 --- a/connections/destinations/catalog/mammoth/index.md +++ b/connections/destinations/catalog/mammoth/index.md @@ -100,7 +100,7 @@ Page calls will be sent to the webhook dataset you created earlier. You can filt If you haven’t had a chance to review our spec, please take a look to understand what the [Screen method](https://segment.com/docs/spec/screen/) does. An example call would look like: ``` -[[SEGAnalytics sharedAnalytics] screen:@ “Home”]; +[[SEGAnalytics sharedAnalytics] screen:@ "Home"]; ``` Screen calls will be sent to the webhook dataset you created earlier. You can filter this data into a different view after you have set up JSON extract pipelines. diff --git a/connections/destinations/catalog/marketo-v2/index.md b/connections/destinations/catalog/marketo-v2/index.md index 24ac8711e3..c8c0564e8a 100644 --- a/connections/destinations/catalog/marketo-v2/index.md +++ b/connections/destinations/catalog/marketo-v2/index.md @@ -215,7 +215,7 @@ You can do one of the following to prevent duplicate leads: | alex@email.com | ABC1234 | | natasha@email.com | XYZ9876 | -To upload a list to Marketo, when you are in Lead Database, click All Leads. Then click “New”, then “Import List” from the drop down. Select your CSV, then click “Next”. Make sure “Email Address” and “userId” are the Marketo Fields selected then click “Next”. Name your list or select a pre-existing list. Select “None” for Acquisition Program. Then Click “Import”. +To upload a list to Marketo, when you are in Lead Database, click All Leads. Then click "New", then "Import List" from the drop down. Select your CSV, then click "Next". Make sure "Email Address" and "userId" are the Marketo Fields selected then click "Next". Name your list or select a pre-existing list. Select "None" for Acquisition Program. Then Click "Import". ![](images/jBhuNezWWP.gif) @@ -234,7 +234,7 @@ There are a few necessary steps that have to be taken to Migrate from Marketo to 2. Two custom fields must be created in Marketo: userId and anonymousId. Check out [Getting Started](https://segment.com/docs/integrations/marketo-v2/#-2-you-must-create-a-user-id-and-an-anonymous-id-field-in-marketo-) for exact details on how to create these custom fields in Marketo. 3. `Track` calls must be mapped in your Destination settings. Our Marketo Destination sent `track` calls as a Munchkin Visit WebPage event in Marketo. In Marketo V2, we'll send your track calls to your Marketo Custom Activities. Detailed instructions [here](https://segment.com/docs/integrations/marketo-v2/#track). 4. If there are any custom Lead fields that you’d like sent to Marketo in your `Identify` calls, you must add them in your Destination settings. Detailed instructions [here](https://segment.com/docs/integrations/marketo-v2/#identify). -5. Update anything in Marketo that rely on the way V1 sends `.track()` events to be triggered by your custom activities. For example, our V1 Marketo destination sent track events as a “Visit Web Page” event with `/event/`. So if you a workflow that is triggered by a “Visit Web Page” event where the web page contains `/event/`, you'll have to swap out the "Visit Web Page" event trigger you have with your Custom Attribute Trigger. In the right side bar, click the "Custom" folder under "Triggers" and select the trigger that you set for your custom activity: +5. Update anything in Marketo that rely on the way V1 sends `.track()` events to be triggered by your custom activities. For example, our V1 Marketo destination sent track events as a "Visit Web Page" event with `/event/`. So if you a workflow that is triggered by a "Visit Web Page" event where the web page contains `/event/`, you'll have to swap out the "Visit Web Page" event trigger you have with your Custom Attribute Trigger. In the right side bar, click the "Custom" folder under "Triggers" and select the trigger that you set for your custom activity: ![](images/cPD4kP65buG+.png) diff --git a/connections/destinations/catalog/mixpanel/index.md b/connections/destinations/catalog/mixpanel/index.md index 4b9ee58450..b5883fe8ae 100644 --- a/connections/destinations/catalog/mixpanel/index.md +++ b/connections/destinations/catalog/mixpanel/index.md @@ -11,7 +11,7 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat 1. From your Segment UI’s Destinations page click on **Add Destination**. 2. Search for Mixpanel within the Destinations Catalog and confirm the Source you’d like to connect to. -3. Copy your Mixpanel “API Secret” and "Token", and paste them into the Connection Settings in Segment. +3. Copy your Mixpanel "API Secret" and "Token", and paste them into the Connection Settings in Segment. 4. Enable the destination to start sending your data to Mixpanel. ## Page diff --git a/connections/destinations/catalog/moengage/index.md b/connections/destinations/catalog/moengage/index.md index 6e294371b0..e48369d055 100644 --- a/connections/destinations/catalog/moengage/index.md +++ b/connections/destinations/catalog/moengage/index.md @@ -75,7 +75,7 @@ For more info refer to this [link](https://segment.com/docs/sources/mobile/ios/# ### Tracking Events -Event tracking is used to track user behaviour in an app. **track** lets you record the actions your users perform. Every action triggers i.e,“event”, which can also have associated attributes. +Event tracking is used to track user behaviour in an app. **track** lets you record the actions your users perform. Every action triggers i.e,"event", which can also have associated attributes. ```[[SEGAnalytics sharedAnalytics] track:@"Item Purchased" properties:@{ @"item": @"Sword of Heracles"}];``` diff --git a/connections/destinations/catalog/mouseflow/index.md b/connections/destinations/catalog/mouseflow/index.md index 4674f93ce1..3bd4275625 100644 --- a/connections/destinations/catalog/mouseflow/index.md +++ b/connections/destinations/catalog/mouseflow/index.md @@ -10,8 +10,8 @@ This document was last updated on April 28, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Mouseflow” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Mouseflow" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Site ID within the Segment Settings UI. You can find this in [your Mouseflow UI](http://help.mouseflow.com/knowledge_base/topics/how-do-i-find-my-mouseflow-site-id). 4. In about 5-10 minutes the CDN will be updated and Mouseflow snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/msg91/index.md b/connections/destinations/catalog/msg91/index.md index 7ceb033782..215172034e 100644 --- a/connections/destinations/catalog/msg91/index.md +++ b/connections/destinations/catalog/msg91/index.md @@ -16,9 +16,9 @@ _**NOTE:** The MSG91 Destination is currently in beta, which means that they are {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “MSG91” within the Destinations Catalog and confirm the Source you’d like to connect to. +2. Search for "MSG91" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in the "API Key" into your Segment Settings UI which you can find from your [MSG91 dashboard](https://control.msg91.com/signin/) in the API page using the ['API' option in the sidebar](https://help.msg91.com/article/177-where-can-i-find-my-authentication-key). It is recommended that you create a brand new API key for the Segment destination. diff --git a/connections/destinations/catalog/new-relic/index.md b/connections/destinations/catalog/new-relic/index.md index 2443d64484..90860e5aba 100644 --- a/connections/destinations/catalog/new-relic/index.md +++ b/connections/destinations/catalog/new-relic/index.md @@ -9,8 +9,8 @@ This document was last updated on August 29, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “New Relic” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "New Relic" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Insights [Account ID](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id) and your [Insert Key](https://docs.newrelic.com/docs/insights/insights-data-sources/custom-data/insert-custom-events-insights-api#register). 4. Once destination enabled we'll start forwarding your calls to New Relic. diff --git a/connections/destinations/catalog/outbound/index.md b/connections/destinations/catalog/outbound/index.md index 7ddd8cb607..3e672e7e71 100644 --- a/connections/destinations/catalog/outbound/index.md +++ b/connections/destinations/catalog/outbound/index.md @@ -16,7 +16,7 @@ Connect is supported on the client-side, server-side and on mobile. ## Identify -Connect needs to identify users and their data to track who we should message. Segment will pass your UserID and any traits that you store on that user to Connect. (Note: Segment refers to user data as “traits”; Connect refers to user data as “attributes”.) +Connect needs to identify users and their data to track who we should message. Segment will pass your UserID and any traits that you store on that user to Connect. (Note: Segment refers to user data as "traits"; Connect refers to user data as "attributes".) analytics.identify({ userId: '019mr8mf4r', diff --git a/connections/destinations/catalog/pendo/index.md b/connections/destinations/catalog/pendo/index.md index 6741129c72..e13606572e 100644 --- a/connections/destinations/catalog/pendo/index.md +++ b/connections/destinations/catalog/pendo/index.md @@ -12,8 +12,8 @@ This document was last updated on September 26, 2018. If you notice any gaps, ou {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin) > Basic Information > API Key. 4. In about 5-10 minutes the CDN will be updated and Pendo’s snippet will be initialized onto your page. This pulls in all page and click events without needing to make additional method calls. @@ -21,8 +21,8 @@ This document was last updated on September 26, 2018. If you notice any gaps, ou If you are implementing server-side, please follow the steps above to add Pendo continue with steps below to add a Webhook destination: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Webhooks” within the Destinations Catalog and confirm the Javascript Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Webhooks" within the Destinations Catalog and confirm the Javascript Source you’d like to connect to. 3. Add the following as your Webhook URL: `https://pendo-io.appspot.com/data/segmentio/YOUR_PENDO_API_KEY` and replace `YOUR_PENDO_API_KEY` with your actual Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin) > Basic Information > API Key. 4. Headers are not required in Webhook configuration. Once you’re done adding in your URL, save changes. 5. Using Track method also requires a setting enabled on your Pendo subscription. Please reach out to Pendo to enable this feature flag for your account. diff --git a/connections/destinations/catalog/perimeterx/index.md b/connections/destinations/catalog/perimeterx/index.md index dca43df404..429187b4fa 100644 --- a/connections/destinations/catalog/perimeterx/index.md +++ b/connections/destinations/catalog/perimeterx/index.md @@ -19,15 +19,15 @@ Here's how you can get started using PerimeterX! + Click the "Admin" tab inside the console. + Click "New Policy". -+ Rename your new policy by clicking the words “Policy name” in the new policy and then -click “Apply Changes”. ++ Rename your new policy by clicking the words "Policy name" in the new policy and then +click "Apply Changes". ![](https://cloudup.com/cg69lTztbJx+) ### 3. Configure your Application -+ Click the “Admin” tab inside the console. -+ Define your first application by clicking the button “Create a New Application” and filling ++ Click the "Admin" tab inside the console. ++ Define your first application by clicking the button "Create a New Application" and filling in the modal. + Select the policy that you would like to use (default is pxDefault_Policy and you should use the policy that you just created) diff --git a/connections/destinations/catalog/personyze/index.md b/connections/destinations/catalog/personyze/index.md index 880fcb6307..4a89dda8a6 100644 --- a/connections/destinations/catalog/personyze/index.md +++ b/connections/destinations/catalog/personyze/index.md @@ -14,7 +14,7 @@ _**NOTE:** Personyze is currently in beta, which means that they are still activ 1. From your Segment UI's Destinations page click on "Add Destination". 2. Search for "Personyze" within the Destinations Catalog and confirm the Source you'd like to connect to. 3. Drop in the "API Key" into your Segment Settings UI which you can find from your [Personyze dashboard](https://personyze.com/site/tracker/condition/index#cat=Account%20settings%2FMain%20settings%2FIntegrations/conditions) under Account Settings > Integrations > Segment > Get Keys -4. Once you’ve updated the API key in Segment, data from the source you selected will be shown right away in Personyze under “Manage Visitor Profiles”. +4. Once you’ve updated the API key in Segment, data from the source you selected will be shown right away in Personyze under "Manage Visitor Profiles". ## Identify diff --git a/connections/destinations/catalog/quanticmind/index.md b/connections/destinations/catalog/quanticmind/index.md index 9059fd57d8..f309b0d67b 100644 --- a/connections/destinations/catalog/quanticmind/index.md +++ b/connections/destinations/catalog/quanticmind/index.md @@ -9,7 +9,7 @@ This document was last updated on January 09, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. + 1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "QuanticMind" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `ClientID`, and `Domain` if provided, from QuanticMind account manager. 4. Under `Events` you can then map any necessary 'track' event/s to QuanticMind numbered event/s. Please note that unless mapped in the settings, no 'track' calls will be sent to QuanticMind. diff --git a/connections/destinations/catalog/quora-conversion-pixel/index.md b/connections/destinations/catalog/quora-conversion-pixel/index.md index c5ad1e404f..499da2edfc 100644 --- a/connections/destinations/catalog/quora-conversion-pixel/index.md +++ b/connections/destinations/catalog/quora-conversion-pixel/index.md @@ -10,8 +10,8 @@ This document was last updated on June 15th, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Quora” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Quora" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your Quora Conversion Pixel Key to your Destination settings. To get this you will need to do the following: i. Log into your [Quora Ads Manager Account](https://www.quora.com/ads/account). diff --git a/connections/destinations/catalog/refersion/index.md b/connections/destinations/catalog/refersion/index.md index f76c469cf4..eea0882c65 100644 --- a/connections/destinations/catalog/refersion/index.md +++ b/connections/destinations/catalog/refersion/index.md @@ -20,8 +20,8 @@ You have two options to connect - either automatically within your Refersion das ### Option 2 - Segment UI -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Refersion” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Refersion" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Once connected, you will be asked to input an API key - which can be found in your [Refersion dashboard](https://www.refersion.com/base/settings/integrations/api) - which is formatted as `publickey.secretkey`. You will need to click "Show" to obtain the "Secret Key" portion. ## Identify diff --git a/connections/destinations/catalog/salesforce-dmp/index.md b/connections/destinations/catalog/salesforce-dmp/index.md index 46ae14c59b..af8383974f 100644 --- a/connections/destinations/catalog/salesforce-dmp/index.md +++ b/connections/destinations/catalog/salesforce-dmp/index.md @@ -146,9 +146,9 @@ To collect a Segment property as an SFDMP `user attribute` instead, contact your SFDMP can split an attribute value into many individual values based on a delimiter. For example, say you have a property `colors` with a value `red,green,blue,yellow`. You can adjust your SFDMP settings so that it recognizes a comma as a delimiter for this attribute. That way, you can -create audience Segments based on individual attribute values such as “red”, -“green”, “blue” and “yellow” rather than on complete strings like -“red,green,blue,yellow”. +create audience Segments based on individual attribute values such as "red", +"green", "blue" and "yellow" rather than on complete strings like +"red,green,blue,yellow". To set up a custom delimiter, contact your Salesforce representative. diff --git a/connections/destinations/catalog/salesforce-marketing-cloud/index.md b/connections/destinations/catalog/salesforce-marketing-cloud/index.md index e505bb55bf..80d94d8fb0 100644 --- a/connections/destinations/catalog/salesforce-marketing-cloud/index.md +++ b/connections/destinations/catalog/salesforce-marketing-cloud/index.md @@ -30,7 +30,7 @@ You should now see a Summary page with a Components section. This section lists Segment will pass any traits you specify in an `identify` call through to the *Identify Data Extension* you specify in the Segment UI. You'll need to create this Data Extension manually in SMC's Contact Builder UI. When creating a Data Extension in SMC, you can set up as many or as few traits as you would like, but a good starting point for your schema is to include Segment's [standard identify traits][]. ### Set up your subdomain -Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters “mc” in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. +Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters "mc" in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. **If you do not set your subdomain, Segment will use the legacy V1 endpoint and your events can result in authentication errors.** diff --git a/connections/destinations/catalog/satismeter/index.md b/connections/destinations/catalog/satismeter/index.md index c1042cd673..cb5918758f 100644 --- a/connections/destinations/catalog/satismeter/index.md +++ b/connections/destinations/catalog/satismeter/index.md @@ -20,7 +20,7 @@ With SatisMeter you can: ## Get Started -To get started you need to sign up to SatisMeter, and click the green button “Enable with Segment”. This will link your SatisMeter project with your Segment project and enable the destination. +To get started you need to sign up to SatisMeter, and click the green button "Enable with Segment". This will link your SatisMeter project with your Segment project and enable the destination. !["Enable with segment" button](https://cloud.githubusercontent.com/assets/12846380/9251740/edd579ca-41d4-11e5-9ebe-732156cbdb2f.png) diff --git a/connections/destinations/catalog/sentry/index.md b/connections/destinations/catalog/sentry/index.md index 1104c64f26..c493d044cf 100644 --- a/connections/destinations/catalog/sentry/index.md +++ b/connections/destinations/catalog/sentry/index.md @@ -10,8 +10,8 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Sentry” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Sentry" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your "Public DSN" into the Sentry destination settings. 4. We’ll automatically initialize Sentry with your "Public DSN" upon loading analytics.js. 5. Sentry will automatically start tracking errors in your app's javascript. diff --git a/connections/destinations/catalog/simplereach/index.md b/connections/destinations/catalog/simplereach/index.md index 058ab55ad3..686e452fc2 100644 --- a/connections/destinations/catalog/simplereach/index.md +++ b/connections/destinations/catalog/simplereach/index.md @@ -10,7 +10,7 @@ This document was last updated on April 16, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “SimpleReach” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "SimpleReach" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, enter your SimpleReach PID which was given to you by the SimpleReach client services team. 4. In about 5-10 minutes the CDN will be updated and the SimpleReach snippet will be initialized onto your page and data will flow through to your SimpleReach Dashboard. diff --git a/connections/destinations/catalog/singular/index.md b/connections/destinations/catalog/singular/index.md index 11a3b414b9..8eba7f4dc0 100644 --- a/connections/destinations/catalog/singular/index.md +++ b/connections/destinations/catalog/singular/index.md @@ -24,7 +24,7 @@ This destination is maintained by Singular. For any issues with the destination, ## Install Attribution -Enable automatic tracking of lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) via initialization config parameters ([iOS](https://segment.com/docs/sources/mobile/ios/#application-lifecycle-tracking), [Android](https://segment.com/docs/sources/mobile/android/#step-2-initialize-the-client)) to track installs and sessions in Singular. The Singular “**session**” will be sent automatically by the integration as long as you are including the events above. +Enable automatic tracking of lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) via initialization config parameters ([iOS](https://segment.com/docs/sources/mobile/ios/#application-lifecycle-tracking), [Android](https://segment.com/docs/sources/mobile/android/#step-2-initialize-the-client)) to track installs and sessions in Singular. The Singular "**session**" will be sent automatically by the integration as long as you are including the events above. ## Apple Search Ads Attribution diff --git a/connections/destinations/catalog/slicingdice/index.md b/connections/destinations/catalog/slicingdice/index.md index 3a98a1dec2..9fd1faa9be 100644 --- a/connections/destinations/catalog/slicingdice/index.md +++ b/connections/destinations/catalog/slicingdice/index.md @@ -54,9 +54,9 @@ analytics.identify('userId123', { ``` Identify calls will be sent to SlicingDice using the following columns: -* `{source_name}-identifies-user-id`: contains the “userId” attribute of an Identify call -* `{source_name}-identifies-{attribute_name}`: contains the “traits” attributes of an Identify call, saving each one as an individual column -* `{source_name}-identifies-context-{attribute_name}`: contains the “context” attributes of an Identify call, saving each one as an individual column +* `{source_name}-identifies-user-id`: contains the "userId" attribute of an Identify call +* `{source_name}-identifies-{attribute_name}`: contains the "traits" attributes of an Identify call, saving each one as an individual column +* `{source_name}-identifies-context-{attribute_name}`: contains the "context" attributes of an Identify call, saving each one as an individual column ## Track @@ -69,9 +69,9 @@ analytics.track('Clicked Login Button') Track calls will be sent to SlicingDice using the following columns: -* `{source_name}-track-event`: contains the “event” attribute of a Track call -* `{source_name}-track-{attribute_name}`: contains the “properties” attributes of a Track call, saving each one as an individual column -* `{source_name}-track-context-{attribute_name}`: contains the “context” attributes of a Track call, saving each one as an individual column +* `{source_name}-track-event`: contains the "event" attribute of a Track call +* `{source_name}-track-{attribute_name}`: contains the "properties" attributes of a Track call, saving each one as an individual column +* `{source_name}-track-context-{attribute_name}`: contains the "context" attributes of a Track call, saving each one as an individual column *Observation: if your* `context` *attribute has nested attributes, your column names will follow this pattern:* `{source_name}-track-context-{attribute_name}{nested_attribute_name}` @@ -92,7 +92,7 @@ Group calls will be sent to SlicingDice using the following columns: * `{source_name}-groups-group-id`: contains the `groupID` attribute of a Group call * `{source_name}-groups-{attribute_name}`: contains the `traits` attributes of a Group call, saving each one as an individual column -* `{source_name}-groups-context-{attribute_name}`: contains the “context” attributes of a Group call, saving each one as an individual column +* `{source_name}-groups-context-{attribute_name}`: contains the "context" attributes of a Group call, saving each one as an individual column *Observation: Group calls will also be sent to SlicingDice using the following [Account](https://segment.com/docs/destinations/#warehouse-schemas) columns that holds the latest state of a group.* * `{source_name}-accounts-group-id`: contains the `groupId` attribute of a Group call diff --git a/connections/destinations/catalog/snapengage/index.md b/connections/destinations/catalog/snapengage/index.md index 5bd173b0a5..819d36ee22 100644 --- a/connections/destinations/catalog/snapengage/index.md +++ b/connections/destinations/catalog/snapengage/index.md @@ -10,9 +10,9 @@ This document was last updated on October 22, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “SnapEngage” within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind that our "SnapEngage" destination is only compatible with our client-side [analytics.js](https://segment.com/docs/sources/website/analytics.js/) library. +2. Search for "SnapEngage" within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind that our "SnapEngage" destination is only compatible with our client-side [analytics.js](https://segment.com/docs/sources/website/analytics.js/) library. 3. Add your SnapEngage `Widget ID` to your destination settings in Segment. You can find the `Widget ID` in your SnapEngage Javascript snippet. It will look something like this: 0c739ebb-2016-44a0-b1da-a5b5eb272474. Alternatively, the `Widget ID` can also be found under the _Advanced Widget ID_ section of the _Get the Code_ tab in the Admin Dashboard when logged in to SnapEngage. diff --git a/connections/destinations/catalog/sparkpage/index.md b/connections/destinations/catalog/sparkpage/index.md index 0a6267c6c7..781ef19a1f 100644 --- a/connections/destinations/catalog/sparkpage/index.md +++ b/connections/destinations/catalog/sparkpage/index.md @@ -5,7 +5,7 @@ This destination is maintained by SparkPage. ## Getting Started -Once the Segment library is integrated with your server, toggle SparkPage on in your Segment destinations, and add your API key which you can find in the SparkPage Dashboard under “Settings” +Once the Segment library is integrated with your server, toggle SparkPage on in your Segment destinations, and add your API key which you can find in the SparkPage Dashboard under "Settings" The Segment SparkPage destination is 100% handled through our servers, so you don't need to bundle their iOS or Android SDKs. Your Segment SDK will be enough. diff --git a/connections/destinations/catalog/trackier/index.md b/connections/destinations/catalog/trackier/index.md index a433087e1f..32c680f064 100644 --- a/connections/destinations/catalog/trackier/index.md +++ b/connections/destinations/catalog/trackier/index.md @@ -20,7 +20,7 @@ _**NOTE:** The Trackier Destination is currently in beta, which means that they If you haven't had a chance to review our spec, please take a look to understand what the [Track method](https://segment.com/docs/spec/track/) does. An example call would look like: ``` - analytics.track(“Item Sold”, { + analytics.track("Item Sold", { click_id: '1233443', sale_amount: $12.54, txn_id: 'random', diff --git a/connections/destinations/catalog/tune/index.md b/connections/destinations/catalog/tune/index.md index bb2b6e0257..be0c396c7e 100644 --- a/connections/destinations/catalog/tune/index.md +++ b/connections/destinations/catalog/tune/index.md @@ -14,8 +14,8 @@ This document was last updated on May 8, 2018. If you notice any gaps, outdated {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “TUNE” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "TUNE" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your TUNE Advertiser ID in the Segment Settings UI from [your TUNE Dashboard](https://developers.tune.com/sdk/finding-your-advertiser-id-and-conversion-key/). 4. In your TUNE account, ensure that you have created a new app by navigating to Applications > Apps > Add A New App. 5. Depending on library you've installed, please follow the additional steps below to finish setting up! diff --git a/connections/destinations/catalog/tv-squared/index.md b/connections/destinations/catalog/tv-squared/index.md index e8a7558487..fe4d2ee8c2 100644 --- a/connections/destinations/catalog/tv-squared/index.md +++ b/connections/destinations/catalog/tv-squared/index.md @@ -10,9 +10,9 @@ This document was last updated on April 20th, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “TV Squared” within the Destinations Catalog and confirm the Javascript source you’d like to connect to. +2. Search for "TV Squared" within the Destinations Catalog and confirm the Javascript source you’d like to connect to. 3. Add your TV Squared Brand ID and Client ID to your Segment Settings UI. You can find this within your TV Squared dashboard. diff --git a/connections/destinations/catalog/userlike/index.md b/connections/destinations/catalog/userlike/index.md index ef52cc4bad..ec6e3db281 100644 --- a/connections/destinations/catalog/userlike/index.md +++ b/connections/destinations/catalog/userlike/index.md @@ -10,8 +10,8 @@ This document was last updated on October 22, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Userlike” within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind, that the Userlike destination is only compatible with our Javascript source. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Userlike" within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind, that the Userlike destination is only compatible with our Javascript source. 3. Add your Secret Key to your destination settings in Segment - your Secret Key can be found under Config > Install > Secret in your Userlike dashboard. It should look something like this: 8a3707ab96df8354253c158a25f908b84dc655c27d5828a1a97d99f08bfba6f4. 4. Once you enable the destination, our CDN is updated within 5-10 minutes. Analytics.js will start asynchronously loading Userlike's javascript onto your page. Please remember to remove Userlike's snippet from your page. diff --git a/connections/destinations/catalog/userlist/index.md b/connections/destinations/catalog/userlist/index.md index 3c7e68fff0..2fd7f0ce72 100644 --- a/connections/destinations/catalog/userlist/index.md +++ b/connections/destinations/catalog/userlist/index.md @@ -13,8 +13,8 @@ _**NOTE:** The Userlist.io Destination is currently in beta, which means that th {% include content/connection-modes.md %} 1. From your Segment UI's Destinations page click on "Add Destination". -2. Search for “Userlist” within the Destinations Catalog and confirm the Source you'd like to connect to. -3. Drop in the “Push API Key" into your Segment Settings UI which you can find from your [Userlist.io Push API settings](https://app.userlist.io/settings/push). +2. Search for "Userlist" within the Destinations Catalog and confirm the Source you'd like to connect to. +3. Drop in the "Push API Key" into your Segment Settings UI which you can find from your [Userlist.io Push API settings](https://app.userlist.io/settings/push). _**NOTE:** The Userlist.io Destination does not support tracking of anonymous users, so please make sure to call `identify` before calling `track`. If you do call `track` on unidentified users, you will receive a 400 error which you can disregard if it was intentional._ diff --git a/connections/destinations/catalog/visual-website-optimizer/index.md b/connections/destinations/catalog/visual-website-optimizer/index.md index c372ae73d8..81ded4d994 100644 --- a/connections/destinations/catalog/visual-website-optimizer/index.md +++ b/connections/destinations/catalog/visual-website-optimizer/index.md @@ -19,8 +19,8 @@ Because the VWO destination needs to be on the page right away, there are two wa Additionaly, to enable the destination please follow these instructions: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Visual Web Optimizer” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Visual Web Optimizer" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Toggle the destination on! @@ -75,10 +75,10 @@ analytics.track('Order Completed', { If you are using VWO together with Google Analytics, you can enable this setting to add the `nonInteraction` flag to your `Experiment Viewed` track events. This can help with low bounce rates. ### Library Tolerance -The maximum amount of time (in milliseconds) to wait for VWO’s full library to be downloaded before simply displaying your original page. This setting is only effective if “Use Async Smart Code” is set to “true”. +The maximum amount of time (in milliseconds) to wait for VWO’s full library to be downloaded before simply displaying your original page. This setting is only effective if "Use Async Smart Code" is set to "true". ### Settings Tolerance -The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page. This setting is only effective if “Use Async Smart Code” is set to “true”. +The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page. This setting is only effective if "Use Async Smart Code" is set to "true". ## Use Existing JQuery -If your page already includes JQuery, you can set this to “true”. Otherwise, VWO will include JQuery onto the page for you. VWO needs JQuery on the page to function correctly. This setting is only effective if “Use Async Smart Code” is enabled. +If your page already includes JQuery, you can set this to "true". Otherwise, VWO will include JQuery onto the page for you. VWO needs JQuery on the page to function correctly. This setting is only effective if "Use Async Smart Code" is enabled. diff --git a/connections/destinations/catalog/webhooks/index.md b/connections/destinations/catalog/webhooks/index.md index 84e791352d..1d043c7428 100644 --- a/connections/destinations/catalog/webhooks/index.md +++ b/connections/destinations/catalog/webhooks/index.md @@ -9,8 +9,8 @@ This document was last updated on January 28, 2018. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Webhooks” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Webhooks" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Specify up to five different Webhook URLs, you would like to forward data to. 4. Add in any header values you would like to add to the HTTP requests 5. If you require authentication, add in a [shared secret](https://segment.com/docs/destinations/webhooks/#authentication). diff --git a/connections/destinations/catalog/wishpond/index.md b/connections/destinations/catalog/wishpond/index.md index f119ca01ce..144c66d7b7 100644 --- a/connections/destinations/catalog/wishpond/index.md +++ b/connections/destinations/catalog/wishpond/index.md @@ -11,7 +11,7 @@ Our Wishpond destination code is open sourced on Github. Feel free to check it o Wishpond works with our client-side javascript library: Analytics.js. -From your Segment Destinations page click on Wishpond. Drop in your Merchant ID and Trackey Key from Wishpond’s [“API Keys” dialog](https://www.wishpond.com/central/welcome?api_keys=true). These are also found in your Wishpond Account in the "API Keys" dropdown under your account name in the top right corner. +From your Segment Destinations page click on Wishpond. Drop in your Merchant ID and Trackey Key from Wishpond’s ["API Keys" dialog](https://www.wishpond.com/central/welcome?api_keys=true). These are also found in your Wishpond Account in the "API Keys" dropdown under your account name in the top right corner. We’ll automatically initialize Wishpond’s Tracking Code with your Tracking Key and Merchant ID upon loading Analytics.js. @@ -73,7 +73,7 @@ To more details how Wishpond's identify works please visit [Wishpond API Docs: # ### Destination is not working properly -Make sure you have copied the right keys from Wishpond’s [“API Keys” dialog](https://www.wishpond.com/central/welcome?api_keys=true), this destination will need `Merchant ID` and `Tracking Key`. +Make sure you have copied the right keys from Wishpond’s ["API Keys" dialog](https://www.wishpond.com/central/welcome?api_keys=true), this destination will need `Merchant ID` and `Tracking Key`. [Analytics.js]: https://segment.com/docs/libraries/analytics.js/ [ci-link]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond diff --git a/connections/destinations/catalog/wootric/index.md b/connections/destinations/catalog/wootric/index.md index dbe50cb00a..dbbc60a5bf 100644 --- a/connections/destinations/catalog/wootric/index.md +++ b/connections/destinations/catalog/wootric/index.md @@ -11,8 +11,8 @@ This document was last updated on October 15, 2018. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your {{integration.name}} "Account Token" in Segment's Settings UI. You can retrieve this from your {{integration.name}} Settings > Your unique Account Token is. It should look like "NPS-XXXXXXXX". 4. If you're using Segment's client-side `analytics.js` library, we asynchronously load {{integration.name}}'s Javascript library onto the page and the CDN will be updated in 5-10 minutes. diff --git a/connections/destinations/catalog/yandex-metrica/index.md b/connections/destinations/catalog/yandex-metrica/index.md index 4afc78b3bf..6d91d914f2 100644 --- a/connections/destinations/catalog/yandex-metrica/index.md +++ b/connections/destinations/catalog/yandex-metrica/index.md @@ -9,8 +9,8 @@ This document was last updated on January 18, 2019. If you notice any gaps, outd ## Getting Started -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Yandex.Metrica” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Yandex.Metrica" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Enter your Counter ID that you can find in your Yandex.Metrica UI navigating to Settings > Tag. 4. In about 5-10 minutes the CDN will be updated and Yandex.Metrica’s snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/zendesk/index.md b/connections/destinations/catalog/zendesk/index.md index 01676f232b..9b866a960e 100644 --- a/connections/destinations/catalog/zendesk/index.md +++ b/connections/destinations/catalog/zendesk/index.md @@ -12,8 +12,8 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Zendesk” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Zendesk" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. There are two ways to authenticate your Zendesk account with Segment: * Use the standard email and password you use to Sign In to your Zendesk account. In the Zendesk settings, add your email in the **Email** setting and your password in the **Password** setting. * Use Zendesk OAuth with a unique token. Get the corresponding token from your Zendesk account: **Settings > Channels > API** and under the Settings Tab choose the corresponding token from the "Active API Tokens" list. In the Zendesk settings, add your `email/token` in the **Email** setting (i.e. `peter@intech.com/token` - use the actual word token in your email address) and add the actual token in the **Password** setting. diff --git a/connections/destinations/catalog/zopim/index.md b/connections/destinations/catalog/zopim/index.md index b067c6e1a2..8e4e110407 100644 --- a/connections/destinations/catalog/zopim/index.md +++ b/connections/destinations/catalog/zopim/index.md @@ -13,8 +13,8 @@ This document was last updated on June 11th, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Zopim” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Zopim" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your Zopim ID to your Destination Settings. If you are using the `Chat Widget`, you can find your Zopim ID in the widget script itself. See example below: ``` diff --git a/connections/sources/catalog/cloud-apps/activecampaign/index.md b/connections/sources/catalog/cloud-apps/activecampaign/index.md index dad3cf975a..79495a56ae 100644 --- a/connections/sources/catalog/cloud-apps/activecampaign/index.md +++ b/connections/sources/catalog/cloud-apps/activecampaign/index.md @@ -17,24 +17,24 @@ If you have previously enabled sending email events via the ActiveCampaign desti 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `ActiveCampaign` for nickname and `activecampaign` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for ActiveCampaign.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for ActiveCampaign.** Copy this write key.  5. In your ActiveCampaign account, navigate to http://YOURACCOUNT.activehosted.com/apps/#/segment -6. Scroll to the bottom of the page to where it says “Send email events data from ActiveCampaign to Segment.” +6. Scroll to the bottom of the page to where it says "Send email events data from ActiveCampaign to Segment." -7. Click the “OFF” toggle. +7. Click the "OFF" toggle. ![off](https://cldup.com/QLv153k6CU.png) -8. This will open a modal for you to enter your Segment.com write key. Enter your write key and click “Connect”. +8. This will open a modal for you to enter your Segment.com write key. Enter your write key and click "Connect". -9. The toggle will now say “ON”. +9. The toggle will now say "ON". ![on](https://cldup.com/cv4rU1Ivg5.png) 10. Once the first event occurs, you’ll always see the last event that occurred in this box. ![last event](https://cldup.com/5OZGDQD3wB.png) -11. If you ever need to re-enter your Segment write key, just click “Re-enter your Segment write key.” +11. If you ever need to re-enter your Segment write key, just click "Re-enter your Segment write key." 12. In Segment, click into your ActiveCampaign Source in `segment.com//sources`. From there you’ll be able to add Destinations where you want to see email events. diff --git a/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md b/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md index b2d532064b..0a62fbf5df 100644 --- a/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md +++ b/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md @@ -31,8 +31,8 @@ Segment `identify` events. ![Add your Segment writeKey](./images/amplitude-segment-writekey.png) 7. If you would like to set up automated export on an hourly or daily basis, - you can use Amplitude's Cohort Sync feature. Click “Advanced Preferences” - and select “Segment” as the integration. + you can use Amplitude's Cohort Sync feature. Click "Advanced Preferences" + and select "Segment" as the integration. 8. From your Segment account, click into your Amplitude Cohorts Source, and you’ll be able to add other downstream destinations where you want to see your Behavioral Cohort data. diff --git a/connections/sources/catalog/cloud-apps/autopilothq/index.md b/connections/sources/catalog/cloud-apps/autopilothq/index.md index 816084385f..d47ddb8936 100644 --- a/connections/sources/catalog/cloud-apps/autopilothq/index.md +++ b/connections/sources/catalog/cloud-apps/autopilothq/index.md @@ -13,7 +13,7 @@ This document was last updated on October 19, 2018. If you notice any gaps, outd ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for AutopilotHQ within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup flow to "Add Source". The nickname is a label used in the Segment interface, and Segment creates a related schema name, which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Sign in to your Autopilot account and visit the [Segment destination](https://app.autopilothq.com/#settings/app-connections/segment-sync) to connect. diff --git a/connections/sources/catalog/cloud-apps/blueshift/index.md b/connections/sources/catalog/cloud-apps/blueshift/index.md index b88c8b84f6..df0a3ff88b 100644 --- a/connections/sources/catalog/cloud-apps/blueshift/index.md +++ b/connections/sources/catalog/cloud-apps/blueshift/index.md @@ -13,7 +13,7 @@ In your favorite BI or analytics tool, you’ll be able to analyze your email ca 1. From your workspace’s segment.com//sources page, click Add source. 2. Choose Blueshift. 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like Blueshift for nickname and Blueshift for the schema name. -4. The next page (“Overview”) will surface your Segment write key for Blueshift. Copy this write key. +4. The next page ("Overview") will surface your Segment write key for Blueshift. Copy this write key. 5. To finish the setup, you’ll have to go into your Blueshift account and enter this Segment write key in their destinations settings. Find the right place in Blueshift by clicking Account > Webhooks: ![](https://i.gyazo.com/39c3955d4ea74e0a8ff07ef6651d4b30.png) @@ -136,7 +136,7 @@ Below is a table of properties that are sent for the events above: ## UserId -Blueshift sends their `customer_id` associated with the message recipient as the top level `userId` field. Additionally, we will also send “email” and “blueshift_user_uuid” under `context.traits`. +Blueshift sends their `customer_id` associated with the message recipient as the top level `userId` field. Additionally, we will also send "email" and "blueshift_user_uuid" under `context.traits`. ## Send Data to Blueshift diff --git a/connections/sources/catalog/cloud-apps/braze/index.md b/connections/sources/catalog/cloud-apps/braze/index.md index 8f6aabb99e..77fc4b6591 100644 --- a/connections/sources/catalog/cloud-apps/braze/index.md +++ b/connections/sources/catalog/cloud-apps/braze/index.md @@ -13,7 +13,7 @@ In your favorite BI or analytics tool, you’ll be able to analyze your mobile, 1. From your workspace Overview page, click Add Source. 2. Choose Braze 3. Give the Source a name. The name will be used to identify this source within your workspace. You can name it however you’d like, but we recommend sticking to something that reflects the Source itself, like Braze. -4. The next page “Overview” will surface your Segment write key for Braze. Copy this write key. +4. The next page "Overview" will surface your Segment write key for Braze. Copy this write key. 5. To finish the setup, you need to activate "Currents" in Braze which requires reaching out to Braze Support or your Customer Support Manager. Braze Currents is only available in select Braze packages and cannot be configured within Braze without assistance from your Braze Customer Success representative. diff --git a/connections/sources/catalog/cloud-apps/chatlio/index.md b/connections/sources/catalog/cloud-apps/chatlio/index.md index 579bdfc57d..a01decc007 100644 --- a/connections/sources/catalog/cloud-apps/chatlio/index.md +++ b/connections/sources/catalog/cloud-apps/chatlio/index.md @@ -10,7 +10,7 @@ Chatlio is a live chat tool that allows you to talk to your customers through yo 1. From your workspace’s `segment.com//sources` page, click Add source. 2. Choose Chatlio. 3. Give the Source a name. The name will be used to identify this source within your workspace. You can name it however you’d like, but we recommend sticking to something that reflects the Source itself, like Chatlio. -4. The next page “Overview” will surface your Segment write key for Chatlio. Copy this write key. +4. The next page "Overview" will surface your Segment write key for Chatlio. Copy this write key. 5. To finish the setup, you’ll have to go into your [Chatlio dashboard](https://chatlio.com/app/#/login) and enter the Segment write key in the settings towards the bottom of the page. 6. Now when you go back to Segment, click into your Chatlio Source and you’ll be able to add other downstream Destinations where you want to see live chat events. diff --git a/connections/sources/catalog/cloud-apps/customer.io/index.md b/connections/sources/catalog/cloud-apps/customer.io/index.md index ba83e06daa..3b37bae96d 100644 --- a/connections/sources/catalog/cloud-apps/customer.io/index.md +++ b/connections/sources/catalog/cloud-apps/customer.io/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Customer.io destinat 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Customerio` for nickname and `customerio` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Customer.io.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Customer.io.** Copy this write key.  5. To finish the setup, you’ll have to go into your Customer.io account and enter this Segment write key in their integrations settings. Find the right place in Customer.io by clicking Settings > Integrations > Segment. diff --git a/connections/sources/catalog/cloud-apps/delighted/index.md b/connections/sources/catalog/cloud-apps/delighted/index.md index 5242ec5565..b937e79529 100644 --- a/connections/sources/catalog/cloud-apps/delighted/index.md +++ b/connections/sources/catalog/cloud-apps/delighted/index.md @@ -12,7 +12,7 @@ This document was last updated on October 19, 2018. If you notice any gaps, outd ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for Delighted within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup steps to "Add Source". The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be anything, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Sign in to your Delighted account and visit the [Segment destination](https://delighted.com/integrations/segment) to connect. diff --git a/connections/sources/catalog/cloud-apps/drip/index.md b/connections/sources/catalog/cloud-apps/drip/index.md index 83ed21118c..5a0e08f5e9 100644 --- a/connections/sources/catalog/cloud-apps/drip/index.md +++ b/connections/sources/catalog/cloud-apps/drip/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Drip destination dur 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Drip` for nickname and `drip` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Drip.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Drip.** Copy this write key.  5. To finish the setup, you’ll have to go into your Drip account and enter this Segment write key in their integrations settings. Find the right place in Drip by clicking Settings > Integrations > Segment. diff --git a/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md b/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md index 69c259c6fa..2202cb4cb5 100644 --- a/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md +++ b/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md @@ -15,7 +15,7 @@ _**NOTE:** Facebook Lead Ads is currently in beta and this doc was last updated ## Getting Started 1. Set up a Facebook Lead Ad campaign if you haven’t already. Instructions on how to do so are [here](https://www.facebook.com/business/help/1462876307360828). -2. Search for "Facebook Lead Ads” within the Sources Catalog and confirm by clicking "Connect" +2. Search for "Facebook Lead Ads" within the Sources Catalog and confirm by clicking "Connect" 3. Give the source a name. The name is a label used in the Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself, like Facebook Lead Ads or Facebook Lead Ads Prod.  4. Click Create And Continue then Connect to OAuth into Facebook. 5. Select which accounts you would like to sync (you may change this selection later). diff --git a/connections/sources/catalog/cloud-apps/factual-engine/index.md b/connections/sources/catalog/cloud-apps/factual-engine/index.md index 5d139183bb..63cfa09531 100644 --- a/connections/sources/catalog/cloud-apps/factual-engine/index.md +++ b/connections/sources/catalog/cloud-apps/factual-engine/index.md @@ -4,7 +4,7 @@ beta: true --- ## How Engine Works -Installing the Engine SDK in your app enables you to gather and analyze information about your users’ location. Engine caches the relevant portion of Factual’s Global Places data on the device to determine where the user is, beyond raw location. Engine needs device location data in order to work and will use whatever location permissions your app has authorized. You can also set custom rules to trigger “actions” like push notifications or emails. +Installing the Engine SDK in your app enables you to gather and analyze information about your users’ location. Engine caches the relevant portion of Factual’s Global Places data on the device to determine where the user is, beyond raw location. Engine needs device location data in order to work and will use whatever location permissions your app has authorized. You can also set custom rules to trigger "actions" like push notifications or emails. The Factual Engine Source is a cloud-based event source. You simply include, configure, and initialize the Engine SDK as you normally would, and then add only a few lines of code to trigger correctly formatted events to Segment in response to your dynamic triggers and actions. This event data then flows seamlessly to your downstream Segment Destinations. Once the Factual Engine Source is enabled, any Segment Destination that can accept server-to-server data can accept data from Factual Engine. The data is also automatically streamed into your next warehouse sync. The data generated from the Factual Engine can also be easily combined with other Source data collected via Segment without any additional development work on your end. diff --git a/connections/sources/catalog/cloud-apps/iterable/index.md b/connections/sources/catalog/cloud-apps/iterable/index.md index 5d6cda8734..cc9160d982 100644 --- a/connections/sources/catalog/cloud-apps/iterable/index.md +++ b/connections/sources/catalog/cloud-apps/iterable/index.md @@ -22,7 +22,7 @@ If you have previously enabled sending email events via the Iterable destination ![](images/Iterable2.png) -4. The next page (“Overview”) will surface your **Segment write key for Iterable.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Iterable.** Copy this write key.  ![](images/Iterable3.png) diff --git a/connections/sources/catalog/cloud-apps/klaviyo/index.md b/connections/sources/catalog/cloud-apps/klaviyo/index.md index da20fdd1cc..4f6df62e28 100644 --- a/connections/sources/catalog/cloud-apps/klaviyo/index.md +++ b/connections/sources/catalog/cloud-apps/klaviyo/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Klaviyo destination 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Klaviyo` for nickname and `klaviyo` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Klaviyo.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Klaviyo.** Copy this write key.  5. To finish the setup, you’ll have to go into your Klaviyo account and enter this Segment write key in their integrations settings. Find the right place in Klaviyo by clicking [Integrations > Segment](https://www.klaviyo.com/integration/segment_io). diff --git a/connections/sources/catalog/cloud-apps/klenty/index.md b/connections/sources/catalog/cloud-apps/klenty/index.md index 22ef2f398d..dab2c3936d 100644 --- a/connections/sources/catalog/cloud-apps/klenty/index.md +++ b/connections/sources/catalog/cloud-apps/klenty/index.md @@ -11,7 +11,7 @@ _**NOTE:** The Klenty Source is currently in beta, which means that they are sti ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for "Klenty" within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup flow to "Add Source". The nickname is a label used in the Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Copy the Write key from the Segment UI and log in to your Klenty account - navigate to Settings > Integrations > Segment Integration and paste the key to connect. diff --git a/connections/sources/catalog/cloud-apps/looker/index.md b/connections/sources/catalog/cloud-apps/looker/index.md index 5a777e8195..6145519c04 100644 --- a/connections/sources/catalog/cloud-apps/looker/index.md +++ b/connections/sources/catalog/cloud-apps/looker/index.md @@ -11,7 +11,7 @@ From Segment's end, you will need to create a Looker source, and copy your write Using this Source, Looker will send Look (query) results into Segment as `identify` calls. This is the only API method that Looker sends to Segment. Any user trait that you include as a column in your Look will be included as a user trait on these identify call. -Note: When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. “churn risk”) and that trait already exists in your tools, syncing the user profile to the downstream tool will override the existing trait value with the new one. +Note: When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool will override the existing trait value with the new one. Below is an example of a cohort of users in Looker who have been active on toastmates.com (example website) at least once in the last 30 days. diff --git a/connections/sources/catalog/cloud-apps/mailjet/index.md b/connections/sources/catalog/cloud-apps/mailjet/index.md index 18954578e0..02c5cf3702 100644 --- a/connections/sources/catalog/cloud-apps/mailjet/index.md +++ b/connections/sources/catalog/cloud-apps/mailjet/index.md @@ -17,7 +17,7 @@ If you have previously enabled sending email events via the Mailjet destination 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Mailjet` for nickname and `Mailjet` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Mailjet.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Mailjet.** Copy this write key.  5. To finish the setup, you’ll have to go into your Mailjet account and enter this Segment write key in their integrations settings. Find the right place in Mailjet by clicking App Connections > Segment. diff --git a/connections/sources/catalog/cloud-apps/mandrill/index.md b/connections/sources/catalog/cloud-apps/mandrill/index.md index 0ca99dad95..0e31cb11d1 100644 --- a/connections/sources/catalog/cloud-apps/mandrill/index.md +++ b/connections/sources/catalog/cloud-apps/mandrill/index.md @@ -32,7 +32,7 @@ Take your company’s email analysis to the next level by **adding Mandrill as a ### Streaming -The Mandrill source is comprised only of a streaming component which listens in real time for inbound webhooks from [Mandrill’s Webhooks](https://mandrill.zendesk.com/hc/en-us/articles/205583217-Introduction-to-Webhooks) and batches the events to be uploaded on your next warehouse flush. These events are only ever appended to your warehouse. Since Mandrill is strictly used for transactional emails triggered directly by API calls, there are no “dimensional” concepts in their data model that would require any additional components. +The Mandrill source is comprised only of a streaming component which listens in real time for inbound webhooks from [Mandrill’s Webhooks](https://mandrill.zendesk.com/hc/en-us/articles/205583217-Introduction-to-Webhooks) and batches the events to be uploaded on your next warehouse flush. These events are only ever appended to your warehouse. Since Mandrill is strictly used for transactional emails triggered directly by API calls, there are no "dimensional" concepts in their data model that would require any additional components. ## Collections diff --git a/connections/sources/catalog/cloud-apps/nudgespot/index.md b/connections/sources/catalog/cloud-apps/nudgespot/index.md index 6db8fb3539..184dc60672 100644 --- a/connections/sources/catalog/cloud-apps/nudgespot/index.md +++ b/connections/sources/catalog/cloud-apps/nudgespot/index.md @@ -17,7 +17,7 @@ If you have previously enabled sending email events via the Nudgespot destinatio 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Nudgespot` for nickname and `nudgespot` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Nudgespot.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Nudgespot.** Copy this write key.  5. To finish the setup, you’ll have to go into your Nudgespot account and enter this Segment write key in their integrations settings. Find the right place in Nudgespot in Setup > Send Email Events to Segment.com. diff --git a/connections/sources/catalog/cloud-apps/provesource/index.md b/connections/sources/catalog/cloud-apps/provesource/index.md index e142af0c9a..9adab9fa11 100644 --- a/connections/sources/catalog/cloud-apps/provesource/index.md +++ b/connections/sources/catalog/cloud-apps/provesource/index.md @@ -9,7 +9,7 @@ _**NOTE:** The ProveSource Source is currently in beta, which means that they ar ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for "ProveSource" within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup flow to "Add Source". The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you'll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Copy the Write key from the Segment UI and log in to your ProveSource account - navigate to [Settings](https://console.provesrc.com/#/settings) > Integrations > Click Edit next to Segment Integration and paste the key to connect. diff --git a/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md b/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md index 63bb251848..4a4dd76e77 100644 --- a/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md +++ b/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md @@ -56,7 +56,7 @@ and client secret: You should now see a Summary page with a Components section. This section lists your _Client ID_ and _Client Secret_ settings. ### Set up your subdomain -Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters “mc” in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. +Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters "mc" in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. ### Enable the Salesforce Marketing Cloud Source diff --git a/connections/sources/catalog/cloud-apps/selligent/index.md b/connections/sources/catalog/cloud-apps/selligent/index.md index 9220d1fe10..0945a26090 100644 --- a/connections/sources/catalog/cloud-apps/selligent/index.md +++ b/connections/sources/catalog/cloud-apps/selligent/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Selligent destinatio 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Selligent` for nickname and `selligent` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Selligent.** Copy this write key. +4. The next page ("Overview") will surface your **Segment write key for Selligent.** Copy this write key. 5. To finish the setup, send your write key to your Selligent Account Manager. He/she will enable the Source for you on Selligent's end. diff --git a/connections/sources/catalog/cloud-apps/vero/index.md b/connections/sources/catalog/cloud-apps/vero/index.md index c7b90a1f45..4b96ad71f2 100644 --- a/connections/sources/catalog/cloud-apps/vero/index.md +++ b/connections/sources/catalog/cloud-apps/vero/index.md @@ -21,7 +21,7 @@ If you have previously enabled sending email events via the Vero destination dur ![](images/vero2.png) -4. The next page (“Overview”) will surface your **Segment write key for Vero.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Vero.** Copy this write key.  5. To finish the setup, you’ll have to go into your Vero account and enter this Segment write key in their integrations settings. Find the right place in Vero by clicking [Integrations](https://app.getvero.com/settings/integrations?integrations=all) > Segment. diff --git a/connections/sources/catalog/cloud-apps/zendesk/index.md b/connections/sources/catalog/cloud-apps/zendesk/index.md index d8da001d4c..5a09159f8c 100644 --- a/connections/sources/catalog/cloud-apps/zendesk/index.md +++ b/connections/sources/catalog/cloud-apps/zendesk/index.md @@ -242,7 +242,7 @@ In your warehouse, each collection gets its own table. Find below a list of the type - The type of this ticket. Possible values: "problem", "incident", "question" or "task”. + The type of this ticket. Possible values: "problem", "incident", "question" or "task". subject @@ -262,7 +262,7 @@ In your warehouse, each collection gets its own table. Find below a list of the status - The state of the ticket. Possible values: "new", "open", "pending", "hold", "solved", "closed”. + The state of the ticket. Possible values: "new", "open", "pending", "hold", "solved", "closed". recipient diff --git a/connections/sources/catalog/mobile/android/index.md b/connections/sources/catalog/mobile/android/index.md index 597034e245..d8d2f80720 100644 --- a/connections/sources/catalog/mobile/android/index.md +++ b/connections/sources/catalog/mobile/android/index.md @@ -196,7 +196,7 @@ import com.segment.analytics.Properties.Product; Properties properties = new Properties(); // add orderId and revenue to the properties object -properties.putValue(“orderId”, String orderId).putValue(“revenue”, double revenue); +properties.putValue("orderId", String orderId).putValue("revenue", double revenue); // initialize a new product Product product1 = new Product(String id, String sku, double price); @@ -208,7 +208,7 @@ Product product2 = new Product(String id, String sku, double price); properties.putProducts(product1, product2); // pass the properties object into your Order Completed event -Analytics.with(context).track(“Order Completed”, properties); +Analytics.with(context).track("Order Completed", properties); ``` Find details on **best practices in event naming** as well as the **`track` method payload** in our [Spec](/docs/spec/track/). diff --git a/connections/sources/catalog/ott/roku/index.md b/connections/sources/catalog/ott/roku/index.md index 2b8166e9e2..4ce92b7184 100644 --- a/connections/sources/catalog/ott/roku/index.md +++ b/connections/sources/catalog/ott/roku/index.md @@ -33,7 +33,7 @@ The library consists of three parts: 2. **source/SegmentAnalytics.brs** - Implementation responsible for making HTTP requests to Segment REST API for identify, track, screen, group or alias. Includes handling for batching, error handling. Must be used within context of SceneGraph Task node. Cannot be used directly within context of SceneGraph UI components. 3. **components/SegmentAnalyticsTask.brs/xml** - SceneGraph Task node that will be running for the entire lifecycle of the app. Responsible for delegating calls to SegmentAnalytics.brs to make requests to Segment REST API. -The “components” folder contains SceneGraph components and the “source” folder contains BrightScript files. The content of each folder must be included in the respective folder of the application. Depending on the application folder structure and where the library files are included, SegmentAnalyticsTask.xml might need to be updated to reflect the file paths. +The "components" folder contains SceneGraph components and the "source" folder contains BrightScript files. The content of each folder must be included in the respective folder of the application. Depending on the application folder structure and where the library files are included, SegmentAnalyticsTask.xml might need to be updated to reflect the file paths. ### Initializing the library @@ -43,32 +43,32 @@ To instantiate the library, you first need to update the application scene .xml 1. Include SegmentAnalyticsConnector.brs BrightScript file ``` -