Release 23.13.2 (#4503)

markzegarelli · Panandhan22 · vanand17 · web-flow · commit d9dd19244cae · 2023-03-30T10:01:51.000-07:00
* Update index.md * Update index.md * Update index.md * GA updates * [netlify-build] * update note format * Update index.md * Add ERD draft [netlify-build] * Update index.md Updating customers on BT and Team plan are only able to have a warehouse * Update index.md * can't suggest the backticks because of github formatting * Update src/protocols/transform/index.md * Add link for CleverTap server-side support * update info on creating eu-workspaces * Add Engineer feedback [netlify-build] * ERD draft [netlify-build] * Adding historical backfills feedback * Destiantion filters not supported for Mobile Updating our docs to reflect the current status of mobile destination filters. See internal jira LIBWEB-1326 for more info. * reverse etl ga edits * edits * edits * edits * [netlify-build] * [netlify-build] * [netlify-build] * Some rebrand updates * [netlify-build] * [netlify-build] * fixed broken links [netlify-build] * Remove beta note from GA4 Web docs ahead of GA * Remove beta note on Braze Cohorts docs ahead of GA * Remove beta note from Segment Profiles Destination * [netlify-build] * add unify icon [netlify-build] * comment out ERD for now * edits [netlify-build] * Profiles > Unify fixes * Add unify redirects [netlify-build] * edits * Add redirects [netlify-build] * Update src/protocols/transform/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Replay Events don't show in Event delivery tab * add flush policy docs * add flush policy docs * Update ERD draft * UI casing updates * Update src/guides/what-is-replay.md * Update src/connections/destinations/destination-filters.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> * Update mapping info with unsupported characters (#4458) * edits * Update src/connections/destinations/catalog/heap/index.md Nice edits! Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> * Add unify debugger updates * [netlify-build] * edits * build retl catalog [netlify-build] * added blurb to catalog * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> * add integration object info * Redaction changes Changed redaction of a few sentences to make it clearer for clients * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md * Update catalog and slug overrides (#4483) * Scaffold TikTok Audiences Docs (#4466) * Scaffold TikTok Audiences docs * Fix step numbers * remove mention of Segment Audience Key * updates to TikTok Audiences docs * Add private metadata --------- Co-authored-by: kdaswani <49517136+kdaswani@users.noreply.github.com> Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * Update index.md * 20230328 fixes (#4484) * nav fixes * catalog build * Update slugs * fix redirect * Elaborating on who can use what storage destinations * Update index.md * Small edits to TikTok Audiences docs * Update src/connections/destinations/catalog/actions-tiktok-audiences/index.md Co-authored-by: maryamsharif <99763167+maryamsharif@users.noreply.github.com> * Install packages for RN 2.0 have Changed As per our docs here, the install packages are now different. https://github.com/segmentio/analytics-react-native/blob/f3d5bc024fe3ae988386aac8b9f6f3fc6d84677a/README.md#installation * Update src/connections/destinations/catalog/clevertap/index.md * Update src/guides/regional-segment.md * Add ERD to Profiles Sync * Clarify Mobile Device Mode behavior Clarify Mobile Device Mode behavior. Make it more explicit that it is not supported. * Add info about loading plugin for Amplitude (Actions) destination (#4436) * Add info about loading plugin for Amplitude (Actions) destination * Update src/connections/destinations/catalog/actions-amplitude/index.md --------- Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * Update src/engage/audiences/index.md * Update src/engage/audiences/index.md * Update src/engage/audiences/index.md * Update src/engage/audiences/index.md * add C# tags to metadata * edit --------- Co-authored-by: Panandhan22 <115441424+Panandhan22@users.noreply.github.com> Co-authored-by: vanand17 <96406241+vanand17@users.noreply.github.com> Co-authored-by: rchinn-segment <ryan.chinn@segment.com> Co-authored-by: Sarah Rudy <78389005+sarahrudy@users.noreply.github.com> Co-authored-by: Charity Holt <38872070+charholt@users.noreply.github.com> Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> Co-authored-by: bobbyatsegment <93934274+bobbyatsegment@users.noreply.github.com> Co-authored-by: Atif Javed <46914900+muhammadatifjav@users.noreply.github.com> Co-authored-by: Niall Brennan <niallbrennan87@gmail.com> Co-authored-by: stayseesong <STACY.S.SONG@GMAIL.COM> Co-authored-by: kdaswani <49517136+kdaswani@users.noreply.github.com> Co-authored-by: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Co-authored-by: Niall Brennan <niall.brennan@segment.com> Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> Co-authored-by: Ashton Huxtable <78318468+ashton-huxtable@users.noreply.github.com> Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Co-authored-by: Esteban Gonzalez Corti <esteban.gonzalezcorti@segment.com> Co-authored-by: maryamsharif <99763167+maryamsharif@users.noreply.github.com> Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> Co-authored-by: Niall Brennan <nbrennan@twilio.com> Co-authored-by: joeynmq <37472597+joeynmq@users.noreply.github.com>
diff --git a/.github/styles/Vocab/Docs/accept.txt b/.github/styles/Vocab/Docs/accept.txt
@@ -145,6 +145,7 @@ Twilio
 upsert
 US
 utm
+varchar
 Vero
 Vidora
 viewability
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1484,7 +1484,7 @@ items:
     isCloudEventSource: true
     slug: actions-qualtrics
     url: connections/sources/catalog/cloud-apps/actions-qualtrics
-    hidden: true
+    hidden: false
     regions:
       - us
     endpoints:
diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md
@@ -53,13 +53,14 @@ To manually add the Log Purchases Action:
 
 The Amplitude (actions) destination does not offer a device-mode connection mode. If you're using one of Segment's new libraries ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift) or [Kotlin](https://github.com/segmentio/analytics-kotlin)) with the Actions-framework version of the destination, you do not need the device-mode connection.
 
-Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination, includes session ID tracking by default. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Unify Identity Resolution.
+
+Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination, includes session ID tracking by default. When connected to the Analytics.js 2.0 source, Segment automatically loads a plugin on your website for session tracking and enrichment as an alternative to the Amplitude SDK. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution.
 
 Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift) or [Kotlin](https://github.com/segmentio/analytics-kotlin)
 
 
 ### Device ID Mappings
-The Amplitude destination requires that each event include either a Device ID or a User ID. If a User ID isn't present, Amplitude uses the a Device ID, and vice versa, if a Device ID isn't present, Amplitude uses the User ID.
+The Amplitude destination requires that each event include either a Device ID or a User ID. If a User ID isn't present, Amplitude uses a Device ID, and vice versa, if a Device ID isn't present, Amplitude uses the User ID.
 
 By default, Segment maps the Segment property `context.device.id` to the Amplitude property `Device ID`. If `context.device.id` isn't available, Segment maps the property `anonymousId` to the Amplitude `Device ID`. The Actions interface indicates this with the following contents of the Device ID field: `coalesce(` `context.device.id` `anonymousId` `)`.
 
diff --git a/src/connections/destinations/catalog/actions-tiktok-audiences/index.md b/src/connections/destinations/catalog/actions-tiktok-audiences/index.md
@@ -25,7 +25,7 @@ By using Segment's TikTok Audiences destination, you can increase traffic and dr
 
 ### Connect the TikTok Audiences destination
 
-1. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with the TikTok Audiences destination. Either choose an existing Engage Audience or create a new one. This is the Audience you plan to send to TikTok.
+1. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with the TikTok Audiences destination. Either choose an existing Engage audience or create a new one. This is the audience you plan to send to TikTok.
 
 2. Navigate to **Engage > Engage Settings** and click **Destinations**. Please ensure you are still in the correct Engage space.
 
@@ -43,12 +43,12 @@ By using Segment's TikTok Audiences destination, you can increase traffic and dr
 
 9. Repeat Steps 7 and 8 to also set up a **Remove Users** mapping.
      
-10.  Navigate back to **Engage > Audiences** and click on the Audience from Step 1. 
+10.  Navigate back to **Engage > Audiences** and click on the audience from Step 1. 
 
 11.  Click **Add Destinations** and select the TikTok Audiences destination you just created. In the settings that appear in the side panel, toggle the **Send Track** option on and do **not** change the Audience Entered/Audience Exited event names. Click **Save Settings**.
 
-The setup is complete and the audience will start syncing to TikTok. The audience will appear in your [TikTok Ads Manager](https://www.tiktok.com/business/en-US/solutions/ads-manager){:target="_blank"} account under **Assets > Audiences**. Please note that it can take 24-28 hours for users to appear in TikTok.
+The setup is complete and the audience will start syncing to TikTok. The audience will appear in your [TikTok Ads Manager](https://www.tiktok.com/business/en-US/solutions/ads-manager){:target="_blank"} account under **Assets > Audiences**. Please note that it can take 24-48 hours for users to appear in TikTok.
 
 To sync additional audiences from your Engage space, create a separate mapping in the TikTok Audiences destination. Navigate to **Connections > Destinations**, search and select the TikTok Audiences destination, and follow Steps 7-11 above.
 
-{% include components/actions-fields.html settings="true"%}
+{% include components/actions-fields.html %}
diff --git a/src/connections/destinations/catalog/clevertap/index.md b/src/connections/destinations/catalog/clevertap/index.md
@@ -9,7 +9,7 @@ Once the Segment library is integrated, toggle CleverTap on in your Segment dest
 
 You can integrate CleverTap using a server-side or mobile destination (iOS or Android). If you are interested in using CleverTap's push notifications or in-app notifications products, you should use the mobile destinations.
 
-All server-side destination requests require both the Segment `anonymousId` and `userId` in the payload. This is a requirement from CleverTap.
+All server-side destination requests require both the Segment `anonymousId` and `userId` in the payload. This is a requirement from CleverTap. CleverTap maintains the server-side integration. For any issues with the server-side integration, [contact the CleverTap Support team](https://help.clevertap.com/hc/en-us/requests/new){:target="_blank"}.
 
 CleverTap supports the `identify`, `track`, `page` (server-side only), and `screen` (iOS and server-side only) methods.
 
diff --git a/src/connections/destinations/catalog/heap/index.md b/src/connections/destinations/catalog/heap/index.md
@@ -12,7 +12,7 @@ id: 54521fd725e721e32a72eebd
 1. From the Segment web app, click **Catalog**.
 2. Search for "Heap" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. In the destination settings, enter your Heap "App ID" into the connection settings.
-4. If you are using Heap using Segment's client-side `analytics.js` library, we asynchronously load Heap's JavaScript library onto the page. As such, all native functionality of Heap, including auto-capturing of all events.
+4. Remove Heap's snippet from your page if you're using Segment's client-side Analytics.js library to load Heap. With the Analytics.js library, Segment asynchronously loads Heap's JavaScript library onto your page. All native functionality of Heap, including auto-capturing of all events are available to you.  
 
 ## Identify
 
diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md
@@ -10,7 +10,7 @@ rewrite: true
 
 Use destination filters to prevent certain data from flowing into a destination. You can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
 
-You can configure destination filters on cloud-mode, mobile, and web device-mode and actions-based destinations.  With device-mode destinations, you can use the same user interface or API mechanism that you use for your cloud-mode destinations, and have those filters acted upon for device-mode destinations on web and mobile.
+You can configure destination filters on cloud-mode, mobile cloud-mode destinations, and web device-mode and actions-based destinations.  With device-mode destinations, you can use the same user interface or API mechanism that you use for your cloud-mode destinations, and have those filters acted upon for device-mode destinations on web.
 
 Common use cases for destination filters include:
 - Managing PII (personally identifiable information) by blocking fields from reaching certain destinations
@@ -29,7 +29,9 @@ Keep the following limitations in mind when you use destination filters:
 - *(For device-mode)* Destination filters don't filter on native events that the destination SDK collects. Instead, you can use the load option to conditionally load relevant bundled JavaScript on the page. See the docs for [load options](/docs/connections/sources/catalog/libraries/website/javascript/#load-options).
 - *(For device-mode)* Destination filters don't filter some fields that are collected by the destination SDK outside of Segment such as `page.url` and `page.referrer`.
 - *(For web device-mode)* Destination filters for web device-mode only supports the Analytics.js 2.0 source. You need to enable device mode destination filters for your Analytics.js source. To do this, go to your Javascript source and navigate to **Settings > Analytics.js** and turn the toggle on for **Destination Filters**.
-- *(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source. Destination filters for mobile is currently not supported.
+- *(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source.
+- *(For mobile device-mode)* Destination filters for mobile device-mode is currenlty not supported.
+
 
 [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/index.md b/src/connections/sources/catalog/libraries/mobile/react-native/index.md
@@ -29,12 +29,12 @@ To get started with the Analytics for React Native 2.0 library:
 1. Create a React Native Source in Segment.
     1. Go to **Connections > Sources > Add Source**.
     2. Search for React Native and click **Add source**.
-2. Install `@segment/analytics-react-native`, [`@segment/sovran-react-native`](https://github.com/segmentio/sovran-react-native){:target="_blank"} and [`react-native-async-storage/async-storage`](https://github.com/react-native-async-storage/async-storage){:target="_blank"}:
+2. Install `@segment/analytics-react-native`, [`@segment/sovran-react-native`](https://github.com/segmentio/sovran-react-native){:target="_blank"} and [`react-native-get-random-values`](https://github.com/LinusU/react-native-get-random-values){:target="_blank"}:
 
     ```js
-    yarn add @segment/analytics-react-native @segment/sovran-react-native @react-native-async-storage/async-storage
+    yarn add @segment/analytics-react-native @segment/sovran-react-native react-native-get-random-values
     # or
-    npm install --save @segment/analytics-react-native @segment/sovran-react-native @react-native-async-storage/async-storage
+    npm install --save @segment/analytics-react-native @segment/sovran-react-native react-native-get-random-values
     ```
 3. If you're using iOS, install native modules with:
 
@@ -682,5 +682,32 @@ const segmentClient = createClient({
 ```
 ### What is the instanceId set in context?
 The instanceId was introduced in [V 2.10.1](https://github.com/segmentio/analytics-react-native/releases/tag/%40segment%2Fanalytics-react-native-v2.10.1) and correlates events to a particular instance of the client in a scenario when you might have multiple instances on a single app. 
+
+### How do I interact with the integrations object?
+The integrations object is no longer part of the Segment events method signature. To access the integrations object and control what destinations the event reaches, you can use a Plugin:
+
+```js
+import {
+    EventType,
+    Plugin,
+    PluginType,
+    SegmentEvent,
+  } from '@segment/analytics-react-native';
+  
+  export class Modify extends Plugin {
+    type = PluginType.before;
+  
+    async execute(event: SegmentEvent) {
+      if (event.type == EventType.TrackEvent) {
+        let integrations = event.integrations;
+        if (integrations !== undefined) {
+          integrations['Appboy'] = false;
+        }
+      }
+      //console.log(event);
+      return event;
+    }
+  }
+```
 ## Changelog
 [View the Analytics React Native 2.0 changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.
diff --git a/src/connections/sources/catalog/libraries/server/net/index.md b/src/connections/sources/catalog/libraries/server/net/index.md
@@ -2,8 +2,11 @@
 title: Analytics for .NET
 repo: analytics.NET
 id: 8HWbgPTt3k
+tags:
+  - C#
+  - C-sharp
 ---
-Our .NET library is the best way to integrate analytics into your .NET application or website. It lets you record analytics data from your ASP.NET, C#, F#, and Visual Basic code. The library issues requests that hit our servers, and then we route your data to any analytics service you enable on our destinations page. This library is open-source, so you can [check it out on GitHub](https://github.com/segmentio/Analytics.NET).
+Segment's .NET library is the best way to integrate analytics into your .NET application or website. It lets you record analytics data from your ASP.NET, C#, F#, and Visual Basic code. The library issues requests that hit our servers, and then Segment routes your data to any analytics service you enable on our destinations page. This library is open-source, so you can [check it out on GitHub](https://github.com/segmentio/Analytics.NET).
 
 All of Segment's server-side libraries are built for high-performance, so you can use them in your web server controller code. This library uses an internal queue to make `identify` and `track` calls non-blocking and fast. It also batches messages and flushes asynchronously to our servers.
 
diff --git a/src/connections/storage/index.md b/src/connections/storage/index.md
@@ -5,13 +5,13 @@ title: Data Storage overview
 Off-the-shelf analytics tools (like Google Analytics and Mixpanel) offer quick and easy insights about common business questions, and often meet the needs of marketing teams and product managers. However, data analysts and data scientists need access to an organization's raw data to derive deeper and more customized insights to support their organization.
 
 > success ""
-> Warehouse Destination are only available and functional for Business and Team Tier customers.
+> Only users with Business or Team plans can add Warehouse destinations.
 
 Segment offers several [Data Storage Destinations](/docs/connections/storage/catalog/) to help you store your raw Segment data, including:
 
-- [Data Warehouses](/docs/connections/storage/warehouses/) (SQL-based databases, such as Postgres and Redshift)
-- [Amazon S3](/docs/connections/storage/catalog/amazon-s3/)
-- [Google Cloud Storage](/docs/connections/storage/catalog/google-cloud-storage/)
+- [Data Warehouses](/docs/connections/storage/warehouses/) (available to Team and Business Tier customers)
+- [AWS S3](/docs/connections/storage/catalog/aws-s3/) (available to all users)
+- [Google Cloud Storage](/docs/connections/storage/catalog/google-cloud-storage/) (available to all users)
 - [Segment Data Lakes](/docs/connections/storage/data-lakes/) (available to Business Tier customers only)
 
 
diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md
@@ -212,3 +212,10 @@ Before you can download the CSV, you will need to generate it. There are three d
     (If the audience recalculates between when you click Generate and when you download the file, you might want to regenerate the file. The CSV is a snapshot from when you clicked Generate, and could be outdated.)</td>
   </tr>
 </table>
+
+## Identifier Breakdown
+
+The audience summary is a breakdown of the percentages of external_ids of users in the audience. These are the default IDs that Segment includes in the Identity resolution configuration. Segment displays the percentage of the audience with each identifier, which you can use to verify the audience size and profiles are correct.
+
+> info ""
+> The Identifier Breakdown won't show custom IDs included in the Identity resolution configuration. Segment only displays external IDs in the breakdown.
diff --git a/src/guides/regional-segment.md b/src/guides/regional-segment.md
@@ -55,7 +55,7 @@ When you send data from a server-side or project source, you can use the `host`
 > info ""
 > Use [this form](https://segment.typeform.com/to/k5ADnN5e#user_id=xxxxx){:target="_blank"} if you need to transition from your existing US-based workspace to an EU workspace.
 
-To create a workspace with a different data processing region:
+To create a workspace with a different data processing region, reach out to the Segment Support team, and they will assist you with enabling the feature. Once the feature has been enabled, you'll be able to self-serve and create a new workspace in a different data processing region by following these steps:
 
 1. Log in to your Segment account.
 2. Click **New Workspace**.
diff --git a/src/protocols/transform/index.md b/src/protocols/transform/index.md
@@ -95,7 +95,17 @@ Depending on the type of transformation you selected, you will need to enter the
 After you select the scope, use the search box to choose the event to transform. You can **only** select a single track event, identify or group call. If you are renaming the event, simply enter the new name in the provided text field.
 
 * **Rename properties or traits:**
-If you rename properties or traits within a selected event, click **+ Add Property**. The dropdown that appears contains the properties or traits sent with the selected event. Segment supports JSON Path notation to select nested objects up to four levels deep. For example, `order.id` selects the `id` property in the `order` object. Segment does not support `.$.` notation to select a property from an array of objects.
+To rename properties or traits within a selected event, click **+ Add Property**. The dropdown that appears contains the properties or traits sent with the selected event. Segment supports JSON Path notation to select nested objects up to four levels deep. For example, `order.id` selects the `id` property in the `order` object. Segment does not support `.$.` notation to select a property from an array of objects. For example, the following event, which generates `products.$.product_id`, is unsupported.
+
+```js
+analytics.track('Example', {
+  products: [{
+      product_id: "123"
+  }],
+})
+```
+
+In this scenario, we do not support the transformation of product_id. 
 
 After selecting a property/trait, select JSON Path or Simple String to change the property/trait. Simple string will change the name in-line, while JSON path allows you to move the property/trait in or out of an object.
 
diff --git a/src/unify/files/ERD.png b/src/unify/files/ERD.png
diff --git a/src/unify/profiles-sync/overview.md b/src/unify/profiles-sync/overview.md
@@ -51,8 +51,6 @@ To learn more about Profiles Sync, visit the following docs:
 - [Sample Queries](/docs/unify/profiles-sync/sample-queries/): View sample queries you can run to help you familiarize yourself with Profiles Sync.
 - [Tables and materialized views](/docs/unify/profiles-sync/tables/): Learn how to use data sets and models that Segment provides to enrich customer profiles.
 
-{% comment %} (commenting out ERD draft for now)
+
 > info ""
 > For more on Profiles Sync logic, table mappings, and data types, download this [Profiles Sync ERD](/docs/unify/files/ERD.png).
-
-{% endcomment %}
diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md

-Original file line number
+Diff line change
 upsert
 US
 utm
 +varchar
 Vero
 Vidora
 viewability