Merge branch 'develop' into issue-4873

Author: forstisabella

src/connections/destinations/catalog/canny-functions/index.md renamed to src/connections/destinations/catalog/actions-canny/index.md

@@ -2,8 +2,6 @@
 title: Canny (Actions) Destination
 id: 6489bbade6fe3eb57c13bd6a
 beta: true
-hidden: true
-private: true
 ---
 
 {% include content/plan-grid.md name="actions" %}

src/connections/destinations/catalog/actions-insider-audiences/index.md

@@ -2,8 +2,6 @@
 title: Insider Audiences (Actions)
 id: 643698ffee21b544f6aa756a
 beta: true
-hidden: true
-private: true
 hide-boilerplate: true
 hide-dossier: true
 ---
@@ -14,8 +12,6 @@ hide-dossier: true
 
 This destination is maintained by Insider. For any issues with the destination, contact the [Insider Support team.](mailto:[email protected]){:target="_blank"}
 
-{% include content/ajs-upgrade.md %}
-
 ## Getting started
 
 > info "Prerequisites"

src/connections/index.md

@@ -54,7 +54,7 @@ You can then sort or filter each column to just the values you care about, by cl
 
 Segment disables sources that don't have enabled destinations after 14 days, and emails you before disabling any sources. Disabling these sources helps maintain a clean workspace.
 
-We do understand there maybe cases to keep a source active, if you'd like to add your source(s) to an exception list, you can do so by filling out this (airtable form)[https://airtable.com/shr7V9LFDZh31cYWW].
+Segment understands there maybe cases to keep a source active. If you'd like to add your source(s) to an exception list, you can do so by filling out this [Airtable form](https://airtable.com/shr7V9LFDZh31cYWW){:target="_blank"}.
 
 
 

src/connections/reverse-etl/index.md

@@ -109,6 +109,7 @@ To create a mapping:
 5. Select a test record to preview the fields that you can map to your destination in the **Add test record** field.
 6. Define how to map the record columns from your model to your destination in the **Select Mappings** section.
       * You map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected.
+      * If you're setting up a destination action, depending on the destination, some mapping fields may require data to be in the form of an object or array. See the [supported objects and arrays for mapping](#supported-object-and-arrays).
 7. Click **Create Mapping**.
 8. Select the destination you’d like to enable on the **My Destinations** page under **Reverse ETL > Destinations**.
 9. Turn the toggle on for the **Mapping Status**. Events that match the trigger condition in the mapping will be sent to the destination.
@@ -133,6 +134,8 @@ To check the status of your extractions:
     * The load results - how many successful records were synced as well as how many records were updated, deleted, or are new.
 5. If your sync failed, click the failed reason to get more details on the error and view sample payloads to help troubleshoot the issue.
 
+#### Replays
+You can choose to replay syncs. To replay a specific sync, contact [[email protected]](mailto:[email protected]). Keep in mind that triggering a replay resyncs all records for a given sync.
 
 ### Edit your model
 
@@ -166,6 +169,71 @@ The Segment Connections destination enables you to mold data extracted from your
 > warning ""
 >  The Segment Connections destination sends data to Segment’s Tracking API, which has cost implications. New users count as new MTUs and each call counts as an API call. For information on how Segment calculates MTUs and API calls, please see [MTUs, Throughput and Billing](/docs/guides/usage-and-billing/mtus-and-throughput/).
 
