merge master

Author: markzegarelli

.github/styles/Vocab/Docs/accept.txt

@@ -145,6 +145,7 @@ Twilio
 upsert
 US
 utm
+varchar
 Vero
 Vidora
 viewability

src/engage/user-subscriptions/subscription-sql.md

@@ -23,7 +23,7 @@ To use Subscriptions with SQL Traits, you need the following:
 
 ## Sync subscription data with SQL
 
-You can sync with SQL from two locations in the Segment app. Navigate to **Profiles > Profile explorer** or **Engage > Audiences > Profile explorer**, then:
+You can sync with SQL from two locations in the Segment app. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer**, then:
 
 1. Click **Manage subscription statuses**, and select **Update subscription statuses**.
 2. Select **Sync with SQL**, and click **Configure**.
@@ -64,7 +64,7 @@ You can schedule sync intervals to import subscription data from your warehouse
 
 Use the Update History page to view all SQL jobs.
 
-1. Navigate to **Profiles > Profile explorer** or **Engage > Audiences > Profile explorer.**
+1. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer.**
 2. Click **Manage subscription statuses**.
 3. Select **View update history**, then select the **SQL Jobs** tab.
 
@@ -76,7 +76,7 @@ When you build your SQL query, keep the following requirements in mind for the d
 
 **Your query must:**
 
-- Return at least one column with `user_id`, `anonymous_id`, `email`, `phone` (or `group_id` for account traits if Profiles for B2B is enabled).
+- Return at least one column with `user_id`, `anonymous_id`, `email`, `phone` (or `group_id` for account traits if Unify for B2B is enabled).
 - Return records less than 16KB in size.
 
 **Your query must not:**

src/unify/profiles-sync/index.md

