ClickReach – Social Share Buttons & Counter

Install and activate ClickReach, then go to Settings > ClickReach Social Share Buttons. Choose your networks, button style, and where the buttons should appear (above or below content), and click Save Settings. The share buttons appear automatically on your selected post types. To place them somewhere specific, use the [clickreach_social_share_buttons] shortcode.

Yes. WhatsApp is one of the built-in networks, along with Facebook, X (Twitter), LinkedIn, Pinterest, Reddit, and Copy Link. Enable it in the Social Networks setting.

Yes. Each button can show its own share count, and an optional Total Shares badge shows the combined count for the post. You can show counts to everyone, only to logged-in users, or hide them.

No! The frontend sharing buttons and AJAX click tracker are written in pure vanilla JavaScript, ensuring zero dependency on jQuery and optimal Core Web Vitals scores.

Not at all. The plugin uses pure inline SVGs (less than 3KB total) and loads CSS/JS conditionally only on pages where buttons are actively displayed.

When a visitor clicks a share link, a secure background AJAX request increments the recorded count for that specific post and platform, updating the live counter in real time without refreshing the page. Counts are based on clicks on your share buttons, so they work without any social network API keys or third-party count services.

To keep counts honest, each visitor is counted once per post and per network every hour, and each visitor can add at most 30 clicks per hour across your whole site. Repeated clicks still open the share window as normal; they just are not counted again. This also stops bots and scripts from inflating your numbers.

Yes. Click tracking works on cached pages (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, and others), because anonymous clicks are protected by rate limiting rather than by a page nonce that can expire inside a cached page.

The rate limit identifies visitors by their IP address. If your server sees the proxy's IP instead of the visitor's real IP, many visitors look like one visitor and fewer clicks are counted. Most hosts already restore the real visitor IP. If yours does not, you can supply it with the ssbc_client_ip filter, for example in a small custom plugin: add_filter( 'ssbc_client_ip', function ( $ip ) { return isset( $_SERVER['HTTP_CF_CONNECTING_IP'] ) ? sanitize_text_field( wp_unslash( $_SERVER['HTTP_CF_CONNECTING_IP'] ) ) : $ip; } ); Only use a header your proxy sets itself (such as CF-Connecting-IP behind Cloudflare). Headers like X-Forwarded-For can be faked by visitors when there is no proxy in front of your site.

Yes! Simply use the shortcode [clickreach_social_share_buttons] inside any post, page, block, or page builder (Elementor, Beaver Builder, etc.).

Yes, completely. It does not set cookies or use browser storage, does not collect personal visitor data, and does not connect to third-party ad or tracking networks. The only external connections made are the standard share redirect URLs that open on the social platform's own website when a user clicks a share button — no data is sent automatically or in the background. To prevent count inflation, the visitor's IP address is turned into a salted, one-way hash that is stored only in temporary WordPress transients for one hour; raw IP addresses are never stored.