From a70cda56fefae322d37db4af4069e5a91e95d17a Mon Sep 17 00:00:00 2001
From: pwseg <paul.wooley@segment.com>
Date: Mon, 5 Dec 2022 16:31:03 -0600
Subject: [PATCH 1/2] Add Events at Limits Updates

---
 src/engage/faqs.md                 |  4 ++--
 src/profiles/faqs.md               |  3 ++-
 src/profiles/profile-api-limits.md | 10 +++++-----
 3 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/src/engage/faqs.md b/src/engage/faqs.md
index e997bbdb9f..229a439002 100644
--- a/src/engage/faqs.md
+++ b/src/engage/faqs.md
@@ -66,14 +66,14 @@ The audience in the image below includes all users that have Product Added in th
 > info ""
 > Funnel Audiences compute based on all instances of the parent event within the lookback period. This means that if you have a user that Product Added ⟶ Order Completed ⟶ Product Added, this user would be entered into the Abandoned Cart state despite having previously completed an order.
 
-<!--PW 9/6/22 ## What is Engage Merge Protection?
+## What is Engage Merge Protection?
 Engage merge protection algorithm protects your identity graph from unnecessary merges by finding and removing untrusted external IDs. Here's an example:
 
 ![Merge protection](images/merge_protection.png "An image representing the merge protection flow")
 
 In this example, `anonymous_id: a1` is not reset during a `User Logout`. Without merge protection rules, Segment would merge `user_id u1` and `user_id u2`. Instead, the identity resolution algorithm detects that such a merge would break `user_id` uniqueness and prevents the merge.
 
-This is especially helpful for preventing "blob users" that are merged together by non-unique anonymous IDs or by common group emails like `team@company.com`. -->
+This is especially helpful for preventing "blob users" that are merged together by non-unique anonymous IDs or by common group emails like `team@company.com`.
 
 ## Which destinations support syncing the identity graph?
 Most destinations on the Segment Platform are built up around a user model. They assume that a user will have a single userId. Further, most Destinations are not built to handle anonymous traffic.
diff --git a/src/profiles/faqs.md b/src/profiles/faqs.md
index 9d5d0d3c73..35dec9cde9 100644
--- a/src/profiles/faqs.md
+++ b/src/profiles/faqs.md
@@ -17,7 +17,6 @@ Identity Graph automatically collects a rich set of external IDs without any add
 
 If you want Identity Graph to operate on a different custom ID, you can pass it in using `context.externalIds` on an `identify()` or `track()`. If you're interested in this feature, contact your CSM to discuss the best way to implement this feature.
 
-<!--PW 9/6/22
 ## How does Profiles handle identity merging?
 Each incoming event is analyzed and external IDs are extracted (`user_id`, `anonymous_id`, `email`). The simplified algorithm works as follows:
 
@@ -27,6 +26,8 @@ Each incoming event is analyzed and external IDs are extracted (`user_id`, `anon
 4. If Segment finds multiple matching profiles, Segment applies the identity resolution settings for merge protection. Specifically, Segment uses identifier limits and priorities to add the correct identifiers to the profile.
 5. Segment then applies [Profile limits](/docs/profiles/profile-api-limits/) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue.
 
+<!-- PW, 12/5/22
+
 ![Identity graph merging](images/merging_1.png "Flowchart of Segment receiving an incoming event")
 
 ![Identity graph merging](images/merging_2.png "Flowchart of Segment searching for profiles by external ID")
diff --git a/src/profiles/profile-api-limits.md b/src/profiles/profile-api-limits.md
index 772a79dcb6..796e643a71 100644
--- a/src/profiles/profile-api-limits.md
+++ b/src/profiles/profile-api-limits.md
@@ -15,8 +15,8 @@ redirect_from:
 
 ## Identity
 
-| name              | Limit         | Details                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| ----------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Identity Merges   | 100 merges    | Engage supports up to 100 merges per profile in its identity graph. Merges occur when a common `external_id` joins two existing profiles. For example, if a user initiates a mobile session but then signs in through a web application, a common identifier like `user_id` will join the two user profiles. Segment drops additional message merge attempts, which usually indicate corrupt profiles. Once the limit is reached, Segment rejects additional events. |
-| Identity Mappings | 1000 mappings | Engage supports up to 1000 mappings per profile in its identity graph. Mappings are external identifier values like a `user_id`, email, mobile advertising `id`, or any custom identifier. Segment drops additional message mapping attempts, which usually indicate corrupt profiles. This limit counts mappings across all merged profiles.                                                                                                                    |
-| Identify calls    | 300 traits    | Engage rejects Identify events with 300 or more traits. If your use case requires more than 300 traits, you can split the traits into multiple Identify calls.                                                                                                                                                                                                                                                                                                   |
+| name              | Limit         | Details                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ----------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Identity Merges   | 100 merges    | Engage supports up to 100 merges per profile in its identity graph. Merges occur when a common `external_id` joins two existing profiles. For example, if a user initiates a mobile session but then signs in through a web application, a common identifier like `user_id` will join the two user profiles. No additional merges will be added once the profile reaches this limit. Event resolution for the profile, however, will continue. |
+| Identity Mappings | 1000 mappings | Engage supports up to 1000 mappings per profile in its identity graph. Mappings are external identifier values like a `user_id`, email, mobile advertising `id`, or any custom identifier. No additional mappings will be added once the profile reaches this limit. Event resolution for the profile, however, will continue.                                                                                                                 |
+| Identify calls    | 300 traits    | Engage rejects Identify events with 300 or more traits. If your use case requires more than 300 traits, you can split the traits into multiple Identify calls.                                                                                                                                                                                                                                                                                 |

From 9431cd8a0f57d46a40ca8ae84aba97b5c4cf07de Mon Sep 17 00:00:00 2001
From: pwseg <86626706+pwseg@users.noreply.github.com>
Date: Mon, 5 Dec 2022 16:43:24 -0600
Subject: [PATCH 2/2] Add Liquid Comments

---
 src/profiles/faqs.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/profiles/faqs.md b/src/profiles/faqs.md
index 35dec9cde9..4246a3e968 100644
--- a/src/profiles/faqs.md
+++ b/src/profiles/faqs.md
@@ -26,13 +26,15 @@ Each incoming event is analyzed and external IDs are extracted (`user_id`, `anon
 4. If Segment finds multiple matching profiles, Segment applies the identity resolution settings for merge protection. Specifically, Segment uses identifier limits and priorities to add the correct identifiers to the profile.
 5. Segment then applies [Profile limits](/docs/profiles/profile-api-limits/) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue.
 
-<!-- PW, 12/5/22
+{% comment %}
 
 ![Identity graph merging](images/merging_1.png "Flowchart of Segment receiving an incoming event")
 
 ![Identity graph merging](images/merging_2.png "Flowchart of Segment searching for profiles by external ID")
 
-![Identity graph merging](images/merging_3.png "Flowchart of Segment merging profiles") -->
+![Identity graph merging](images/merging_3.png "Flowchart of Segment merging profiles") 
+
+{% endcomment %}
 
 ## Is all matching deterministic, or is there any support for probabilistic matching?
 All Profile matching is deterministic and based on first-party data that you've collected.