Two tools exist specifically so a support question can be answered from evidence rather than guesswork.
The Diagnostics tab:
A read only system report covering:
- The plugin version and its current state
- Critical plugin files, confirming nothing is missing from the install
- Your PHP version and configuration
- The required PHP extensions and whether each is present
- Your WordPress version and relevant settings
- Your database server
- The plugin's own database tables and whether each exists
- Detected potential plugin conflicts
- A full list of active plugins
The conflict section is the one to read first when something behaves strangely, because security plugins that block form posts, caching plugins that serve stale pages and SEO plugins that rewrite URLs are the usual causes.
The debug log:
The plugin writes to its own log file at wp-content/uploads/fcreports-assets/plugin-debug.log. It does not depend on WordPress debugging being switched on, although entries are also mirrored into the WordPress debug log when that is enabled.
What gets logged:
- Every opt-in attempt, with the email, the funnel, the provider and the list used
- Every successful subscription
- Every failed subscription, with the reason returned
- Cases where a lead was stored locally but not delivered to the provider
- PDF rebranding errors
Reading and clearing it:
The Settings tab shows the most recent hundred entries, newest first. There is a copy to clipboard button for pasting into a support ticket, and a clear button that empties the file.
What should I send with a support ticket?
Include your WordPress and PHP versions, the plugin version, your site URL, a clear description of what you did and what happened, screenshots of any error, and the relevant debug log lines. A ticket with the log attached is usually answered in one reply rather than three.
The database tables:
The plugin creates tables for funnel settings, opt-ins, page views, aggregate statistics and Splash page statistics. It checks they exist on every load, which is what makes it survive a host migration or a database restore, and runs its column upgrades only when the stored version number changes.