How to add analytics to WordPress

There's no VisitTrack plugin to install and keep updated — the tracker is one script tag. Avoid editing header.php directly: block themes (Twenty Twenty-Four, Twenty Twenty-Five and most new themes) don't have one, and on classic themes the edit disappears with the next theme update unless you use a child theme.

How to install VisitTrack on WordPress

1. 1

   Step 1: Copy your site id

   Add your WordPress site in VisitTrack and copy the snippet from the install step (or Settings → General). Replace SITE_ID below.

2. 2

   Step 2: Option A — use a header-code plugin

   In wp-admin, go to Plugins → Add New, install and activate WPCode (formerly Insert Headers and Footers). Open Code Snippets → Header & Footer, paste the snippet into Header, and save. Other header/footer plugins work the same way. The first line is the optional queue stub, which lets inline calls (like the WooCommerce snippet below) run before the deferred script has loaded.

   WPCode → HeaderCopy

   <script>window.visitrack=window.visitrack||function(){(window.visitrack.q=window.visitrack.q||[]).push(arguments)}</script>
   <script defer data-site="SITE_ID" src="https://visitrack.app/tracker.js"></script>

3. 3

   Step 3: Option B — print it from wp_head

   Prefer code? Add this to a child theme's functions.php or as a PHP snippet. It also prints the one-line queue stub (so inline calls work before the deferred script loads) and skips administrators so your own browsing isn't counted.

   functions.phpCopy

   // functions.php of a child theme, or a "PHP snippet" in a code-snippets plugin
   add_action('wp_head', function () {
     // Optional: don't count logged-in administrators.
     if (current_user_can('manage_options')) return;
     echo '<script>window.visitrack=window.visitrack||function(){(window.visitrack.q=window.visitrack.q||[]).push(arguments)}</script>' . "\n";
     echo '<script defer data-site="SITE_ID" src="https://visitrack.app/tracker.js"></script>' . "\n";
   });

4. 4

   Step 4: Clear your page cache

   If you use a caching plugin or host-level cache (WP Rocket, LiteSpeed Cache, W3 Total Cache, a managed host's cache), purge it so cached pages pick up the new tag.

How to check VisitTrack is working on WordPress

1. Log out (or use a private window — admins are skipped with Option B) and open two pages of your site.
2. VisitTrack's live view shows you within seconds; posts and pages appear by path in the Pages tab.
3. View source and search for tracker.js. If it's missing, the cache wasn't purged or the snippet isn't active.

Does VisitTrack track WordPress page navigation?

WordPress pages are full page loads, so each one is a pageview. Paginated archives (/blog/page/2/) have their own paths and are counted separately; query-string variations such as ?replytocom= count toward the same path.

To keep the admin area and login out, nothing extra is needed — the tag is printed on the front end only (wp_head doesn't run in wp-admin). Add data-exclude="/my-account/*" if you also want to skip WooCommerce account pages.

How to track custom events and goals in WordPress

In the block editor, select a Button block, open Advanced in the sidebar, and you can add a CSS class — but not custom attributes. For a button you want to count, use a Custom HTML block with data-vt-goal, or make the button link to a page and create a page goal for that path.

Contact Form 7, WPForms and Gravity Forms submit regular HTML forms, so with automatic events on, each submission records a form_submit event named after the form's id or name. For a cleaner conversion, redirect to a thank-you page and create a page goal for its exact path in Settings → Goals.

<!-- Custom HTML block -->
<a class="wp-element-button" href="/book-a-call/" data-vt-goal="book_call_click">Book a call</a>
<section data-vt-scroll="pricing_viewed">…</section>

mailto: and tel: links (common in headers and footers) are recorded as contact_click events automatically — turn that into a goal to count calls and emails.

Revenue attribution on WordPress

WooCommerce payments usually run through gateways that use Stripe PaymentIntents or other processors, which VisitTrack's revenue attribution doesn't read (it attributes Stripe Checkout sessions, Polar, Lemon Squeezy, Paddle and Razorpay — see Revenue attribution). You can still count purchases by source: this hook fires a purchase event on the order-received page, with the order total in its props. It relies on the queue stub included in both options above. If your store uses the block-based order confirmation template, confirm the event fires by adding data-debug to the tag once.

// Fire one "purchase" event on WooCommerce's order-received page.
add_action('woocommerce_thankyou', function ($order_id) {
  $order = wc_get_order($order_id);
  if (!$order) return;
  printf(
    '<script>window.visitrack("purchase", %s);</script>',
    wp_json_encode([
      'amountcents' => (int) round($order->get_total() * 100),
      'currency'    => $order->get_currency(),
    ])
  );
});

Script options you might need on WordPress

All optional — add them to the same tag. Full reference: script configuration.

WordPress troubleshooting

Not on WordPress? See all 29 integration guides.