Both. The auhfc_settings option holds the literal head, body, and footer code as strings, and SleekView can display them in a table card next to the chart cards. The chart cards themselves aggregate on counts, slots, and timestamps, so the visualisation stays readable even on sites with hundreds of overrides.

Only if the _auhfc_* meta row still exists with an empty value. Head Footer Code deletes the row when the editor clears the field, so a Number card with a non-empty filter shows only live overrides. A separate card can include emptied rows if the team wants to track historical churn.

Yes. The Misha build and the original Stefano Lissa version both use the auhfc_settings option name and the _auhfc_* meta keys. Any fork that keeps the same storage layout works without configuration. The plugin slug only matters for picking up settings UI changes, not for reporting.

Yes. A Bar card can group by post_id and aggregate Maximum on the character length of the _auhfc_head meta_value, useful for catching the one landing page where someone pasted an entire GTM container by accident instead of a one-line snippet.

SleekView reads wp_options and wp_postmeta directly on dashboard load, so an override edit shows up immediately on the next refresh. Heavier aggregates can opt into a configurable cache, but the default behaviour is live reads against the actual storage Head Footer Code writes to.

Yes. Saved chart views support role-based visibility, so webmasters, ad ops, and external consultants see only the dashboards you allow them to see. The scoping happens at the view level, not at the underlying data level, so audit trails stay intact.

Yes. Any saved chart view can be embedded on a frontend page with role-based access, useful for an internal team page or a client portal where the dashboard needs to live outside WP Admin behind a login of its own.

No. The plugin keeps reading wp_options once per page load to print the snippets, and SleekView's queries only run when the dashboard renders. The two systems read the same rows but the frontend tag injection path is untouched by anything SleekView Charts does.