What this surface shows
Analytics / Opt-In Clicks / List is one combined analytics page for opt-in interaction records.
The route shows two layers at once:
- aggregated analytics at the top
- raw records in the table below
Use the top section when you need a quick summary of views, clicks, click rate, and the strongest-performing features for the selected date window. Use the table when you need to inspect concrete records by feature, user, IP address, or timestamp.
How to read the page
Top summary cards
The first row shows:
Total ViewsTotal ClicksClick RateUnique Users
These cards are calculated from grouped stats rows by feature. They are useful for quick monitoring, but they are not a separate immutable reporting total with one precomputed totals row.
Feature Performance
This block ranks features by view volume and shows per-feature:
- views
- clicks
- CTR
Only the top 10 features by views are shown in this block.
Daily Trend
This block shows the last 30 daily buckets from the source aggregation, reformatted for compact display.
Raw record table
The table is the row-level inspection surface. It is the place to verify a single record, identify the feature slug, confirm whether the record was only viewed or actually clicked, and export or delete selected rows.
Filters that change the page
The page contains five visible filters:
FeatureStatusUser IDStart DateEnd Date
Important scope difference:
Start DateandEnd Dateaffect both the top analytics section and the raw table.Feature,Status, andUser IDaffect the raw table request only.
Actions operators can use
Refreshreloads the current table query. It does not force-refresh the top stats widget.Export CSVdownloads rows for the current table filter set. It is not limited to selected rows or the current page.Deleteremoves the selected raw records after confirmation.Resetclears the visible filters, resets the table page, and clears selected rows.
Common questions
Why do the top cards stay the same when I change Status or User ID?
Because the stats request only receives startDate and endDate. Those cards do not use the table-only filters.
Why can Unique Users look larger than expected?
Because the top card sums unique_users across feature groups. If one user interacted with multiple features, that user can be counted more than once in the top card.
What is the difference between Viewed and Clicked?
Viewed means the record exists with clicked = 0. Clicked means the stored record has clicked = 1.
Is there a row detail page?
Not in the currently verified CRM surface. Operators use the combined page with embedded table and stats.
Known caveats
- The
Featuredropdown counts come from source aggregation that is narrowed only by date range, not byUser IDorStatus. - The table row selection is purely for bulk deletion on this screen.
- Select-all applies to the currently loaded table rows, not to every matching row across all pages.
- Changing filters does not explicitly clear the current selection in the verified page code; use
Resetor review selected rows before deleting. - No verified CRM create form exists on this module today.