What this module is for

Use Analytics / Opt-In Clicks to inspect how often CRM opt-in links or feature prompts were viewed and clicked. The page is mainly for support, product operations, or low-frequency investigations when someone needs to confirm whether a feature was shown, whether users clicked it, and which feature names generated traffic.

Real operator surface

• Analytics / Opt-In Clicks / List is the only verified Backoffice surface for this module.

The current FE route is one combined page:

• top summary cards
• feature performance block
• daily trend block
• filter bar
• paginated raw record table

There is no separate verified Backoffice route for create, edit, or detail pages in the current FE. The admin backend exposes POST /api/admin/optin-clicks, but the current CRM page does not expose an operator create form for it.

What operators need to know first

• The summary cards are not returned as one ready-made totals payload. FE calculates them from the backend stats rows.
• Only the date range is shared between the summary section and the table. Feature, Status, and User ID change the table request, but they do not change the top stats block.
• The Feature dropdown counts are generated from backend aggregation that respects only the date filter. Those counts are not narrowed by User ID or Status.
• The page is effectively read-mostly. The only destructive operator action on the current route is deleting selected raw records.

Backend ownership summary

The operator surface is owned by gs-admin-backend:

• GET /api/admin/optin-clicks
• GET /api/admin/optin-clicks/stats
• DELETE /api/admin/optin-clicks
• GET /api/admin/optin-clicks/export-csv

The record-production side is also traced to gs-casino-backend user routes, because public opt-in views and clicks are recorded there:

• GET /api/user/optin
• GET /api/user/optin/view
• GET /api/user/optin/click

Common caveats

• Unique Users on the top cards is currently a frontend sum of per-feature unique-user counts. That means it can overcount users who interacted with more than one feature in the selected date window.
• Click Rate on the top cards is also frontend-derived from summed views and clicks.
• The table shows raw records, while the top section shows aggregated statistics. They answer different questions even though they are on the same route.