View
Views are one of the most basic actions your user can do. Views should be sent whenever your customer navigates to a page, whether that's from the navigation menu, a search result, or a product detail page. View actions are used within our services in order to track impressions, and product views.
Impressions vs Views.
When your customer navigates through your website or performs a search, results are displayed and our system tracks this as an impression. If you customer then decides to click on a product, that translates into a view, so then we can ultimately calculate the view conversion rate.
Views on Navigation Results
If your website's navigation is powered by Attraqt's services, you should send a navigation view event whenever your users navigate to a page and a query is made (in case of an infinite scroll implementation you can send multiple events while on the same page). Check the structure of the event below.
The properties needed for sending a view event on a navigation result are as follows:
action
- you need to specify the action as viewtarget.page
- you need to specify the path of your page in your web shopsourceId
- if you are implementing an FHR integration, you need to specifysourceId
which is equal to theresponseId
you get from the FAS response.locale
- the locale selected by the user.
If you have any extra details you wish to send you can include them in the metadata
_**_object.
Views on Search Results
If your website's search is powered by Attraqt's services, you should send a navigation view event whenever your users navigate to a page. Check the structure of the event below.
The properties needed for sending a view event on a search result are as follows:
action
- you need to specify the action as viewtarget.page
- you need to specify the path of your page in your web shoptarget.search-terms
- you need to specify the search terms. If you are implementing an FHR integration they would be available in the FHR query response.sourceId
- if you are implementing an FHR integration, you need to specifysourceId
which is equal to theresponseId
you get from the FHR query response.locale
- the locale selected by the user.
If you have any extra details you wish to send you can include them in the metadata
_**_object.
Views on products - PDPs powered by FHR
If your Product Detail Pages(PDPs) are powered by Attraqt's services, you should send a product view event when your users land on your product details page.
The properties needed for sending a view event on a product detail page are as follows:
action
- you need to specify the action as viewtarget.product
- you need to specify the product id of the product on the page. For an FHR integration, this corresponds to thesecondId
**provided in the FHR query** response.sourceId
- if you are implementing an FHR integration you need to specify asourceId
which is equal to theresponseId
you get from the FHR query response. If you are implementing an XO integration, you need to specify asourceId
which corresponds to therecommendationId
.locale
- the locale selected by the user.
If you have any extra details you wish to send you can include them in the metadata
_**_object.
Views on products - PDPs NOT powered by FHR
If your Product Detail Pages(PDPs) are not powered by FHR, you should still send a product view event when your users land on a product detail page.
The properties needed for sending a view event on a product detail page when not powered by FHR are as follows:
action
- you need to specify the action as viewtarget.product
- you need to specify the product id of the product on the page. For an FHR integration, this corresponds to thesecondId
**provided in the FHR query** response.locale
- the locale selected by the user.
If you have any extra details you wish to send you can include them in the metadata
_**_object.
Last updated
Was this helpful?