Validate all necessary events

* isactivedatahead tag is needed in the head tag in the ISML code templates.

1. viewProduct: This event should fire once on every product detail page. It enables recently viewed recommenders and recommenders utilizing the real time personalization strategy
2. viewReco: This event should fire on every page where recommendations have been placed
3. clickReco: This event should fire every time a recommendation is clicked on
4. addToCart: This event should fire every time a product is added to the cart
5. finishCheckout: This event should fire every time the checkout process is complete (order has been placed). For customers redirected to a 3rd party payment page, Einstein also tracks this event on the server side so this may not show in the Commerce Cloud Recommendation Validator Chrome extension.
6. viewCategory: This event should fire every time a shopper views a category grid page
7. viewSearch: This event should fire every time a shopper views the search results page with results
8. clickCategory: This event should fire every time a shopper clicks through from a category grid page to a product detail page
9. clickSearch: This event should fire every time a shopper clicks through from a search results page to a product detail page

Ensure anchors are properly populated to the context-object attribute**

1. PDP - Product id should display in DWPI Integration validator next to 'anchors' on the Recommendations tab.
   Example PDP slot tag:
   <isslot id="pdp-you-may-like" description="PDP You May Like" context="global" context-object="${pdict.Product}"/>
   
   
2. Category Page - Category id should display in DWPI Integration validator next to 'anchors' on the Recommendations tab.
   Example Category slot tag:
   <isslot id="recomm-category-anchor" description="Product page slot" context="global" context-object="${pdict.ProductSearchResult.category}"/>
   
    

Common data errors and how to fix/diagnose

1. Availability allocation defined as '0' on master product in Business Manager.
   1. Remove inventory definitions if possible, the result would be an allocation of 'N/A'
   2. If master id allocation is required, define some valid amount of allocation i.e. '100'
2. Einstein dashboard is not reporting data.
   1. This mainly depends on two events firing properly: viewReco and clickReco

Common storefront errors and how to fix/diagnose

1. viewProduct is not firing.
   How to fix: Make sure you are using <isobject object="${product}" view="detail"> to you  product detail page templates
2. viewReco is not firing.
   How to fix: Make sure you are using <isobject object="${product}" view="recommendation"> in your Einstein content slots rendering templates (This should NOT be applied to non Einstein content slot rendering templates).
3. clickReco is not firing.
   How to fix:
   1. Use integration validator to check for clickReco. If missing, go check the page with the recs that you clicked for viewReco.
   2. If viewReco is there, then make sure the product id matches the product id in the viewProduct activity on the page after you click. If this is not the case, that is the problem and you'll need to engage Commerce Cloud Support for further review.
   3. If there is no viewReco, then that is the problem. You'll need to reach out to your developer, solution support OR technical design authority (TDA) to ensure the isobject tag is configured correctly.
4. Incorrect price displaying because of master product price definitions.
   How to fix: Update the template API to call on variation price definitions instead of master id.
5. viewCategory or viewSearch not firing.
   How to fix: The tracking of viewSearch / viewCategory happens automatically if your code follows the SiteGenesis examples to place an 'isobject' tag when rendering each product tile.