Skip to Content
WordPress troubleshooting

WordPress troubleshooting

Most WordPress issues come down to caching, an order that has not reached Completed, or a site that is not connected yet. Work through the checks below. For issues that are not specific to WordPress (magic-link emails, “Unauthorized”, and so on), see the general Troubleshooting guide.

I connected, but no data shows

  1. Purge your page cache. This is the most common cause. If your host or a caching plugin is serving old HTML, that HTML has no Voris tag. Purge the cache and load a page again. The plugin reminds you to do this whenever you save.
  2. Confirm the site is connected and tracking is on. On Tools → Voris, check that the site is connected and tracking is enabled.
  3. Load a page in a fresh incognito window, then watch the live indicator at the top of your Voris dashboard for a green dot and a rising event count.
  4. Check for an ad blocker on the browser you are testing with — it may block the tag. Test in a clean browser.
  5. Check a Content Security Policy. If your site sends a CSP, it must allow the script from cdn.voris.ai and the connection to ingest.voris.ai. See Troubleshooting → CSP.

If it still will not show, the general waiting-for-first-event checklist applies to WordPress too.

I changed a setting and nothing changed

Almost always the page cache again. WordPress is serving the previously-cached HTML. Purge the cache and the change takes effect.

Store revenue is not showing up

Revenue is reported when an order reaches Completed, not when it is paid. Stores that leave orders in Processing indefinitely will not see revenue in Voris. Move an order to Completed and it reports. Virtual and downloadable orders that auto-complete report immediately. Free or zero-total orders carry no revenue and are not reported. See WooCommerce revenue tracking.

A refund is not showing up

A refund is only reported when Voris confirmed receiving the original purchase. If the purchase was never delivered — for example, the site was not connected when the order completed — the plugin skips the refund so your dashboard does not show negative revenue against a sale Voris has no record of. The skip is recorded in the delivery log.

The delivery log

When the plugin cannot send a server-side event (a purchase or refund), it retries in the background. If an event still cannot be delivered, it is listed for you on the Tools → Voris settings screen, with the reason. The log keeps the most recent entries.

Reasons you might see include:

  • A network or Voris-side error — usually transient; the background retry handles most of these.
  • purchase_not_delivered — a refund was skipped because Voris never confirmed the original purchase (see above).
  • refused_locally — the order could not produce a valid event (for example, an unusable currency, or an order reference that looked like it might contain personal data and was refused before sending).

A revenue report is never allowed to break an order, so these are recorded and surfaced rather than thrown.

Does the plugin slow my site down?

No. The tracking tag loads from Voris’s CDN with defer, and revenue events are sent after the page has finished rendering, with a two-second ceiling. If Voris is slow or unreachable, your pages, your admin, and your checkout carry on exactly as if the plugin were not installed.

What happens when I uninstall?

Everything the plugin stored is removed on uninstall. If you would rather keep your settings for later, tick Keep my settings if I uninstall Voris on the settings screen first. Deactivating the plugin never deletes anything.

Still need help?

If none of the above resolves it, contact us at support@voris.ai with your site’s URL and what you have already tried.