+## Supported object and arrays 
+
+When you set up destination actions in Reverse ETL, depending on the destination, some [mapping fields](#step-4-create-mappings) may require data to be in the form of an [object](#object-mapping) or [array](#array-mapping). 
+
+### Object mapping
+You can send data to a mapping field that requires object data. An example of object mapping is an `Order completed` model with a `Products` column that’s in object format. 
+
+Example: 
+    
+    {
+        "product": {
+            "id": 0001,
+            "color": "pink",
+            "name": "tshirt",
+            "revenue": 20,
+            "inventory": 500
+        }
+    }
+
+To send data to a mapping field that requires object data, you can choose between these two options: 
+
+Option | Details
+------ | --------
+Customize object | This enables you to manually set up the mapping fields with any data from the model. If the model contains some object data, you can select properties within the object to set up the mappings as well.
+Select object | This enables you to send all nested properties within an object. The model needs to provide data in the format of the object. 
+
+> success ""
+> Certain object mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your object don't match with the destination properties, the data won't send. Segment recommends you to use **Customize Object** to ensure your mapping is successful.
+
+
+### Array mapping
+To send data to a mapping field that requires array data, the model must provide data in the format of an array of objects. An example is an `Order completed` model with a `Product purchased` column that’s in an array format.
+
+Example: 
+
+    
+    [
+    {
+        "currency": "USD",
+        "price": 40,
+        "productName": "jacket",
+        "purchaseTime": "2021-12-17 23:43:47.102",
+        "quantity": 1
+    },
+    {
+        "currency": "USD",
+        "price": 5,
+        "productName": "socks",
+        "quantity": 2
+    }
+    ]
+    
+
+To send data to a mapping field that requires array data, you can choose between these two options: 
+
+Option | Details
+------ | --------
+Customize array | This enables you to select the specific nested properties to send to the destination. 
+Select array | This enables you to send all nested properties within the array.
+
+> success ""
+> Certain array mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your array don't match the destination properties, the data won't send. Segment recommends you to use the **Customize array** option to ensure your mapping is successful.
+
+Objects in an array don't need to have the same properties. If a user selects a missing property in the input object for a mapping field, the output object will miss the property. 
+
 ## Limits
 To provide consistent performance and reliability at scale, Segment enforces default use and rate limits for Reverse ETL.
 

src/connections/sources/catalog/cloud-apps/listrak/index.md

@@ -0,0 +1,84 @@
+---
+title: 'Listrak Source'
+hidden: true
+private: true
+---
+{% include content/source-region-unsupported.md %}
+
+> info ""
+> The Listrak Source is in beta, and Listrak is still developing the source. To join Listrak's beta program or to give any feedback to help improve the Listrak Source and its documentation, [let Listrak know](mailto:[email protected]).
+
+Listrak is the retail industry’s leading customer engagement platform. Listrak delivers results for more than 1,000 retailers by providing best-in-class email, text message marketing, identity resolution marketing and push notifications through seamless cross-channel orchestration. Listrak’s data-first approach delivers 1:1 personalization at scale so you can send messages at precisely the right time across the right combination of channels and devices to maximize customer engagement, revenue, and lifetime value.
+
+The Listrak as an Event Cloud Source integration enables marketers to utilize behavioral activities such as sending, opening, clicking, converting, bouncing, abuse complaints, and unsubscribing events within the Segment platform. This capability empowers marketers to perform downstream analysis by leveraging additional platform integrations set up as Segment destinations.
+
+[Listrak](https://listrak.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides self-serve predictive analytics for growth marketers, using machine learning to automate audience insights and recommendations.
+
+This is an [Event Cloud Source](https://segment.com/docs/sources/#event-cloud-sources){:target="_blank"} can export data into your Segment warehouse and federate the exported data into your other enabled Segment Destinations.
+
+Listrak as an Event Cloud Source enables marketers to align contacts in Listrak’s lists to audiences in Segment.
+
+Listrak maintains this Source. For any issues with the source, [contact Listrak's Support team](mailto:[email protected]).
+
+## Getting Started
+
+1.	From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog){:target="_blank"} click **Add Source**.
+
+1.  Search for **Listrak** in the Sources Catalog, select **Listrak**, and click **Add Source**.
+
+1.	On the next screen, give the Source a nickname configure any other settings.
+    - The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example, `Listrak_Prod`, `Listrak_Staging`, `Listrak_Dev`).
+
+1.	Click **Add Source** to save your settings.
+
+1.	Copy the Write key from the Segment UI and log in to your Listrak account - navigate to **Integrations > Integrations Manager > New Integration > Segment Integration**.
+    - You should see the Information tab for the Segment Integration.
+    - Click the Setup tab, where you'll find input fields that allow you to enter the write key as well as other relevant information.
+
+## Components
+
+**Stream**
+
+Listrak uses Segment's Source component to send Segment event data. It uses server-side Track and Identify methods to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.
+
+The default behavior is for Listrak to pass the `userId` associated with the email recipient as the `userId`. The Listrak Segment integration maps a Listrak `Segmentation Field` to Segment's `userId`. If no value for the `Segmentation Field` exists, Listrak won't pass a `userId`. Listrak always uses the contact’s email address as the `anonymousId` and always adds a trait called `email` with the user's email. Listrak also provides a trait that contains the Listrak `listId` with the name `Listrak_list_{listId}`, where `{listId}` is the id of the list, for example, `Listrak_list_12345`.
+
+
+**Events**
+
+The following table lists events that Listrak sends to Segment. These events appear as tables in your warehouse and as regular events in other Destinations. Listrak includes the `userId` if available.
+
+| Event Name			| Description |
+| -----------			| ----------- |
+| `Email Sent`			| Email was sent successfully |
+| `Email Opened`			| Prospect opened the email |
+| `Link Clicked`			| Prospect clicked the tracking link |
+| `Email Replied`			| Prospect replied to the email sent |
+| `Email Bounced`			| Email servers rejected the email |
+| `Email Unsubscribed`	| Prospect clicked the unsubscribe link |
+
+
+**Event Properties**
+
+The following table lists the properties included in the events table:
+
+|Property Name	|Description |
+| -----------	| ----------- |
+|`event`		|Email event type |
+|`userId`		|Prospect email ID |
+|`email_id`		|ID of the email |
+|`fromId`		|Sender email ID |
+|`email_subject`|Subject line of the email |
+|`link`			|URL of the link clicked |
+
+
+
+## Adding Destinations
+
+Now that your Source is set up, you can connect it with Destinations. 
+
+The Listrak Source works better when you also connect Listrak as a Destination Action. With the Listrak Destination Action, you can use Segment to send Listrak user and event data, enabling you to trigger email campaigns. Listrak is developing the Destination Action features, enabling you to send website or mobile data to Listrak. 
+
+Log into your downstream tools and check to see that your events appear as expected and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](https://segment.com/docs/connections/event-delivery/){:target="_blank"} tool, and refer to the Destination docs for each tool for troubleshooting.
+
+If there are any issues with how the events are arriving to Segment, [contact the Listrak support team](mailto:[email protected]).

src/connections/sources/catalog/cloud-apps/onetrust/index.md

@@ -8,7 +8,7 @@ OneTrust makes it easy for you to capture, centralize, govern, and sync consente
 
 This is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations. 
 
-This source is maintained by OneTrust. For any issues with the source, [contact their support team]([email protected]).
+This source is maintained by OneTrust. For any issues with the source, [contact their support team](mailto:[email protected]){:target="_blank”}.
 
 ## Getting Started 
 

src/engage/quickstart.md

@@ -41,7 +41,7 @@ Invite teammates to your Engage dev space and grant them access to the space. Na
 
 ## Step 3: Connect production sources
 
-1. From your Engage space, go to your space Settings and click **Sources**.
+1. From your Engage space, navigate to **Unify settings** and click **Profile sources**.
 2. On the screen that appears, choose one or two production sources from your Connections workspace.
    Segment recommends connecting your production website or App source as a great starting point.
 

src/unify/faqs.md

@@ -50,3 +50,7 @@ Any of the external IDs can be used to query a profile. When a profile is reques
 
 ### Can ExternalID's be changed or removed from the profiles?
 No. As the Identity Graph uses ExternalIDs, they remain for the lifetime of the user profile.
+
+### Can I delete specific events from a user profile in Unify? 
+No. Alternatively, you may delete the entire user profile from Segment using a [GDPR deletion request](/docs/privacy/user-deletion-and-suppression/).
+