@@ -103,6 +103,9 @@ To start seeing unified profiles in your warehouse and build attribution models,
 
 Please visit [Tables you materialize](/docs/unify/profiles-sync/tables/#tables-you-materialize) for more on how to materialize these views either on your own, or with [Segment's open source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="blank"}.
 
+> warning ""
+> Please note that dbt models are in beta and need modifications to run efficiently on BigQuery, Synapse, and Postgres warehouses. Segment is actively working on this feature. 
+
 ## Profiles Sync limits
 
 As you use Profiles Sync, please keep the following limits in mind:

src/unify/profiles-sync/tables.md

@@ -92,11 +92,11 @@ Using the profile merge scenario, Segment would generate three new entries to th
 
 <div style="overflow-x:auto;" markdown=1>
 
-| `segment_id` (varchar) | `canonical_segment_id` (varchar) | `triggering_event_type` (varchar) | `triggering_event_id` (varchar) | `timestamp` (datetime)        |
-| ------------ | ---------------------- | ----------------------- | --------------------- | ------------------- |
-| `profile_1`  | `profile_1`            | `page`                  | `event_1`             | 2022-05-02 14:01:00 |
-| `profile_2`  | `profile_2`            | `page`                  | `event_3`             | 2022-06-22 10:47:15 |
-| `profile_2`  | `profile_1`            | `identify`              | `event_4`             | 2022-06-22 10:48:00 |
+| `segment_id` (varchar) | `canonical_segment_id` (varchar) | `triggering_event_type` (varchar) | `triggering_event_id` (varchar) | `timestamp` (datetime) |
+| ---------------------- | -------------------------------- | --------------------------------- | ------------------------------- | ---------------------- |
+| `profile_1`            | `profile_1`                      | `page`                            | `event_1`                       | 2022-05-02 14:01:00    |
+| `profile_2`            | `profile_2`                      | `page`                            | `event_3`                       | 2022-06-22 10:47:15    |
+| `profile_2`            | `profile_1`                      | `identify`                        | `event_4`                       | 2022-06-22 10:48:00    |
 
 </div>
 
@@ -117,11 +117,11 @@ The anonymous site visits sample used earlier would generate the following event
 
 <div style="overflow-x:auto;" markdown=1>
 
-| `segment_id` (varchar) | `external_id_type` (varchar) | `external_id_value` (varchar)     | `triggering_event_type` (varchar) | `triggering_event_id` (varchar) | `timestamp` (datetime)        |
-| ------------ | -------------------| ------------------------| ----------------------- |-----------------------| ------------------- |
-| `profile_1`  | `anonymous_id`     | `5285bc35-05ef-4d21`    | `page`                  | `event_1`             | 2022-05-02 14:01:00 |
-| `profile_1`  | `email`            | `[email protected]`  | `identify`              | `event_2`             | 2022-05-02 14:01:47 |
-| `profile_2`  | `anonymous_id`     | `b50e18a5-1b8d-451c`    | `page`                  | `event_3`             | 2022-06-22 10:48:00 |
+| `segment_id` (varchar) | `external_id_type` (varchar) | `external_id_value` (varchar) | `triggering_event_type` (varchar) | `triggering_event_id` (varchar) | `timestamp` (datetime) |
+| ---------------------- | ---------------------------- | ----------------------------- | --------------------------------- | ------------------------------- | ---------------------- |
+| `profile_1`            | `anonymous_id`               | `5285bc35-05ef-4d21`          | `page`                            | `event_1`                       | 2022-05-02 14:01:00    |
+| `profile_1`            | `email`                      | `[email protected]`        | `identify`                        | `event_2`                       | 2022-05-02 14:01:47    |
+| `profile_2`            | `anonymous_id`               | `b50e18a5-1b8d-451c`          | `page`                            | `event_3`                       | 2022-06-22 10:48:00    |
 
 </div>
 
@@ -142,21 +142,21 @@ The previous result would generate two entries in the `pages` table:
 
 <div style="overflow-x:auto;" markdown=1>
 
-| `segment_id` (varchar) | `context_url` (array)         | `anonymous_id` (varchar)      | `event_source_id` (varchar) | `event_id` (varchar) | `timestamp` (datetime)        |
-| ------------ | ---------------------- | -------------------- | ----------------- | ---------- | ------------------- |
-| `profile_1`  | `twilio.com`           | `5285bc35-05ef-4d21` | `source_1`        | `event_1`  | 2022-05-02 14:01:00 |
-| `profile_2`  | `twilio.com/education` | `b50e18a5-1b8d-451c` | `source_1`        | `event_3`  | 2022-06-22 10:47:15 |
+| `segment_id` (varchar) | `context_url` (array)  | `anonymous_id` (varchar) | `event_source_id` (varchar) | `event_id` (varchar) | `timestamp` (datetime) |
+| ---------------------- | ---------------------- | ------------------------ | --------------------------- | -------------------- | ---------------------- |
+| `profile_1`            | `twilio.com`           | `5285bc35-05ef-4d21`     | `source_1`                  | `event_1`            | 2022-05-02 14:01:00    |
+| `profile_2`            | `twilio.com/education` | `b50e18a5-1b8d-451c`     | `source_1`                  | `event_3`            | 2022-06-22 10:47:15    |
 
 </div>
 
 And two entries in the `identifies` table:
 
 <div style="overflow-x:auto;" markdown=1>
 
-| `segment_id` (varchar) | `context_url` (array)                | `anonymous_id` (varchar)      | `email`  (varchar)              | `event_source_id` (varchar) | `event_id` (varchar) | `timestamp` (datetime)        |
-| ------------ | ---------------------------- | -------------------- | ---------------------- | ----------------- | ---------- | ------------------- |
-| `profile_1`  | `twilio.com/try_twilio`      | `5285bc35-05ef-4d21` | `[email protected]` | `source_1`        | `event_2`  | 2022-05-02 14:01:47 |
-| `profile_2`  | `twilio.com/events/webinars` | `b50e18a5-1b8d-451c` | `[email protected]` | `source_2`        | `event_4`  | 2022-06-22 10:48:00 |
+| `segment_id` (varchar) | `context_url` (array)        | `anonymous_id` (varchar) | `email`  (varchar)     | `event_source_id` (varchar) | `event_id` (varchar) | `timestamp` (datetime) |
+| ---------------------- | ---------------------------- | ------------------------ | ---------------------- | --------------------------- | -------------------- | ---------------------- |
+| `profile_1`            | `twilio.com/try_twilio`      | `5285bc35-05ef-4d21`     | `[email protected]` | `source_1`                  | `event_2`            | 2022-05-02 14:01:47    |
+| `profile_2`            | `twilio.com/events/webinars` | `b50e18a5-1b8d-451c`     | `[email protected]` | `source_2`                  | `event_4`            | 2022-06-22 10:48:00    |
 
 </div>
 
@@ -188,6 +188,9 @@ Follow the steps below to change your schema name:
 > info "dbt model definitions package"
 > To get started with your table materializations, try Segment's [open-source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="_blank"}, or materialize views with your own tools.
 
+> warning ""
+> Please note that dbt models are in beta and need modifications to run efficiently on BigQuery, Synapse, and Postgres warehouses. Segment is actively working on this feature. 
+
 Every customer profile (or `canonical_segment_id`) will be represented in each of the following tables.
 
 ### `id_graph` table
@@ -196,10 +199,10 @@ This table represents the current state of your identity graph, showing only whe
 
 The most recent entry for each `segment_id` from `id_graph_updates` reflects this. After the four example events, `id_graph` would show the following:
 
-| `segment_id` (varchar) | `canonical_segment_id` (varchar) | `timestamp`  (datetime)       |
-| ------------ | ---------------------- | ------------------- |
-| `profile_1`  | `profile_1`            | 2022-05-02 14:01:00 |
-| `profile_2`  | `profile_1`            | 2022-06-22 10:48:00 |
+| `segment_id` (varchar) | `canonical_segment_id` (varchar) | `timestamp`  (datetime) |
+| ---------------------- | -------------------------------- | ----------------------- |
+| `profile_1`            | `profile_1`                      | 2022-05-02 14:01:00     |
+| `profile_2`            | `profile_1`                      | 2022-06-22 10:48:00     |
 
 Segment drops most diagnostic information from this table, since it’s designed for reference use. In this case, you’d learn that any data references to `profile_2` or `profile_1` now map to the same customer, `profile_1`.
 
@@ -209,11 +212,11 @@ Use this table to view the full, current-state mapping between each external ide
 
 In the case study example, you’d see the following:
 
-| `canonical_segment_id` (varchar) | `external_id_type` (varchar) | `external_id_value` (varchar)   | `timestamp` (datetime)          |
-| ---------------------- | ------------------ | ---------------------- | --------------------- |
-| `profile_1`            | `anonymous_id`     | `5285bc35-05ef-4d21`   | `2022-05-02 14:01:00` |
-| `profile_1`            | `email`            | `[email protected]` | `2022-05-02 14:01:47` |
-| `profile_1`            | `anonymous_id`     | `b50e18a5-1b8d-451c`   | `2022-06-22 10:48:00` |
+| `canonical_segment_id` (varchar) | `external_id_type` (varchar) | `external_id_value` (varchar) | `timestamp` (datetime) |
+| -------------------------------- | ---------------------------- | ----------------------------- | ---------------------- |
+| `profile_1`                      | `anonymous_id`               | `5285bc35-05ef-4d21`          | `2022-05-02 14:01:00`  |
+| `profile_1`                      | `email`                      | `[email protected]`        | `2022-05-02 14:01:47`  |
+| `profile_1`                      | `anonymous_id`               | `b50e18a5-1b8d-451c`          | `2022-06-22 10:48:00`  |
 
 
 ### `profile_traits` table
@@ -226,10 +229,10 @@ If Segment later merges away a profile, it populates the `segment_id` it merged
 
 In the case study example, Segment only collected email.  As a result, Segment would generate the following `profile_traits` table:
 
-| `canonical_segment_id` (varchar) | `email`  (varchar)       | `merged_to` (varchar)|
-| ---------------------- | ---------------------- | ----------- |
-| `profile_1`            | `[email protected]` |             |
-| `profile_2`            |                        | `profile_1` |
+| `canonical_segment_id` (varchar) | `email`  (varchar)     | `merged_to` (varchar) |
+| -------------------------------- | ---------------------- | --------------------- |
+| `profile_1`                      | `[email protected]` |                       |
+| `profile_2`                      |                        | `profile_1`           |
 
 > info "Merged profiles"
 > Profiles that Segment merges away are no longer canonical.