Data analytics

What is measured

Analytics uses execution results stored locally by the extension. Explore/Profile records include browses, likes, bookmarks, comments, follows and duration. Comment workflows also record replies and collected users. Follows are accounts you followed, not followers gained; browses are not impressions on your posts; collected profiles are not conversions.

View records

Open Data Analytics and choose Explore, Comment or Profile.
Check summary cards and the execution table, including workflow name and time.
Open an execution's details to inspect its status, operations and errors.
Use the table export menu for CSV or JSON when you need an offline check. Confirm the exported rows and fields; do not assume export is limited to the visible page.

Search, filters and export scope

The execution table supports workflow-name search and ascending/descending sorting by name or creation time. Date choices include all, today, yesterday, the last seven days and the last thirty days. Status filters help inspect successful, stopped or failed records. Review the filtered list before export: export uses the filtered record set, not only the current page.

CSV is useful in a spreadsheet; JSON retains structured fields. Exports contain the table's defined fields and are not full database backups. Check text encoding and column names after opening the file. These filters concern execution records, not platform readership trends.

Interpret the result

Running, success, suspended, timeout and failure describe execution status. Success does not mean the platform increased your reach. Interrupted records may be incomplete, and unfinished tasks may lack a complete duration. Summaries join workflows to logs, so deleting a workflow can change which historical records appear in summaries.

Review performance

Compare configuration with completed actions first. No comments can mean commenting was disabled, filters matched nothing, content was already processed or a request failed. Check your platform's creator tools separately for readership and follower changes. Include configuration, review and troubleshooting time when assessing efficiency; automatic runtime alone is not time saved.

Storage and cleanup

Logs live in the current browser's extension database and can include action targets, identifiers and error details, not only anonymous counters. Downloads stay on your device and are not automatic cloud backups. Resetting the database clears local workflows, templates, users and logs; preserve needed records first. PDF reports, cross-device cloud synchronization and arbitrary date-range trend charts are not promised here.

More: Data and permissions.

Applies to extension 3.5.3. Reviewed on September 17, 2026.