IntelliSuggest Tracking is required to be implemented so that Searchsprings various reporting tools can collect data appropriately and help your merchandising team make informed decisions on merchandising strategy. IntelliSuggest tracking also enables other features your team can leverage for merchandising purposes, learn more here.
IntelliSuggest tracking is also required if Personalized Recommendations or Personalized Search is included in your plan. IntelliSuggest tracking allows specific data to be sent to our Personalization engine so that it can personalize recommended products and populate shopper interactions appropriately in the Product Recommendations report.
Reports IntelliSuggest Tracking influences:
IntelliSuggest Requirements
To ensure there are no issues with IntelliSuggest tracking the following must be followed:
- _isuid cookie is set
- IntelliSuggest library integration script does not have a defer or async attribute
<script type="text/javascript" src="//cdn.searchspring.net/intellisuggest/is.min.js"></script>
Testing/Debugging
When testing each of the following events to ensure data is passed correctly, have your browsers Network panel open and enable preserve log. For each of the following sections we will be checking the resources logged in the Network Log and review specific resources payload to review the data passed.
Product Click (result click) Tracking
It is required that this code is implemented, do not build a request to the track.json endpoint directly as this can result in issues with tracking data.
References to intellisuggestData and intellisuggestSignature will be sourced from the Search API endpoint within the iteration of a result object. To ensure this click functionality works as expected, filter the Network Log by track.json in the Network panel. You should see a resource available for track.json, click on it and then click on payload to review the data passed within the query string parameters.
Query string parameters - both values will be sourced for the iteration of the result that was clicked on:
- d should receive the intellisuggestData value for the clicked result
- s should receive the intellisuggestSignature value for the clicked result
- Search API - see query string parameters intellisuggestData and intellisuggestSignature
Documentation:
Product Page View/Basket/Sale Tracking
Utilize the documentation provided at the end of this section to utilize the appropriate integration code per the platform your store uses.
It is important to ensure references to SKU is aligned with the SKU core field for the indexed product in Searchspring. You can use the Search Preview tool to review what the SKU core field of an indexed product is at any time.
Product Page View
This event should occur the instant the shopper is taken to the product page.
Within the Network panel, filter resources by beacon. Review the payload data. You should be able to find a beacon API call that has an event type of product. Within this event the event.sku value passed should align with the SKU core field of the indexed product in Searchspring.
Basket (add to cart)
This event should occur if the shopper navigates to the cart page or adds a product to the cart. In the case a mini cart is implemented, this event should also be sent if the mini cart is opened by the shopper.
Within the Network panel, filter resources by beacon. Review the payload data. You should be able to find a beacon API call that has an event type of cart. Within this event the event.sku value passed should align with the SKU core field of the indexed product in Searchspring.
Sale (purchase/order confirmation)
This event should occur if the shopper has completed a purchase or has been taken to an order confirmation page.
Within the Network panel, filter resources by beacon. Review the payload data. You should be able to find a beacon API call that has an event type of sale. Within this event the event.sku value passed should align with the SKU core field of the indexed product in Searchspring.
Documentation:
- Shopify
- BigCommerce - Blueprint
- BigCommerce - Stencil
- Magento 1
- Magento 2
- Miva
- CommerceV3
- 3dCart
- Volusion
- Custom
FAQs
Q: Where setShopperId() is referenced in the tracking scripts, what is that value and where is it sourced?
A: setShopperId() will be the unique ID of the logged in shopper from your platform. This value is also stored as the ssShopperId cookie value when a login occurs.
Q: When the ssShopperId cookie is stored, does that value also need to update the _isuid and ssUserId cookies to have the same value?
A: No, ssShopperId is a separate value. The _isuid and ssUserId will not be changed when ssShopperId is set.