Merge remote-tracking branch 'upstream/develop' into develop

Author: lopenchi

src/connections/destinations/catalog/actions-first-party-dv360/index.md

@@ -9,7 +9,7 @@ redirect_from: /connections/destinations/catalog/first-party-dv360/
 
 Google’s [Display & Video (DV360)](https://marketingplatform.google.com/about/display-video-360/){:target="_blank"} is an end-to-end campaign management tool that enables enterprise customers to plan, measure, and run display and video advertisements. Segment’s integration with DV360 enables Segment customers to sync audiences created in Engage with DV360 for centralized audience management and improved retargeting.
 
-This destination is different from the existing DV360 Actions as it allows you to upload [contact info](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#ContactInfo){:target="_blank"} and the [mobile device ID](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#mobiledeviceidlist){:target="_blank"}.
+This destination is different from the existing DV360 Actions as it allows you to upload [contact info](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#contactinfo){:target="_blank"} and the [mobile device ID](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#mobiledeviceidlist){:target="_blank"}.
 
 This destination can only be used with Engage. 
 
@@ -68,12 +68,15 @@ Segment automatically sends consent as `TRUE` for this destination.  Segment use
 
 ## Data requirements
 Based on Google’s documentation, make sure you send the correct required identifiers:
-* [Contact info list requirements](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#contactinfo){:target="_blank"}
+* [Contact info list requirements](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#contactinfo){:target="_blank"}
    * For example, you must send first name, last name, ZIP code, and country code all together and not just one. Make sure all phone numbers are in [E.164 format](https://en.wikipedia.org/wiki/E.164){:target="_blank"}. 
-* [Mobile ID Requirements](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#mobiledeviceidlist){:target="_blank"}
+* [Mobile ID Requirements](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#mobiledeviceidlist){:target="_blank"}
 
 
 ## FAQs
 
 #### When will my data appear in DV360?
 When you complete the connection between Segment and DV360, it can take from 24 to 48 hours for Google to create the user list. This must complete before Segment can begin to sync users into that list. 
+
+#### What is membershipDurationDays and its limit?
+The duration in days that an entry remains in the audience after the qualifying event. The set value must be greater than 0 and less than or equal to 540.

src/connections/destinations/catalog/primer/index.md

@@ -16,8 +16,6 @@ Since Primer needs to be initialized as early as possible, you need to supply th
 
 This will initialize the Primer SDK under the hood and begin collecting events and initializing the Primer Flow.
 
-- - -
-
 Primer supports the `identify` and `track` methods.
 
 ## Identify

src/connections/destinations/catalog/promoter-io/index.md

@@ -11,8 +11,6 @@ hide-dossier: true
 
 Once the Segment library is integrated with your service, add your Promoter API Key and enable Promoter in your Segment destinations page. You can find your API key in Promoter.io under **Accounts Settings > Segment Destination**.
 
-- - -
-
 Promoter supports the `identify` and `track` methods from Segment and will allow you to:
 
 - Add a contact to a list

src/connections/destinations/catalog/quora-conversion-pixel/index.md

@@ -13,13 +13,13 @@ id: 5952698570a3e552b9575519
 2. Search for "Quora" in the Catalog, select it, and choose which of your sources to connect the destination 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){:target="_blank"}.
+   1. Log into your [Quora Ads Manager Account](https://www.quora.com/ads/account){:target="_blank"}.
 
-	ii. Navigate to the "Quora Pixel" tab in your Quora Dashboard.
+   2. Navigate to the "Quora Pixel" tab in your Quora Dashboard.
 
-	iii. Click the "Setup Pixel" button to open the installation popup modal.
+   3. Click the "Setup Pixel" button to open the installation popup modal.
 
-	iv. Under "Option A: Install a JavaScript Pixel," find your Quora Conversion Pixel Key in the Quora JavaScript Pixel - the key is embedded in a tag that looks like `qp('init', '7cc5a029c2604daa8365d15ff337146e')`. In the example below, the key is `7cc5a029c2604daa8365d15ff337146e`.
+   4. Under "Option A: Install a JavaScript Pixel," find your Quora Conversion Pixel Key in the Quora JavaScript Pixel - the key is embedded in a tag that looks like `qp('init', '7cc5a029c2604daa8365d15ff337146e')`. In the example below, the key is `7cc5a029c2604daa8365d15ff337146e`.
 
 
 ## Track

src/connections/destinations/catalog/ramen/index.md

@@ -2,19 +2,20 @@
 title: Ramen Destination
 id: 558c9d1a0a20f4e22f0fb3bb
 ---
+
 ## Getting Started
 
 When you enable Ramen in the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Ramen's JavaScript library onto your page. This means you should remove Ramen's snippet from your page if you already have it there.
-​
-+ As of March 2016, Ramen supports asking questions of anonymous website visitors in addition to logged-in users. Calling [`page`](#page), [`track`](#track), and [`group`](#group) will work without calling [`identify`](#identify). However, when you call [`identify`](#identify) you _must_ pass in an `id` or else the Ramen destination will ignore the call.
-​
-​
+
+- As of March 2016, Ramen supports asking questions of anonymous website visitors in addition to logged-in users. Calling [`page`](#page), [`track`](#track), and [`group`](#group) will work without calling [`identify`](#identify). However, when you call [`identify`](#identify) you _must_ pass in an `id` or else the Ramen destination will ignore the call.
+
 ## Identify
-​
+
 When you make an [Identify call](/docs/connections/spec/identify) on Analytics.js, it identifies the logged-in user to Ramen.
-​
+
 Here is a full example, which we will annotate below:
-​
+
+
 ```javascript
 analytics.identify('314159', {
   email: '[email protected]',
@@ -25,26 +26,23 @@ analytics.identify('314159', {
   mrr: 149.99
 });
 ```
-​
+
 Here is a list of the attributes we process:
-​
+
 * `id` becomes the `id` of the user in Ramen.
 * `email` becomes the `email` of the user in Ramen.
 * `name` becomes the `name` of the user in Ramen.
 * `created_at` becomes the `customer_created_at` timestamp for the user in Ramen. It can be passed in as a `Date` or seconds since the epoch.
 * If `company` is an `Object` with an `id` attribute, we'll treat that information as if it was passed to [`group`](#group) and create a company in Ramen.
 * Attributes with names ending in `_at` will be parsed as times.
 * Attributes with names beginning with `is_` will be parsed as Booleans.
-​
-​
+
 **Note:** Ramen will ignore any calls to `identify` that do not contain `userId`.
-​
-​
-​
+
 ## Group
-​
+
 Segment supports Ramen Companies in Analytics.js through the [`group`](/docs/connections/spec/group) method. Users can be put into multiple groups, which will associate them to multiple companies in Ramen.
-​
+
 Here is a full example, which we will annotate below:
 ​
 ```javascript
@@ -57,49 +55,44 @@ analytics.group('314159', {
   mrr: 149.99
 });
 ```
-​
+
 Here is a list of the attributes we process:
-​
+
 * `id` becomes the `id` of the company in Ramen.
 * `url` becomes the `url` of the company in Ramen.
 * `name` becomes the `name` of the company in Ramen.
 * `created_at` becomes the `company_created_at` timestamp for the company in Ramen. It can be passed in as a `Date` or seconds since the epoch.
 * Other attributes can be passed in as well, and will parsed according to the same rules as denoted in the [`identify`](#identify) section.
-​
-​
+
 ## Page
-​
+
 When you call [`page`](/docs/connections/spec/page) on Analytics.js, it registers a new pageview in Ramen and checks to see if any questions should be asked.
-​
+
 Ramen does not support passing in any attributes to `page`. You can call `page({ title: "Our page" })` but the attributes (ie. `title` in this example) will be ignored.
-​
-​
+
 ## Track
-​
+
 When you call [`track`](/docs/connections/spec/track) on Analytics.js, it registers a new event in Ramen and checks to see if any questions should be asked.
-​
+
 Ramen does not support passing in any attributes to `track` beyond the event name. You can call `track('Subscribed', { plan: "Startup" })` but the attributes (ie. `plan` in this example) will be ignored.
-​
-​
-- - -
-​
+
+
 ## Features
-​
-​
+
 ### Secure Mode
-​
+
 If you want to enable Ramen [secure mode](http://docs.ramen.is/#secure-mode){:target="_blank"} for analytics.js, you can pass in the `timestamp` and `auth_hash` variables by rendering it in your server-side templates.
-​
+
 The `timestamp` should be a Unix timestamp (epoch seconds). The `auth_hash` is a SHA256 has of several attributes. The hash is not based on the email, it is based on:
-​
-+ user.email - If you do not store emails for your customers, use an empty string
-+ user.id
-+ user.name - If you do not have a name for your customers, use their email address or an empty string
-+ timestamp
-+ Ramen API Secret
-​
+
+- user.email - If you do not store emails for your customers, use an empty string
+- user.id
+- user.name - If you do not have a name for your customers, use their email address or an empty string
+- timestamp
+- Ramen API Secret
+
 Here's an example of a Ruby web server rendering an identify call with secure mode:
-​
+
 ```ruby
 analytics.identify('<%= current_user.id %>', {
     email   : '<%= current_user.email %>',
@@ -113,31 +106,26 @@ analytics.identify('<%= current_user.id %>', {
     }
 });
 ```
-​
+
 `RAMEN_ORGANIZATION_SECRET_KEY` is found in Ramen's RamenJS documentation.
-​
-​
-- - -
-​
-​
+
 ## Troubleshooting
-​
-​
+
 ### I'm seeing a `404` error
-​
+
 Check to make sure your Ramen `ORGANIZATION_ID` is correct.
-​
+
 ### I'm seeing a `401` error
-​
+
 The request you are sending is not valid. Several things can cause this:
-​
-+ An invalid `user.email`. It can be blank, but it cannot be an invalid email address.
-+ A missing `user.id`.
-+ Not including `timestamp` and `auth_hash` once Secure Mode has been enabled. You can see if Secure Mode is enabled by visiting your RamenJS settings page in Ramen.
-​
+
+- An invalid `user.email`. It can be blank, but it cannot be an invalid email address.
+- A missing `user.id`.
+- Not including `timestamp` and `auth_hash` once Secure Mode has been enabled. You can see if Secure Mode is enabled by visiting your RamenJS settings page in Ramen.
+
 If the above all look correct, and you are sending `timestamp` and `auth_hash`, check the following:
-​
-+ `timestamp` is being dynamically generated (ie. it is not accidentally hard-coded).
-+ `auth_hash` is being calculated correctly
-​
+
+- `timestamp` is being dynamically generated (ie. it is not accidentally hard-coded).
+- `auth_hash` is being calculated correctly
+
 If you are still having trouble, you can email [Ramen support](mailto:[email protected]).

src/connections/destinations/catalog/recombee-ai/index.md

@@ -18,7 +18,6 @@ This destination is maintained by Recombee. For any issues with the destination,
 
 > info ""
 > The Recombee Destination is currently in beta, which means that the Recombee team is still actively developing the destination. If you have any feedback to help improve the Recombee Destination and its documentation, [contact the Recombee support team](mailto:[email protected]).
->>>>>>> Stashed changes
 
 Use this Segment destination to send your interaction data, like views, purchases, or plays, to Recombee.
 

src/connections/destinations/catalog/relay/index.md

@@ -7,7 +7,6 @@ title: Relay Destination
 Once the Segment library is integrated with your server, toggle Relay on in your Segment destinations.
 
 Relay supports the `identify` and `track` methods.
-- - -
 
 ## Identify
 

src/connections/destinations/catalog/retina/index.md

@@ -8,7 +8,7 @@ id: 5f287bfa332cce0b1ed18331
 
 Retina AI maintains this destination. For any issues with the destination, contact the [Retina AI Support Team](mailto:[email protected]).
 
-> info " "
+> info ""
 > The Retina AI Destination is in beta, which means that they are still actively developing the destination. To join the beta program, or if you have any feedback to help improve the Retina AI Destination and its documentation, contact the [Retina AI Support Team](mailto:[email protected]).
 
 

src/connections/destinations/catalog/rollbar/index.md

@@ -20,12 +20,12 @@ This feature makes use of JavaScript Source Maps to translate the minified code
 
 2. Provide your source map. There are two ways you can do this:
 
-  a. Automatic download: place a comment like the following at the bottom of your minified JavaScript files:
+   1. Automatic download: place a comment like the following at the bottom of your minified JavaScript files:
 
-  ```
-  //# sourceMappingURL=URL_TO_SOURCE_MAP
-  ```
+   ```
+   //# sourceMappingURL=URL_TO_SOURCE_MAP
+   ```
 
-  b. Upload pre-deploy: at the beginning of your deploy script, upload a source map package using Rollbar's API.
+   2. Upload pre-deploy: at the beginning of your deploy script, upload a source map package using Rollbar's API.
 
   For more detail on providing your source map, checkout [Rollbar's documentation here](https://rollbar.com/docs/source-maps/#step-2-provide-your-source-map){:target="_blank"}.

src/connections/destinations/catalog/route/index.md

@@ -10,8 +10,6 @@ Once the Segment library is integrated with your server, toggle Route `on` in yo
 
 Route supports the `identify` and `track` methods.
 
----
-
 ## Identify
 
 When you `identify` a contact, we'll pass that contact's information to Route with `email` as Route's Contact ID. The traits recognized as Route's contact profile fields are: