Skip to content

Works with your stack

Cookie consent for Shared Counts

plain links, counts on the server

← Cookie Rocks for your stack

Shared Counts shows share buttons as plain links, with its script and styles served by your site. Visitor pages get no outside script, no frame and no cookie. Share counts are fetched by your server, not the visitor’s browser.

Shared Counts

WordPress plugin

Tested
Tested version
1.5.0
How
Tested automatically around each Cookie Rocks version
Last test
7 November 2026

What Shared Counts adds to your visitors’ browser

No trackers In our test of Shared Counts 1.5.0 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.

What matters for consent with Shared Counts

Links wait for the click

Each button is a plain link. Nothing loads from a social network until the visitor clicks and leaves your page.

Counts from your server

When counts are out of date, your server asks for them at the end of a page view. It sends only the post address, nothing about the visitor.

Click tracking follows analytics

With social tracking on, a click is sent to Google Analytics only if Analytics is already on the page. Analytics follows the visitor’s choice like any other tracker, and Cookie Rocks holds known trackers until the visitor agrees.

What our tests found on Shared Counts

  • Good to know · Shared CountsShared Counts loads nothing from other sites; the server fetches share counts

    setting “Count Source”

    Share buttons are plain links: no third-party script, cookie or storage. When counts are stale, the server sends only the post address to SharedCount, Facebook, Pinterest or Yummly.

    Read in its code, 16 October 2026, Shared Counts 1.5.0.

    Full detail

    Shared Counts 1.5.0 renders share buttons as plain links and serves its script and stylesheet from the site: no third-party script, frame, cookie or browser storage on visitor pages. Share counts are fetched by the site's server at the end of a page view whose counts are stale, sending only the post address to SharedCount, Facebook, Pinterest or Yummly. With social tracking on, a click calls ga() or __gaTracker only if they are already loaded.

How we test it

Around each version, with its latest release

Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.

  • Shared Counts 1.5.0, tested on 7 November 2026.
  • The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
  • Settings of the test: Default settings after activation.
  • Last run: Shared Counts 1.5.0 on 7 November 2026, with WordPress 7.1.3.

Questions

Does Shared Counts need consent?

Not for the buttons. They are plain links, and nothing reaches a social network before the click.

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For sites with Shared Counts

Share buttons for everyone.

links never wait

Every feature of the complete plugin for 30 days, no card. Shared Counts keeps working as it does today.

  • During the trial: everything, including the full settings and the scans
  • After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
  • What waits for a key: most settings, updates and support

How the trial works, in detail

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.