Merge pull request #2684 from segmentio/develop

Release 22.13.2

Author: pwseg

src/_data/sidenav/main.yml

@@ -324,6 +324,8 @@ sections:
       title: Complying With GDPR
     - path: /privacy/user-deletion-and-suppression
       title: User Deletion and Suppression
+  - path: /privacy/account-deletion
+    title: Account & Data Deletion 
   - path: /privacy/faq
     title: Privacy FAQs
 - section_title: Protocols

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

@@ -16,7 +16,7 @@ id: 573a3dfb80412f644ff13679
 
 Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading the Ambassador snippet on your page and sending data.
 
-Since Ambassador only records specific events and user data, events and users may not appear in Ambassador until you start using the API explained below.
+Since Ambassador only records specific events and user data, events and users may not appear in Ambassador until you start using the API explained below. And you must approve your website domain through the Editor -> Manage websites section in the navigation pane along the left-hand side of the page.
 
 ## Identify
 

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

@@ -196,6 +196,8 @@ The example below shows a Data Extension for `User Registered` Track calls that
 
 ![](images/dext-user-regd-example.png)
 
+> warning ""
+> Segment doesn't automatically send timestamps. You must add timestamps as a property in the Track Call to send timestamps to the destination.
 
 ### Configure the SFMC Destination in Segment
 
