Merge pull request magento-commerce/devdocs/pull#2612 from magento-devdocs/em_prex-eventsdk

Cleaning up PREX events topic

Author: erikmarr

src/_data/toc/product-recommendations.yml

@@ -12,7 +12,7 @@ pages:
   url: /recommendations/install-configure.html
   versionless: true
 
-- label: Recommendation Events
+- label: Data Collection for Recommendations
   url: /recommendations/events.html
   versionless: true
 

src/recommendations/events.md

@@ -1,25 +1,29 @@
 ---
 group: product-recommendations
-title: Recommendation Events
+title: Data Collection for Recommendations
 ee_only: True
 ---
 
-When you deploy the `magento/product-recommendations` module, the module tracks the following user events. These events enable behavioral data collection.
+When you install and configure SaaS-based Adobe Commerce features such as [Product Recommendations]({{ page.baseurl }}/recommendations/install-configure.html) or [Live Search]({{ page.baseurl }}/live-search/install.html), the modules deploy behavioral data collection to your storefront. This mechanism collects anonymized behavioral data from your shoppers and powers product recommendations. For example, the `view` event is used to compute the `Viewed this, viewed that` recommendation type, and the `place-order` event is used to compute the `Bought this, bought that` recommendation type.
 
-If shoppers use ad blockers or enable privacy settings that prevent the `magento/product-recommendations` module from capturing events, the metrics reflected in the [Product Recommendations dashboard](https://docs.magento.com/user-guide/marketing/product-recommendations.html#dashboard) will not be accurate. Most likely, the engagement and revenue numbers will be underrepresented.
+The following events are not specific to Product Recommendations, but are required to return results:
 
-{:.bs-callout-info}
-If [Cookie Restriction Mode](https://docs.magento.com/user-guide/stores/compliance-cookie-restriction-mode.html) is enabled, Magento does not collect behavioral data until the shopper consents. If Cookie Restriction Mode is disabled, Magento collects behavioral data by default.
+-  `view`
+-  `add-to-cart`
+-  `place-order`
+
+The [Storefront Events Collector]({{ site.baseurl }}/shared-services/storefront-event-collector.html#quick-start) lists all the events deployed to your storefront. From that list, however, there is a subset of events specific to Product Recommendations. These events collect data when shoppers interact with recommendation units on the storefront and power the metrics used to help you analyze how well your recommendations are performing.
 
-Event | Category | Description
+Event | Description | [Used for metrics?](https://docs.magento.com/user-guide/marketing/recommendation-metrics.html)
 --- | --- | ---
-`add-to-cart` | product | A product is added to the cart
-`impression-render` | recommendation-unit | The recommendation unit is rendered on the page.
-`instant-purchase` | checkout |  The customer completes an instant purchase
-`place-order` | checkout | The customer's order is submitted
-`rec-add-to-cart-click` | recommendation-unit | The customer clicks the **Add to cart** button for an item in the recommendation unit.
-`rec-click` | recommendation-unit | The customer clicks a product in the recommendation unit.
-`remove-discount-action` | shopping-cart | A discount code is removed from a cart
-`remove-from-cart` | product | A product is removed from a cart
-`view` | product | The customer views a product details page (PDP)
-`view` | recommendation-unit | The recommendation unit becomes viewable on the page, such as by scrolling into view
+`impression-render` | The recommendation unit is rendered on the page. | Yes
+`rec-add-to-cart-click` | The customer clicks the **Add to cart** button for an item in the recommendation unit. | Yes, when an **Add to cart** button is present in the recommendations template.
+`rec-click` | The customer clicks a product in the recommendation unit. | Yes
+`view` | The recommendation unit becomes viewable on the page, such as by scrolling into view. | Yes
+
+If you are using the default Adobe Commerce storefront or [PWA](https://magento.github.io/pwa-studio/product-recs/), handling these events is done for you. If you are writing your own custom storefront, learn how you can [integrate Product Recommendations]({{ site.baseurl }}/recommendations/headless.html) into your storefront.
+
+Many shoppers use ad blockers or enable privacy settings. These configurations prevent the `magento/product-recommendations` module from capturing events, which might cause the metrics in the [Product Recommendations dashboard](https://docs.magento.com/user-guide/marketing/product-recommendations.html#dashboard) to underreport engagement and revenue numbers.
+
+{:.bs-callout-info}
+If [Cookie Restriction Mode](https://docs.magento.com/user-guide/stores/compliance-cookie-restriction-mode.html) is enabled, Adobe Commerce does not collect behavioral data until the shopper consents to using cookies. If Cookie Restriction Mode is disabled, Adobe Commerce collects behavioral data by default.

src/recommendations/headless.md

@@ -14,15 +14,13 @@ To integrate Product Recommendations in a headless storefront you must:
 
 1. Fetch product recommendation results and render those results on the page.
 
-You can perform both of these actions using the available SDKs as described below.
-
-The following workflow describes how to integrate Product Recommendation in a headless storefront.
+You can perform both of these actions using the available SDKs as described in the following workflow.
 
 1. [Install the Product Recommendations]({{ page.baseurl }}/recommendations/install-configure.html) module.
 
 1. Install and use the [Storefront Events SDK]({{ page.baseurl }}/shared-services/storefront-events-sdk.html) to fire the [behavioral events]({{ page.baseurl }}/recommendations/events.html).
 
-    The minimum required events to enable Product Recommendations are:
+    The minimum required events to return Product Recommendations results:
 
     Event | Category
     --- | ---

src/recommendations/images/event-metric.png

@@ -6,13 +6,7 @@ ee_only: True
 
 Before you deploy recommendations to your production environment, you should test on a non-production environment to ensure everything is working as expected.
 
-Product Recommendations return products based on shopper [behavioral data]({{ page.baseurl }}/recommendations/product-recs.html#types-of-data) collected from your storefront. In a non-production environment, however, it is likely you will not have any behavioral data from shoppers. The only recommendation type you can test without behavioral data is **More like this**. This recommendation type does not require any input data, as it uses a direct content similarity match.
-
-The following recommendation types require behavioral data:
-
--  **Most Viewed**
--  **Viewed this, viewed that**
--  **Bought this, bought that**
+Product Recommendations return products based on shopper [behavioral data]({{ page.baseurl }}/recommendations/product-recs.html#types-of-data) collected from your storefront. In a non-production environment, however, it is likely you will not have any behavioral data from shoppers. The only recommendation types you can test without behavioral data are **More like this** and **Visual Similarity**. These recommendation types do not require any input data, as they use a direct content similarity match.
 
 How can you test your recommendations in a non-production environment using behavioral data? There are a couple of options.
 
@@ -41,6 +35,6 @@ See the [user guide](https://docs.magento.com/user-guide/marketing/recommendatio
 
 ### Caveats
 
--  The non-production SaaS Data Space behavioral and catalog data identifies an isolated environment in which the resulting product recommendations will be based entirely on the behavioral data generated on the associated storefront.
+-  The behavioral and catalog data associated with your non-production SaaS Data Space identifies an isolated environment. This results in Product Recommendations based entirely on the behavioral data generated on the associated storefront.
 
--  Because you will not have large amounts of behavioral data, input data for computing product associations is sparse. However, that data is still sent to Sensei to compute the machine learning models and provide recommendations based on data you generated within this environment.
+-  Because you will not have large amounts of behavioral data, input data for computing product associations is sparse. However, that data is still sent to Adobe Sensei to compute the machine learning models and provide recommendations based on data you generated within this environment.

src/recommendations/test.md

@@ -55,9 +55,7 @@ A value of `Data validity : NOT FOUND` in the debugger indicates an internal sch
 
 ## Verify events are firing correctly
 
-To verify that the events used for metrics are firing correctly, look for the `impression-render`, `view`, and `rec-click` events in the Snowplow Analytics Debugger. See the [full list of events](https://devdocs.magento.com/recommendations/events.html).
-
-![Events for metrics]({{ page.baseurl }}/recommendations/images/event-metric.png)
+To verify that the events used for metrics are firing correctly, look for the `impression-render`, `view`, and `rec-click` events in the Snowplow Analytics Debugger. See the [full list](https://devdocs.magento.com/recommendations/events.html) of events specific to Product Recommendations.
 
 {:.bs-callout-info}
 If [Cookie Restriction Mode](https://docs.magento.com/m2/ce/user_guide/stores/compliance-cookie-restriction-mode.html) is enabled, Magento does not collect behavioral data until the shopper consents. If Cookie Restriction Mode is disabled, Magento collects behavioral data by default.