Skip to content

Release 22.13.2 #2684

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 71 commits into from
Mar 31, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
71 commits
Select commit Hold shift + click to select a range
6888604
Basic first draft of BCR compliance docs
forstisabella Mar 1, 2022
afb5c20
DOC-460 Content updates
forstisabella Mar 3, 2022
2d34465
DOC-360 Forgot to save
forstisabella Mar 3, 2022
3842fb6
DOC-460 Updating BCR page with info from meeting with PM
forstisabella Mar 4, 2022
cf6648d
DOC-460 added status update note, removed weasel words
forstisabella Mar 4, 2022
1c2afee
DOC-460 updating an answer, minor grammar edits
forstisabella Mar 7, 2022
01c3011
DOC-460 Editing pass
forstisabella Mar 7, 2022
9b592c0
DOC-460 More edits
forstisabella Mar 7, 2022
dc3696c
[netlify-build]
forstisabella Mar 7, 2022
5b419ac
Apply suggestions from code review!
forstisabella Mar 8, 2022
ff502c7
Separating account deletion and BCR pages [netlify-build]
forstisabella Mar 9, 2022
1969a05
DOC-460 Editing pass [netlify-build]
forstisabella Mar 9, 2022
63deeb6
[netlify-build]
forstisabella Mar 9, 2022
2507c34
Merge branch 'develop' into DOC-460-IF
forstisabella Mar 9, 2022
086c295
Editing pass [netlify-build]
forstisabella Mar 10, 2022
01f21c3
Removing BCR compliance page, as per legal [netlify-build]
forstisabella Mar 10, 2022
b8ea3db
Removing BCR from main nav [netlify-build]
forstisabella Mar 10, 2022
528e5d5
Fixing side nav [netlify-build]
forstisabella Mar 10, 2022
f5457fa
DOC-460 Small change requested by Legal
forstisabella Mar 15, 2022
1e5cd2c
[netlify-build]
forstisabella Mar 16, 2022
d56882d
[netlify-build]
forstisabella Mar 16, 2022
6bf462e
Merge branch 'develop' into DOC-460-IF
forstisabella Mar 16, 2022
f55d84c
[netlify-build]
forstisabella Mar 16, 2022
62a605b
DOC-460 netlify troubleshooting [netlify-build]
forstisabella Mar 16, 2022
9d9c3a7
Fixing changes [netlify-build]
forstisabella Mar 16, 2022
7be19c9
DOC-452 Vale updates, adding table headers
forstisabella Mar 18, 2022
9936523
DOC-452 Updating collections table, adding tables for each new collec…
forstisabella Mar 18, 2022
f2c65ec
DOC-452 Fixing links
forstisabella Mar 18, 2022
eb582a5
Updating the type for two new collections DOC-452
forstisabella Mar 21, 2022
8b086a1
DOC-453 Updating the order of new properties, linking the property in…
forstisabella Mar 21, 2022
8cd0bdd
DOC-452 Removing mystery property
forstisabella Mar 22, 2022
a52686c
Merge branch 'develop' into DOC-452-IF
forstisabella Mar 22, 2022
9684a72
[netlify-build]
forstisabella Mar 22, 2022
a837732
DOC-452 Fixing HTML weirdness [netlify-build]
forstisabella Mar 22, 2022
262d50e
DOC-452 Making changes requested by PM [netlify-build]
forstisabella Mar 22, 2022
f745d9a
DOC-452 Fixing duplicate description [netlify-build]
forstisabella Mar 22, 2022
f74634f
Apply suggestions from code review [netlify-build]
forstisabella Mar 23, 2022
2f7709b
DOC-452 HTML tables -> MD tables (1/2)
forstisabella Mar 23, 2022
3ca095c
DOC-452 Fixing small spelling error
forstisabella Mar 23, 2022
afaf692
DOC-452 HTML -> MD tables (2/2) [netlify-build]
forstisabella Mar 23, 2022
b7dd243
MoEngage SDK version 12, 8 document update
umangmoe Mar 25, 2022
2c6951e
swift package manager support added.
umangmoe Mar 25, 2022
a38fb16
Minor edits
rchinn1 Mar 26, 2022
6ef0beb
DOC-452 Changing properties based on PM feedback
forstisabella Mar 28, 2022
1974dd2
Merge branch 'develop' into DOC-460-IF
forstisabella Mar 28, 2022
ce26a34
[netlify-build]
forstisabella Mar 28, 2022
3c5a776
[netlify-build]
stayseesong Mar 29, 2022
590acf5
DOC-452 Updating collection descriptions as per engineering [netlify-…
forstisabella Mar 29, 2022
dca8660
Merge pull request #288 from segmentio/repo-sync
bot-docsteam Mar 29, 2022
c6c7bb6
Update src/connections/destinations/catalog/moengage/index.md
rchinn1 Mar 29, 2022
ca878e2
Update src/connections/destinations/catalog/moengage/index.md
rchinn1 Mar 29, 2022
7aa6f73
Merge branch 'develop' into develop
rchinn1 Mar 29, 2022
353ea49
Correcting Page methods name
markurquhart Mar 30, 2022
6343259
Merge pull request #2657 from umangmoe/develop
rchinn1 Mar 30, 2022
86fd02d
Merge pull request #289 from segmentio/repo-sync
bot-docsteam Mar 30, 2022
3ff44f1
Merge pull request #2677 from segmentio/repo-sync
bot-docsteam Mar 30, 2022
d82c2c4
Merge pull request #2673 from segmentio/issue-2605
stayseesong Mar 31, 2022
5e6425f
Merge pull request #2678 from segmentio/repo-sync
bot-docsteam Mar 31, 2022
abea117
Merge pull request #290 from segmentio/repo-sync
bot-docsteam Mar 31, 2022
ccbeed2
Merge pull request #2676 from markurquhart/issue-2669
pwseg Mar 31, 2022
c130eea
Merge pull request #2679 from segmentio/repo-sync
bot-docsteam Mar 31, 2022
ad75013
Merge pull request #291 from segmentio/repo-sync
bot-docsteam Mar 31, 2022
04dca4e
Update Ambassador destination docs
tobiordobi Mar 31, 2022
02e882d
Update index.md
tobiordobi Mar 31, 2022
b0c02e2
[DOC-452] Addressing comments left in code review [netlify-build]
forstisabella Mar 31, 2022
7905853
Merge pull request #2632 from segmentio/DOC-452-IF
forstisabella Mar 31, 2022
9254274
Merge pull request #2682 from segmentio/repo-sync
bot-docsteam Mar 31, 2022
72ab43e
Merge pull request #2570 from segmentio/DOC-460-IF
forstisabella Mar 31, 2022
c5f3941
Update product-limits.md
pwseg Mar 31, 2022
d3ff479
Merge pull request #2681 from segmentio/tobiordobi-patch-1
pwseg Mar 31, 2022
7028571
Merge pull request #2683 from segmentio/DOC-454-journeys-limits-repac…
pwseg Mar 31, 2022
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/_data/sidenav/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion src/connections/destinations/catalog/ambassador/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
124 changes: 83 additions & 41 deletions src/connections/destinations/catalog/moengage/index.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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:
Expand Down
6 changes: 3 additions & 3 deletions src/connections/destinations/methods-compare.md
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand All @@ -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 %}
1,029 changes: 296 additions & 733 deletions src/connections/sources/catalog/cloud-apps/zendesk/index.md

Large diffs are not rendered by default.

15 changes: 5 additions & 10 deletions src/personas/product-limits.md
Original file line number Diff line number Diff line change
Expand Up @@ -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. |
50 changes: 50 additions & 0 deletions src/privacy/account-deletion.md
Original file line number Diff line number Diff line change
@@ -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 [(friends@segment.com)](mailto:friends@segment.com) 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 [(friends@segment.com)](mailto:friends@segment.com).

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 [(friends@segment.com)](mailto:friends@segment.com) 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 [(friends@segment.com)](mailto:friends@segment.com). 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 [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible.
2 changes: 1 addition & 1 deletion src/privacy/user-deletion-and-suppression.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 ""
Expand Down