@@ -281,7 +283,7 @@ In order to do this, you must have access to **Personas**. To learn more, [conta
 > **Tip**: We recommend that you use [SFMC batching](#optional-set-up-sfmc-batching) with Personas to help reduce the number of API calls that you send to SFMC, but this is optional. If you choose to set up batching, do this _before_ you set up the SFMC destination in your Segment workspace.
 
 Personas sends audience membership and computed trait values to SFMC using Identify calls. To integrate Personas with SFMC:
-1. [Create a Data Extension to store Identify calls](#create-a-data-extension-in-sfmc-to-store-identify-calls) if you haven't already. 
+1. [Create a Data Extension to store Identify calls](#create-a-data-extension-in-sfmc-to-store-identify-calls) if you haven't already.
 2. [Configure SFMC as a Personas Destination](#configure-the-salesforce-marketing-cloud-destination-in-segment)
 
 When you sync to an existing Data Extension, note these additional requirements:

src/connections/destinations/catalog/salesforce-marketing-cloud/index.md

@@ -18,11 +18,11 @@ This page lists which [Segment methods](/docs/connections/spec/) each destinatio
   <th> <a href="/docs/connections/spec/alias/">Alias 🏷</a> </th>
 </tr>
 {% for destination in site.data.catalog.destinations.items %}
-{% unless destination.methods.track == false and destination.methods.page_view == false and destination.methods.identify == false and destination.methods.group == false and destination.methods.alias == false %}
+{% unless destination.methods.track == false and destination.methods.page == false and destination.methods.identify == false and destination.methods.group == false and destination.methods.alias == false %}
 <tr>
   <td>{% if destination.status == "PUBLIC_BETA" %}ℹ️ {% endif %}**[{{ destination.display_name }}](/docs/{{ destination.url }})**</td>
   <td>{% if destination.methods.track %}✅{% else %}⬜️{% endif %} </td>
-  <td>{% if destination.methods.page_view %}✅{% else %}⬜️{% endif %} </td>
+  <td>{% if destination.methods.page %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.methods.identify %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.methods.group %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.methods.alias %}✅{% else %}⬜️{% endif %} </td>
@@ -34,7 +34,7 @@ This page lists which [Segment methods](/docs/connections/spec/) each destinatio
 
 #### The following destinations have no method information available:
 {% for destination in site.data.catalog.destinations.items %}
-{% if destination.methods.track == false and destination.methods.page_view == false and destination.methods.identify == false and destination.methods.group == false and destination.methods.alias == false %}
+{% if destination.methods.track == false and destination.methods.page == false and destination.methods.identify == false and destination.methods.group == false and destination.methods.alias == false %}
 - [{{ destination.display_name }}](/docs/{{ destination.url }}){% if destination.status == "PUBLIC_BETA" %} (beta){% endif %}
 {% endif %}
 {% endfor %}

src/connections/destinations/methods-compare.md

@@ -56,13 +56,8 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
 
 ## Journeys
 
-
-In addition to [Personas Default Limits](#default-limits), Journeys enforces default limits to ensure feature performance and reliability.
-
-| Item          | Limit description                | Details                                                                                                                                                                                                                                                                               |
-| ------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Journeys      | 10 Journeys per workspace        | Applies to active, concurrent Journeys. <br><br>Once the limit is reached, you cannot publish any additional Journeys. You will still be able to create draft Journeys.                                                                                               |
-| Journey steps | 20 steps per Journey             | This applies to certain steps:<br><br>- Initial cohort: 1<br>- Wait for condition: 1<br>- True / False Split: 1<br>- Multi-Branch Split: Number of branches<br>- Send to Destinations: 1<br><br>Once the limit is reached, you will be unable to add additional steps to the Journey. |
-| Journey Name  | Maximum length of 73 characters  | Once the limit is reached, you cannot add additional characters to the name.                                                                                                                                                                                               |
-| Step Name     | Maximum length of 170 characters | Once the limit is reached, you cannot add additional characters to the name.                                                                                                                                                                                               |
-| Key           | Maximum length of 255 characters | Once the limit is reached, you cannot add additional characters to the key.                                                                                                                                                                                                |
+| Item         | Limit description                | Details                                                                                                                                                                 |
+| ------------ | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Journey Name | Maximum length of 73 characters  | Once the limit is reached, you cannot add additional characters to the name.                                                                                            |
+| Step Name    | Maximum length of 170 characters | Once the limit is reached, you cannot add additional characters to the name.                                                                                            |
+| Key          | Maximum length of 255 characters | Once the limit is reached, you cannot add additional characters to the key.                                                                                             |

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

@@ -0,0 +1,50 @@
+---
+title: Account & Data Deletion
+---
+
+Segment allows you to delete specific data relating to an individual end user, all data from associated with a source, or all data within your entire workspace.
+
+## Delete individual user data
+To delete the data for an individual user from you workspace, follow the instructions on the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression) page.
+
+## Delete data from a source
+To delete the data for an entire source, email the Customer Success team [([email protected])](mailto:[email protected]) to create a support ticket. In your email to Customer Success, include the following information:
+- Your workplace slug
+- The source from which you'd like to delete data
+- The time frame for the data you'd like to delete*
+
+**Due to the way Segment stores data internally, source-level deletions can only be scoped to one day in granularity. Deletion requests for smaller time frames are not supported.*
+
+> note "Deleting source data"
+> When Segment deletes your data for a particular source, the deletion is not forwarded to sources or data storage providers associated with your account: your data is only removed from Segment's S3 archive buckets. To remove your data from external sources, reach out to the individual source about their deletion practices. 
+
+## Delete your workspace data
+
+Workspace admins can delete all of the data associated with a workspace, including customer data. 
+
+**To delete all data from one workspace:**
+
+1. Sign in to the Segment app, select the workspace you'd like to delete, and click **Settings.**
+2. On the General Settings page, click the **Delete Workspace** button. 
+3. Follow the prompts on the pop-up to delete your workspace. 
+
+**To delete data from all workspaces in which you have workspace admin permissions:**
+
+1. Sign in to the Segment app. 
+2. Navigate to the [User Settings page](https://app.segment.com/settings/user). 
+3. Click the **Delete Account** button, located at the bottom of the page. 
+4. On the popup, enter your password and select **Yep, delete my account anyway!** to delete your account.
+
+After you delete your workspace or account, Segment removes all data associated with each workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a data purge status update, email the Customer Success team [([email protected])](mailto:[email protected]).
+
+If you do not delete your workspace after you stop using Segment, **your data remains in Segment's internal servers until you submit a written deletion request**.
+
+> warning "Purging data from workspaces deleted prior to March 31, 2022"
+> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment's S3 archive buckets, email the Customer Success team [([email protected])](mailto:[email protected]) to create a support ticket. In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. 
+
+### What is a complete data purge?
+
+A complete data purge is the way Segment removes all workspace and customer data from internal servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team by emailing [([email protected])](mailto:[email protected]). In your email to Customer Success, include either the slug or the ID of the workspace that you'd like to delete. Deletions related to data purges will *not* be forwarded to your connected third-party destinations or raw data destinations. 
+
+> error " "
+> Segment waits for five calendar days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [[email protected]](mailto:[email protected]) to cancel the data purge. After the five-day grace period, the deletion will be irreversible.

src/personas/product-limits.md

@@ -6,7 +6,7 @@ In keeping with Segment's commitment to GDPR and CCPA readiness, Segment offers
 
 [Contact Support](https://segment.com/help/contact/) if you need to process more than 100,000 users within a 30 day period.
 
-> info "Business Plan Customers)"
+> info "Business Plan Customers"
 > If you use this feature to delete data, you can not Replay the deleted data. For standard Replay requests, you must wait for any pending deletions to complete, and you cannot submit new deletion requests for the period of time that Segment replays data for you.
 
 > info ""