ACF Extended's underlying posts: acf-field rows whose field_type matches an ACFE-registered type, acf-field-group rows for grouping, and the form submission post type ACFE registers when the Forms module is on. No premium add-on beyond ACFE itself is needed.

Mostly. The free ACFE plugin still registers most of the extended field types, so the field-usage charts populate fully. The front-end Forms module is ACFE Pro, so the submission cards only populate on installs that have Pro active.

Yes. Filter the field-instance dataset to field_type in the ACFE-registered list (clone, code_editor, columns, post_types, taxonomy_terms and the rest) and every chart narrows to ACFE only. A second card on plain ACF gives the side-by-side.

Yes. Group submission_date by day or week with an Area or Line card and filter to a specific form_name. Useful for campaign retros and for spotting forms that quietly stop converting after a redesign.

Yes. ACFE's dynamic blocks register through the standard block API, so SleekView can group post_content occurrences by block name. A Bar of block usage shows which ACFE blocks are load-bearing and which were tried once.

Yes. ACFE updates add and rename field types occasionally, but the underlying acf-field storage is stable. The dashboard reads field_type as a column, so new types appear automatically in the pie without any configuration.

Yes. Any filtered set behind a chart card exports as CSV. Useful for handing a refactor brief to a backend dev or for sending a campaign retro to a marketing lead.

Yes. ACFE field types are exposed through WPGraphQL for ACF the same way standard ACF types are. The dashboard can join field exposure with field usage for a fuller headless audit.