Website Custom Reporting: Metrics, Dimensions, and Use Cases
Updated
The Custom Reporting fields for Website Surveys help you analyze and measure Intercept Performance across your survey experiences. This documentation provides an overview of the key metrics and dimensions available for reporting, enabling you to track how visitors interact with survey intercepts and evaluate overall survey effectiveness.
Using these reporting fields, you can monitor the complete intercept journey from triggered to engaged, abandoned, and completed, compare performance across different distributions and creatives, and uncover trends based on time and audience context. For deeper analysis, use rate-based metrics to compare performance across audiences or cohorts, and count-based metrics to track overall response volumes and engagement levels.
Business Use Cases
Intercept funnel monitoring: Monitor triggered, engaged, abandoned, and completed actions to identify points where users drop off in the funnel.
Creative effectiveness analysis: Analyze the levels of engagement and completion among different creative types and their respective names.
Distribution benchmarking: Examine the distributions based on channel or name to identify the leading performers.
Time-based insights: Examine performance based on the time of day, day of the week, and month of the year.
User-level segmentation (where available): Identify the users or profiles that interact with intercepts.
Metrics and Dimensions
All rate metrics are percentages and typically use Intercept Triggered Count as the denominator.
Metrics (Intercept Performance)
Metric | Description | Possible values |
Intercept Triggered Count | Number of times an intercept was shown/triggered for recipients. | Integer ≥ 0 |
Intercept Engagement Count | Number of times users engaged with the intercept (opened/accepted prompt to proceed). | Integer ≥ 0 |
Intercept Engagement Rate | Engagement % out of total triggered. Formula: (Engagement Count / Triggered Count) × 100 | 0–100% |
Intercept Abandoned Count | Number of times users closed/dismissed the intercept (e.g., close icon / secondary action such as “No”). | Integer ≥ 0 |
Intercept Abandonment Rate | Abandonment % out of total triggered. Formula: (Abandoned Count / Triggered Count) × 100 | 0–100% |
Intercept Completed Count | Number of times the intercept was completed (completion event as defined in intercept flow). | Integer ≥ 0 |
Intercept Completed Rate | Completion % out of total triggered. Formula: (Completed Count / Triggered Count) × 100 | 0–100% |
Dimensions
Dimension | Description | Possible values (examples) |
Distribution Channel | Channel used to deliver/trigger the distribution. | Enumerated (e.g., In‑App, Website, …) |
Distribution Name | Name of the distribution in CFM. | Free-text (user-defined) |
Intercept Creative Name | Creative name for the intercept shown. | Free-text (user-defined) |
Intercept Creative Type | Creative format shown to the user. | Web: Popup, Positioned Popup & Feedback Button, Embedded In-App: Popup, Embedded & Rating Popover |
Intercept Page URL | The URL page on which the intercept was triggered | URL |
Intercept Engaged User | User/profile that engaged with the intercept. | User/profile identifier |
Intercept Activity Time | Timestamp when intercept is shown (intercept activity event time). | DateTime |
Response Time | Timestamp when the survey response is submitted. | DateTime |
Survey Open Time | Timestamp when the survey was opened (if tracked separately). | DateTime |
IP Address | IP captured during interaction (if available). | IPv4/IPv6 string |
Note:
Counts vs Rates
Counts represent absolute volumes for the selected filters and time range.
Rates represent normalised performance and are better for comparisons across cohorts.
Denominator behaviour
Callout (Warning): When the Intercept Triggered Count is equal to 0, the rate metrics might appear as 0, empty, or N/A based on the reporting standards.
Applicability notes
Intercept Page URL is most relevant for Website distributions (if enabled/exposed).
Intercept Engaged User is intended for user-level segmentation and may be subject to privacy/access controls.