Update quality-foundation-implementation-guide.mdx

added table

src/content/docs/new-relic-solutions/observability-maturity/customer-experience/quality-foundation-implementation-guide.mdx

@@ -27,6 +27,7 @@ Digital customer experience includes web, mobile, and IoT. The first version of
 Quality Foundation is about creating a standard practice to help you understand your digital customer experience in a meaningful way.
 
 ## Desired Outcome [#desired-outcome]
+
 This implementation guide will help you:
 
 * Look at customer experience in relation to:
@@ -133,10 +134,10 @@ Quality Foundation measures the following KPIs:
 * [SPA enabled for single page applications](/docs/new-relic-solutions/best-practices-guides/full-stack-observability/browser-monitoring-best-practices-guide/#how-to-do-it)
 *  Synthetics monitors configured:
 
-    - [Ping monitors configured for anonymous users ](/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors/)
-    - [Scripted synthetics check configured for login flow](/docs/synthetics/synthetic-monitoring/using-monitors/store-secure-credentials-scripted-browsers-api-tests/)
-    - Monitors should be configured to [test from all regions applicable to your users](/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors/#setting-location)
-    - Monitors should be configured for each domain and each login flow
+    * [Ping monitors configured for anonymous users ](/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors/)
+    * [Scripted synthetics check configured for login flow](/docs/synthetics/synthetic-monitoring/using-monitors/store-secure-credentials-scripted-browsers-api-tests/)
+    * Monitors should be configured to [test from all regions applicable to your users](/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors/#setting-location)
+    * Monitors should be configured for each domain and each login flow
 * Data retention for browser events is at least 2x an average sprint.
 
 ## Establish current state [#current-state]
@@ -193,24 +194,104 @@ Typical segmentation involves breaking down user experience into the following c
 <table>
   <thead>
     <tr>
-      <th style={{ width: "150px" }}>
-        xx
+      <th style={{ width: "200px" }}>
+        Segment
       </th>
 
       <th>
-        xx
+        Guidance
       </th>
     </tr>
   </thead>
 
   <tbody>
     <tr>
       <td>
-        xx
+        Region/Location
+      </td>
+
+      <td>
+        **Basic:** Group by country. Browser events automatically contain the country code of requests, so there is nothing you need to do to break it out further.
+
+        **Advanced:** Make regional grouping match regional SLO groups by creating your own region attribute using [custom attributes](/docs/telemetry-data-platform/custom-data/custom-events/report-browser-monitoring-custom-events-attributes/) in Browser.
+
+        Facet by `countryCode`.
+
+        Related attributes:
+
+        * `regionCode`
+        * `city`
+        * `asnLatitude`
+        * `asnLongitude`
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Device
+      </td>
+
+      <td>
+        Break out performance and engagement device type so you can understand:
+
+        * Typical breakdown of desktop vs mobile browser users
+        * Experience of desktop vs mobile browser users
+
+        Facet by `deviceType`.
+
+        Related attributes:
+
+        * `userAgentName`
+        * `userAgentOS`
+        * `userAgentVersion`
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Product/Line of Business
+      </td>
+
+      <td>
+        In this scenario, a product is a separate line of business or service provided by your organization. Some examples of industries and respective products:
+
+        * An insurance company that sells both car and house insurance
+        * A media company that has multiple streaming services or channels
+        * A travel company that provides car rental as well as hotel bookings
+
+        **Basic:** Break out performance by product by:
+
+        * Faceting on `pageUrl`: Use this approach when multiple products are grouped into one browser app in New Relic.
+        * Faceting by `appName`: Use this approach when each product is instrumented as a separate web app.
+        * Grouping by `appName` and then facet: Use this approach when there are multiple apps in browser supporting one product.
+
+        **Advanced:** Add product offering as a custom attribute to browser pages using [custom attributes](/docs/telemetry-data-platform/custom-data/custom-events/report-browser-monitoring-custom-events-attributes/).
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Environment
+      </td>
+
+      <td>
+        During instrumentation or afterwards, follow a naming convention that specifies the environment in Browser. Well named browser apps specify product and/or function as well as environment. Examples:
+
+        * `account-management.prod`
+        * `hotels-book.prod`
+        * `car-insurance.uat`
+
+        Using app naming conventions to specify the environment supports filtering data in both the UI and in dashboards. For more information, see the documentation for [how to rename Browser apps](/docs/browser/new-relic-browser/configuration/rename-browser-apps/).
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Team
       </td>
 
       <td>
-        xx
+        In some organizations, a single team supports multiple products, while in others, a product is big enough to be supported by multiple teams.   Report on team performance against customer experience or engagement by either adding the team name to the Browser app name (for example, `account-management.prod.unicorn-squad`) or by using [custom attributes](/docs/telemetry-data-platform/custom-data/custom-events/report-browser-monitoring-custom-events-attributes/).
       </td>
     </tr>