We listened! The profile teams collected your feedback and adapted Profile Tag accordingly, resulting in the best Profile Tag ever: Profile Tag 2.0.0. This release includes these new features and improvements:
- Data collections replace selectors and interactions
- Template data collections replace predefined events
- Improved, simplified UI
- Profile Tag can collect data from triggered events
- Profile Tag applies all matching page definitions
- Improved debug mode
Data collections replace selectors and interactions
Profile Tag no longer uses the terms "selector" and "interaction" for events that it raises on page load or on user interaction, respectively. It now uses the term "data collection" for both. A data collection defines which data Profile Tag captures and when it captures that data. Profile Tag uses the data collections to create the desired events. "Interaction" is no longer used in the context of Profile Tag. "Selectors" define the information that Profile Tag captures from a page, and constitute data collections.
For more details about data collections, see Configure Data Collections.
Template data collections replace predefined events
The set of predefined events is no longer implicitly defined by a set of selectors using certain selector keys. Profile Tag now provides a set of templates for data collections, which create the most common events.
If you wanted Profile Tag to raise a ProductDetailPageView event, you had to manually add and configure the selectors productName, productSku, productCategory, and productPrice. Now you simply select the data collection PRODUCT DETAILS PAGE VIEW from a drop down list. The UI creates the required keys. You only have to specify where their data shall come from.
For more details about templates for data collections, see Creating a new Data Collection.
Improved, simplified UI
All these improvements are reflected in a new, simplified and more structured UI. Data collections for events on page load and events on user interactions share a similar configuration pop-up. The pop-up fits on a single screen, so you do not have to scroll anymore. Furthermore, the names of the input boxes describe the desired attributes much better, and tooltips are more verbose.
For more details about the new Profile Tag configuration UI, see the Profile Tag documentation.
Profile Tag can collect data from triggered events
Profile Tag has a new selector type called
Event. This selector type enables Profile Tag to gather data from an event and add that data to the data collection that was triggered by that event.
You configured Profile Tag to raise a click event, if a user clicks on a certain button. With this new feature you can not only capture that a user clicked that button, but also the amount of pressure applied to a touch or tabdevice when generating the event.
Profile Tag applies all matching page definitions
Instead of applying only the first matching page definition, Profile Tag now iterates on all page definitions and applies all matches.
Improved debug mode
Debug mode in Profile Tag enables the tracing of user activities across your web presence. Enable the debug mode by adding the debug flag to the URL of your website. You can also now switch debug mode on and off by invoking
Y_TRACKiNG.disableDebugMode() in the console of your browser.
For more details about Profile Tag debug mode and tracing, see Enable tracing in your storefront using Profile Tag.
The major, minor, and patch versions are also updated. For more information, see Decide which Profile Tag link to use
If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.
Use our private help channel. Receive updates over email and contact our specialists directly.
If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.