Configure views for tracking

purple experience in the purple experience builder, any view of the views json will trigger two tracking events 1\) the view event storefront \<viewname> 2\) the action event of opening the view storefront view \<viewname> we fire two events to ensure that any tracking provider will be able to get all the necessary data to make one or both events appear on your 3rd party tracking provider, follow the documentation in tracking configuration docid\ sxkxo oept7crfzzob9nw for your desired provider if you do not map this accordingly, the data will not appear mostly, you'll want to know more than just the view name so, you need to add view tracking parameters to achieve that, navigate to your views json and add them tracking parameters are defined as keys and values, we are not limiting your chose of keys in any way per convention, all tracking parameters are capitalised and blanks are substituted with underscores we'll convert those, but we recommend setting them up like that in the first place if you require computed data, we recommend that you compute any required data within the url resolver to ensure early availability please note that some data may not be available from the ssr, i e it is not possible to know if a user has purchased content from there any value in the viewtrackingparams must be of type string when you have configured everything according to your liking, it's time to verify proper execution please refer to logging raw events docid\ crx l92env q 8h0bijew to check the event emitted from purple experience as soon as this works as expected, you must map the events to your desired 3rd part analytics tool see tracking configuration docid\ sxkxo oept7crfzzob9nw and tracking services docid 3ofsgplkna2zz3rzik3fg for details