Detailed analytics by object
This page complements the Analytics Introduction by detailing the metrics available in the object-level views: Stories, Widgets, Interactions, and Products. These views make it possible to closely analyze the performance of a specific element, whereas global metrics provide an aggregated view.
The session filtering rules (engaged sessions + exposed to JOIN assets) also apply here. See 1. Definition of the sessions that are taken into account.
1. Analytics by Story
The Analytics by Story view lets you compare the individual performance of each story, both in terms of viewing and engagement with the interactions it contains.
Name | Description |
Widgets | List of widgets in which the story is displayed. The same story can appear in several widgets; the |
Views | Total number of story views over the period |
Viewers | Number of unique visitors who viewed the story |
Completion rate | Average percentage of viewing progress (video progress or tap to next) |
Avg. watch time | Average time spent (in seconds) on the story. Can exceed the actual duration in case of pause or rewind |
Nb. engagements | Total number of clicks on interactions present in the story (CTA, forms, polls, quizzes, replies, etc.) |
Engagement rate | Engagement rate: Nb. engagements / Views. |
ℹ️ Note: a story with no interactions will show 0 engagement and N/A for engagement rate. This is not underperformance—just the absence of clickable elements.
2. Analytics by Interactions
The Analytics by Interactions view groups the performance of clickable elements within stories. It is segmented by interaction type via a tab system:
CTA: call-to-action buttons that redirect to a URL
Forms: data collection forms
Replies: free-text reply areas
Polls: multiple-choice polls
Quizzes: quizzes with multiple answers
The reading logic is similar from one tab to another: each row corresponds to an interaction occurrence within a given story, along with the associated exposure volume and engagement volume. For some interaction types, metrics related to the questions asked and the answers are displayed.
ℹ️ Note: the same story can contain multiple interactions of the same type (e.g., two CTAs to two different URLs). Each will appear on its own row, which explains why a story can appear multiple times within the same tab.
3. Analytics by Widget
The Analytics by Widget view lets you analyze how each widget performs on the site: how many times it is loaded, its actual visibility, and its ability to generate clicks to stories.
Name | Description |
Nb Stories | Number of stories contained in the widget over the period |
Widgets loaded | Total number of times the widget was loaded |
Views | Number of times the widget was actually seen (75% of the widget’s height visible on screen) |
Viewability rate | Viewability rate: Views / Widgets loaded. A widget that is loaded but never scrolled into view does not count as viewed |
Click rate | Click-through rate: Widgets clicks / Widgets loaded. Measures the widget’s ability to trigger the opening of a story |
ℹ️ Widgets loaded vs Views: a widget placed low on a PDP can have a high volume of Widgets loaded but a low Viewability rate if few visitors scroll down to it. This is a good signal to consider repositioning.
4. Revenue attribution
The Revenue section lets you analyze JOIN’s contribution to revenue, with three levels of granularity via the Products, Stories, and Widgets tabs. The attribution logic (Post-Click, Post-View, Indirect) described in the Introduction applies in the same way, but is read differently depending on the object analyzed.
❓How to interpret attribution at the object level:
When a visitor purchases after being exposed to JOIN, the order is attached to all objects involved in their journey, depending on the applicable model:
Post-Click: attached to the story and widget where the click occurred, as well as the purchased product
Post-View: attached to the story and widget where the product was viewed, as well as the product
Indirect: attached to any story viewed and its widget, as well as the purchased cart (all products combined)
The same euro of revenue can therefore appear simultaneously in the three tabs. There is no double counting within a tab, but totals do not add up across tabs.
4.1 Revenue by Product
View centered on the products in your catalog.
Name | Description |
Views | Number of times the product was viewed in a story shopping interaction |
Engagements | Number of clicks on the product in those shopping interactions |
Engagement rate |
|
Post-Click Revenue | Revenue generated after a click on the story shopping interaction (7-day window) |
Post-View Revenue | Revenue generated after a view of the story shopping interaction, without a direct click (2-day window) |
Indirect Revenue | Product revenue when it was purchased following a story view only (1-day window) |
Revenue | Sum of the three attribution columns |
4.2 Revenue by Story
View centered on stories: which story contributes the most to revenue, and how.
Name | Description |
Views | Total number of story views |
Conversion rate | Conversion rate of sessions that viewed this story (conversion in the same session only) |
Product engagements | Number of clicks on products featured in the story |
Product engagement rate |
|
Post-Click Revenue | Revenue attributed to the story after purchase of a product clicked in the story (7-day window) |
Post-View Revenue | Revenue attributed to the story after purchase of a product viewed in the story (2-day window) |
Indirect Revenue | Revenue attributed to the story after purchase of a product with no click or view in the story (1-day window) |
Revenue | Total revenue attributed to the story |
ℹ️ Conversion rate vs Revenue: these two metrics are not correlated. Conversion rate counts only purchases that happen in the same session, while Revenue applies the attribution windows (up to 7 days). A story can therefore show a low conversion rate but high revenue, or the reverse.
4.3 Revenue by Widget
View centered on widgets: which placement generates the most value, independent of the stories it hosts.
Name | Description |
Widgets views | Number of widget views (75% visible on screen) |
Conversion rate | Conversion rate of sessions that viewed this widget |
Product engagements | Product clicks in stories accessible via this widget |
Product engagement rate | Product engagements / Product views within the widget |
Post-Click Revenue | Revenue attributed to the widget after purchase of a product clicked in a story from this widget (7-day window) |
Post-View Revenue | Revenue attributed to the widget after purchase of a product viewed in a story from this widget (2-day window) |
Indirect Revenue | Revenue attributed to the widget after purchase of a product with no click or view in a story from this widget (1-day window) |
Revenue | Total revenue attributed to the widget |