Merge branch 'develop' of github.com:segmentio/segment-docs into develop

Author: markzegarelli

src/_data/catalog/destinations_private.yml

@@ -147,3 +147,7 @@ Google recommends use of their Firebase SDKs to send mobile data to Google Analy
 ### Reserved Names
 
 Google reserves certain event names, parameters, and user properties. Google silently drops any events that include [these reserved names](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference?client_type=gtag#reserved_names){:target="_blank"}. If you notice that your data isn't appearing in Google, please check that you're not using a reserved name.
+
+### Data taking a long time to appear in Google's reports
+
+Google may take [24-48 hours](https://support.google.com/analytics/answer/9333790)  to process data sent to Google Analytics. As a result, the Google Analytics user interface may not reflect the most current data. The Google Analytics [Realtime report](https://support.google.com/analytics/answer/9271392){:target="_blank"} displays activity on your site as it happens.

src/connections/destinations/catalog/actions-google-analytics-4/index.md

@@ -0,0 +1,38 @@
+---
+title: Ripe Cloud (Actions) Destination
+hide-boilerplate: true
+hide-dossier: true
+private: true
+id: 63cade592992cf7052ce2e3e
+---
+
+[Ripe](https://www.getripe.com/){:target="_blank"} is a product-led sales 
+platform that empowers you to unlock revenue pipeline with product data. By identifying and showing which prospects to focus efforts on, you can convert leads into meetings inside your product.
+
+This destination enables you to send product data to Ripe. Sales teams can identify who decision-makers and product champions are by understanding what properties they have and what events they have triggered. The Ripe destination is built as an alternative to directly adding Ripe’s SDK script to your app or site.
+
+The Ripe Segment integration is an [Actions-based Destination in cloud mode](/docs/connections/destinations/#connection-modes) that lets you send your backend events directly to Ripe.
+
+{% include content/ajs-upgrade.md %}
+
+## Benefits of Ripe
+
+Ripe provides the following benefits:
+
+- **Be relevant**. The Ripe destination understands key events in Segment to identify relevant leads, and shows its widget selectively to them.
+- **Quick integration**. Using the Ripe destination is the fastest way to start combining key product events with sales data and start targeting ripe leads.
+- **More control**. You can customize the conditions under which the events are sent to Ripe.
+
+## Getting started
+
+> info ""
+> Before you begin, create an API key in Ripe which you'll use to configure the integration.
+
+
+1. From the Segment web app, navigate to **Connections > Catalog**, then click the **Destinations** tab at the top of the catalog.
+2. Search for *Ripe Cloud Mode (Actions)* in the left navigation, and click it.
+3. Click **Configure Ripe Cloud Mode (Actions)**.
+4. Select an existing Source to connect to Ripe (Actions).
+5. Enter your Ripe API key in the API key field.
+
+{% include components/actions-fields.html %}

src/connections/destinations/catalog/actions-ripe-cloud/index.md

@@ -1,5 +1,5 @@
 ---
-title: Ripe Destination (Actions)
+title: Ripe Web (Actions) Destination
 hide-boilerplate: true
 hide-dossier: true
 id: 63913b2bf906ea939f153851
@@ -29,8 +29,8 @@ Ripe provides the following benefits:
 
 
 1. From the Segment web app, navigate to **Connections > Catalog**, then click the **Destinations** tab at the top of the catalog.
-2. Search for *Ripe* in the left navigation, and click it.
-3. Click **Configure Ripe**.
+2. Search for *Ripe Device Mode (Actions)* in the left navigation, and click it.
+3. Click **Configure Ripe Device Mode (Actions)**.
 4. Select an existing Source to connect to Ripe (Actions).
 5. Enter your Ripe API key in the API key field.
 

…stinations/catalog/actions-ripe/index.md …ations/catalog/actions-ripe-web/index.mdsrc/connections/destinations/catalog/actions-ripe/index.md renamed to src/connections/destinations/catalog/actions-ripe-web/index.md src/connections/destinations/catalog/actions-ripe/index.md renamed to src/connections/destinations/catalog/actions-ripe-web/index.md

@@ -150,7 +150,7 @@ You can specify what the event action should be called in the Google Universal A
 
 Segment makes it simple to save your A/B testing versions to custom dimensions in Google Universal Analytics by mapping an experiment to a custom dimension in the Google Universal Analytics destination settings.
 
-If you are using cloud-mode or server-side Google Universal Analytics destinations, you can also send this data automatically using the `experiment_id`, `experiment_name`, `variation_id`, and `variation_name` properties. If both an experiment and variation are defined, then this is sent automatically. Segment uses the ids before using the names. If both an ID and a name exist, Segment sends the ID first. For example, if you an `experiment_id`, an `experiment_name`, and a `variation_name` in a call, only the `experiment_id` and `variation_name` are sent to Google Universal Analytics.
+If you are using cloud-mode or server-side Google Universal Analytics destinations, you can also send this data automatically using the `experiment_id`, `experiment_name`, `variation_id`, and `variation_name` properties. If both an experiment and variation are defined, then this is sent automatically. Segment uses the ids before using the names. If both an ID and a name exist, Segment sends the ID first. For example, if you have an `experiment_id`, an `experiment_name`, and a `variation_name` in a call, only the `experiment_id` and `variation_name` are sent to Google Universal Analytics.
 
 When you have an active A/B test on a page, Segment either sets that experiment as a property or a user trait, depending on how you choose to send experiment data to other tools on your A/B testing tool's Segment settings page. The property or trait for A/B test experiments are labeled like the following examples:
 

src/connections/destinations/catalog/google-analytics/index.md

@@ -142,6 +142,9 @@ analytics.track({
 
 When you call `track` on `analytics.js`, Segment calls Klaviyo's `track` with the same parameters.
 
+> info ""
+> When you're tracking client-side, some Klaviyo events require you send an Identify call  before a Track call. 
+
 ### Server-side Track
 
 When you call make a Track call from one of Segment's mobile or server-side libraries, Segment keys the user with the `userId` and also provides the Klaviyo `$email` `customer_property` if your `userId` is an email, or you provide `email` as one of your event `properties`.

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

@@ -386,6 +386,12 @@ Copy and paste this URL into the upstream tool or service to send data to this s
 ##### What is the retry policy for a webhook payload?
 
 Segment retries invocations that throw RetryError or Timeout errors up to six times. After six attempts, the request is dropped.
+The initial wait time for the retried event is a random value between one and three minutes.
+Wait time increases exponentially after every retry attempt. The maximum wait time between attempts can reach 20 minutes.
+
+##### I configured RetryError in a function, but it doesn't appear in my source function error log.
+
+Retry errors only appear in the source function error logs if the event has exhausted all six retry attempts and, as a result, has been dropped.
 
 ##### What is the maximum payload size for the incoming webhook?
 

src/connections/functions/source-functions.md

@@ -131,6 +131,25 @@ analytics.track("Receipt Viewed", {}, {
 
 This works for any [context field](/docs/connections/spec/common/#context) that Segment automatically collects.
 
+### Can I add context fields that do not already exist?
+
+Yes. Similar to overwriting context, you can add context fields by passing them into the options object as the third argument of the event call. For example, the analytics.js library does not automatically collect location information. To add this into the context object, pass it into the third argument as in the example below:
+
+```js
+analytics.track("Order Completed", {}, {
+    location: {
+        latitude: '39.7392',
+        longitude: '104.9903'
+    }
+})
+```
+
+> info ""
+> You must pass the context object with the call, event if it's empty, as shown by the empty object in the example above.
+
+Some destinations accept properties only. As a result, custom context fields you add may not forward to these destinations.
+
+
 ## Known issues:
 
 [Review and contribute to these on GitHub](https://github.com/segmentio/analytics.js/issues)