Activities
Track user actions with activities to analyze behavior, personalize experiences, measure performance, and improve engagement. Includes details like action, target, user, source ID, and metadata.
Last updated
Front End Tracking
Track user actions with activities to analyze behavior, personalize experiences, measure performance, and improve engagement. Includes details like action, target, user, source ID, and metadata.
Last updated
An activity is a specific action (or event) performed by a user on your platform. By tracking activities, our system can extract meaningful data that provides insights into user behavior, that can be analyzed to enhance user experience, optimize content, and drive conversions.
Whenever a user performs an action on your platform, you should send an activity containg all relevant information about that action. Our system processes and aggregates the resulting data, delivering the valuable insights you need to make informed decisions.
Activities form the core data that powers analytics and personalization. Every user interaction, from simple page views to more complex actions like purchases, can be captured as an activity. By understanding these activities, businesses can:
Analyze user behavior: Track how users navigate your platform: what they view, click, or purchase, and which features or content they interact with.
Personalize user experience: Consider activity data when making decisions regarding conten customization, recommendations, and promotions.
Measure performance: Identify actions that drive conversions, identify bottlenecks, and optimize the customer journey.
Improve engagement: Identify actions that foster higher engagement, such as frequent product views or successful checkout flows.
Each activity is made up of the following parts:
: The event or task performed by the user. This can include a wide range of actions such as clicking a link, adding a product to the cart, viewing a page, or completing a purchase.
: The object or entity on which the action is performed. Examples of targets include products, categories, or specific pages on a platform.
: The entity performing the action. This could be an anonymous visitor or an identified user based on user authentication (e.g. a logged-in customer).
: When a page is powered by FHR or XO, the data for that page will be associated with an ID, i.e. response ID. This value should be used as the source ID for any activity that takes place within the context of that data.
Activities on a page not powered by FHR or XO should not include a source ID.
Capture activity: When a user performs an action, an activity is captured.
Send activity data: The raw activity data is sent to your tracking system or event pipeline.
Process activity: Once the activity data is received, it is processed by the system. This may involve cleaning and enriching the data, as well as integrating it into your analytics tools or personalization engine.
Analyze and act: The processed data is then used to gain insights, segment users, personalize recommendations, and improve platform functionality.
: Additional metadata associated with the activity that provides further context for the action, such as locale (language and region), device type (mobile, desktop), quantity, or price.