Merge pull request #5566 from segmentio/MStephen024-patch-5

Update Engage Section.md

Author: stayseesong

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

@@ -1,6 +1,7 @@
 ---
 title: Kustomer Destination
 rewrite: true
+hide-personas-partial: true
 id: 5c73feeb9947e900010a60ac
 ---
 [Kustomer](https://www.kustomer.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is the next-generation customer management platform for the people-first enterprise. It enables support teams to get a holistic view of the customers they are engaging with, resulting in meaningful interactions between businesses and customers.
@@ -77,4 +78,8 @@ analytics.track("Registered", {
 });
 ```
 
-Track calls will sent as a `tracking event` to Kustomer on the timeline of the customer who was tracked. If the `kustomer_session_id` is included, it will cluster this tracking event into a single "session" on the customer's timeline. If no `kustomer_session_id` is supplied, we will automatically generate session IDs based on time between tracking events. (Read why Segment doesn't have session tracking [here](https://segment.com/blog/facts-vs-stories-why-segment-has-no-sessions-api/){:target="_blank”}).
+Track calls send as a `tracking event` to Kustomer on the timeline of the customer who was tracked. If the `kustomer_session_id` is included, it clusters this tracking event into a single "session" on the customer's timeline. If no `kustomer_session_id` is supplied, Segment automatically generates session IDs based on time between tracking events. See why [Segment doesn't have session tracking](https://segment.com/blog/facts-vs-stories-why-segment-has-no-sessions-api/){:target="_blank”}.
+
+
+## Engage limitation
+The Kustomer destination only accepts standard properties such as name, email, and phone. It doesn't support custom properties. Any Audience or Computed Trait created in Engage is considered a customer property by Kustomer destination and isn't supported.