Official WordPress plugin

Install ReviseFlow with the official WordPress plugin

For WordPress sites, use the ReviseFlow plugin from WordPress.org. Do not paste script tags into theme files, GTM, or code-snippet plugins. The plugin handles widget loading, token validation, wp-admin board access, visibility controls, and WordPress context automatically.

Plugin-only setup

This is the only recommended WordPress setup path. Install the official plugin, connect your ReviseFlow token, and continue from wp-admin.

  1. 1

    Install the official plugin

    In WordPress, go to Plugins → Add New, search for ReviseFlow — Visual Feedback & Bug Reports, then click Install Now and Activate.

  2. 2

    Create a ReviseFlow project

    Sign up or log in to ReviseFlow, create a WordPress website project, and copy the project widget token.

  3. 3

    Paste the token in wp-admin

    Open ReviseFlow → Settings in wp-admin, paste the token, then click Test connection. Save after the project details are confirmed.

  4. 4

    Open the embedded board

    Open ReviseFlow → Board. The plugin loads your ReviseFlow board directly inside wp-admin, so you can triage incoming feedback without leaving WordPress.

  5. 5

    Visit your public site

    Open a public page on your WordPress site. The ReviseFlow feedback button appears automatically when the plugin is enabled and the token is valid.

What the plugin handles for you

  • -Loading the ReviseFlow widget on public WordPress pages
  • -Keeping script tags out of header.php, footer.php, GTM, and code-snippet plugins
  • -Validating your widget token from ReviseFlow → Settings
  • -Embedding the ReviseFlow board inside wp-admin
  • -Adding per-page hide controls in the post and page editor
  • -Supporting role-based visibility for staging and internal review
  • -Adding a front-end admin-bar shortcut for logged-in users
  • -Attaching WordPress, theme, plugin, WooCommerce, and language context to feedback reports

Do not manually install ReviseFlow on WordPress

Manual website snippets are for non-WordPress sites. On WordPress, the official plugin is cleaner and safer because it prevents duplicate launchers and keeps settings inside wp-admin.

  • !Do not paste the ReviseFlow script into header.php or footer.php.
  • !Do not use a code-snippet plugin for ReviseFlow on WordPress.
  • !Do not add the widget through Google Tag Manager if this is a WordPress site.
  • !Do not install both the WordPress plugin and a manual script tag on the same site.
  • !Do not skip Test connection after pasting the widget token.

Recommended first settings

SettingRecommended start
Widget tokenPaste from your ReviseFlow project
Enable widgetOn
Show widget to rolesPick admins/editors for staging, leave empty for all visitors
Admin Bar shortcutOn for logged-in QA and editors
Per-page hideUse for login, legal, checkout, or private pages
WooCommerce checkout pagesKeep hidden unless you explicitly want checkout feedback

Troubleshooting

Plugin is installed, but the widget does not appear

Confirm the plugin is active, the widget is enabled in ReviseFlow → Settings, the token test succeeds, and the current page is not hidden from the ReviseFlow Widget meta box.

Test connection fails

Copy the token again from the ReviseFlow project, remove trailing spaces, and confirm the project domain matches the WordPress site URL.

You previously added a manual script

Remove the old script tag first, then keep only the official WordPress plugin active. Running both paths can show duplicate launchers.

Cache delays the button

Save the plugin settings, clear your page-cache plugin, then hard-refresh the public page with Ctrl/Cmd + Shift + R.

Page builder preview looks different

The plugin avoids builder edit and preview modes. Test the live URL in a normal browser tab after publishing or updating the page.

Privacy and data

The WordPress plugin connects to ReviseFlow to load the feedback widget, validate the widget token, create the embedded board session, upload feedback files, and create feedback reports.

The widget itself does not set tracking cookies. Diagnostic collectors start after a visitor opens the feedback widget. Submitted feedback can include comments, screenshots, annotations, browser and device metadata, page URL, diagnostic summaries, and WordPress context. Disclose this in your privacy policy.

Use the official plugin, then open your board

Install from WordPress.org, paste your widget token in ReviseFlow → Settings, and use ReviseFlow → Board to manage feedback inside wp-admin.