WebLink Analytics helps you understand how learners interact with your training storefront. By monitoring visitor behavior, registrations, and conversion activity, you can evaluate how effectively your WebLink-powered catalog supports learner discovery and booking.
Analytics does not change how WebLink works. Instead, it provides visibility into how users navigate the storefront and complete registration journeys.
If you have not yet implemented WebLink on your website, start with WebLink Overview and Installation .
Table of contents
- Why storefront analytics matter
- How WebLink analytics works
- Where analytics data comes from
- Supported analytics event data
- Hosted WebLink and Google Tag Manager
- WebLink Widgets tracking
- Typical storefront metrics
- Analyzing the learner journey
- Improving storefront performance
- Testing analytics tracking
- Common issues
- Best practices
- Related articles
Why storefront analytics matter
Understanding how learners interact with your storefront can help you improve the training experience and increase successful registrations.
- which courses attract the most attention
- how learners navigate the catalog
- where learners abandon the booking journey
- which training programs generate the most registrations
How WebLink analytics works
WebLink Analytics captures event data throughout the learner journey and makes it available to your analytics tools.
This includes interactions such as browsing, course views, and checkout activity, allowing you to track the full journey from discovery to booking.
WebLink supports passing this data to analytics platforms using standard web tracking approaches.
Where analytics data comes from
WebLink storefront pages behave like normal website pages, which means they can be monitored using standard analytics tools.
- tracking storefront page views
- monitoring course page engagement
- tracking registration and checkout events
- analyzing conversion between browsing and booking
Supported analytics event data
WebLink provides structured event data that can be captured by analytics platforms or tag managers.
For a detailed breakdown of supported events, refer to: WebLink Analytics Event Documentation .
This event data enables deeper analysis beyond simple page views, including tracking specific actions within the booking journey. [oai_citation:0‡index.html](sediment://file_0000000043d871f8a4e6b4df773f0623)
Hosted WebLink and Google Tag Manager
If you are using Hosted WebLink or Hosted Checkout, analytics tracking is typically configured using Google Tag Manager (GTM).
In this setup, WebLink sends event data to GTM, which can then forward it to your analytics tools. [oai_citation:1‡index.html](sediment://file_0000000043d871f8a4e6b4df773f0623)
Set up Google Tag Manager
- Go to Settings → Portals
- Select your WebLink Portal
- Enter your GTM Container ID
- Save the configuration
Once configured, you can create tags in GTM to capture and process WebLink event data. [oai_citation:2‡index.html](sediment://file_0000000043d871f8a4e6b4df773f0623)
WebLink Widgets tracking
If you are using WebLink Widgets, analytics data is passed to the data layer in your website.
You can capture this data using your preferred analytics platform or tag manager (such as GTM) and configure custom tracking as needed. [oai_citation:3‡index.html](sediment://file_0000000043d871f8a4e6b4df773f0623)
Typical storefront metrics
- catalog page visits
- course detail views
- checkout starts
- completed registrations
Analyzing the learner journey
- high views but low registrations
- checkout abandonment
- uneven traffic across catalog pages
Improving storefront performance
- simplify catalog structure
- improve course descriptions
- highlight popular courses
- reduce checkout friction
Testing analytics tracking
- Open your storefront page
- Browse courses and open a detail page
- Start a test registration
- Confirm events appear in your analytics tool
Common issues
No analytics data appears
- tracking script not installed
- pages not included in tracking scope
- analytics tool not receiving data
Registration activity not tracked
- checkout not tracked
- event tracking not configured
- user leaves tracked domain during checkout
Best practices
- monitor analytics regularly
- validate tracking after changes
- use GTM or equivalent for flexibility
- combine analytics with Administrate reporting