Social Snap's Pro analytics add-on writes one row per share click to wp_socialsnap_analytics: post_id, network (facebook, twitter, pinterest, linkedin), location (which button position fired the click), and created_at. The plugin's own dashboard aggregates this into bar charts and top-N lists, but the raw rows never appear as a table.

SleekView reads wp_socialsnap_analytics directly and joins on wp_posts.ID so each click has a real post title and author next to it. Filter chips on network, location, and date range mean 'all Pinterest clicks from the floating sidebar in March' is a saved view, not a SQL query. Aggregate views pivot click counts per post and per network alongside the standard post list.

The plugin's settings page stays the source of truth for share-button configuration. SleekView does not write to wp_socialsnap_analytics; it only reads the rows the plugin already logged and surfaces them in a way editorial and marketing can actually use without exporting CSVs or asking a developer.

Share-button analytics live in two worlds. The chart world is good for the executive summary: bar chart of total clicks per network, top-five posts of the month, a sparkline trend. The row world is good for everything else: which exact post lost Pinterest traction in week three, which button placement earns its scroll cost on long-form posts, whether a redesign that moved the floating sidebar to the inline-top position changed click distribution by location.

Social Snap's Pro analytics already collects the row data in wp_socialsnap_analytics, but the default admin only renders the chart world. SleekView gives the row world a real table: wp_socialsnap_analytics joined to wp_posts, with filter chips for network, location, post type, and date. Growth marketing finally sees the placement story, editorial sees the long tail, and reporting gets a CSV that matches what marketing uses elsewhere in the stack.

The plugin's chart stays where it is, the click-log table is where the answers live.