Skip to content

Works with your stack

Cookie consent for Joinchat

the click event waits too

← Cookie Rocks for your stack

Joinchat serves its WhatsApp button from your site and contacts no one before the click. On the click, it can also send an event to Google and Meta if their tags are on the page. If those tags are held, nothing reaches them.

By Creame · join.chat · WordPress.org

Is this your product? Tell us if anything here is out of date. Write to us

Joinchat

WordPress plugin

Tested
Tested version
6.4.2
How
Tested automatically around each Cookie Rocks version
Last test
7 November 2026
Latest version
6.4.2 tested
Active installs
700,000+

What Joinchat adds to your visitors’ browser

No trackers In our test of Joinchat 6.4.2 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 Joinchat

Click events follow the tags

On a click, Joinchat sends a lead event to Google Analytics, a Google Ads conversion if set, and a Meta Pixel event if the pixel is loaded. When those tags wait for consent, the events go nowhere.

A counter on your site

Its click counter, on by default, posts to your own site. Nothing goes to another company.

Local storage for auto-open

To open the chat window by itself, Joinchat counts page views in the browser’s local storage. A developer can move it to session storage, or turn off automatic opening to remove storage.

What our tests found on Joinchat

  • Good to know · Click to Chat, Joinchat, WP WhatsAppWhatsApp button plugins keep their state on the site, not with Meta
    • Click to Chat stores ht_ctc_storage.
    • Joinchat stores joinchat_views (a page-view counter updated on every page) and joinchat_hashes.
    • WP WhatsApp (NinjaTeam) sets nta-wa-gdpr for 30 days, only when the visitor ticks its consent box.
    • None of them contacts Meta before the click.

    Read in its code, 17 October 2026, Click to Chat, Joinchat, WP WhatsApp.

    Full detail

    WhatsApp button plugins keep their state on the site only: Click to Chat stores ht_ctc_storage, Joinchat stores joinchat_views (a page-view counter updated on every page) and joinchat_hashes, and WP WhatsApp (NinjaTeam) sets nta-wa-gdpr for 30 days only when the visitor ticks its consent box. None of them contacts Meta before the click.

  • Good to know · JoinchatJoinchat sends click events to Google and Meta tags when they exist

    setting “Clicks Counter (tracking)” · by default: on

    On click it sends events to the site's Google tags, a Google Ads conversion if set, and Meta if present. If those tags are held, nothing reaches Google or Meta.

    Read in its code, 16 October 2026, Joinchat 6.4.2.

    Full detail

    On click, Joinchat sends a generate_lead event through gtag to each G- or GT- tag found, a Google Ads conversion if set, a dataLayer push and fbq('trackCustom') if fbq exists, then opens wa.me or web.whatsapp.com; if those tags are held, nothing reaches Google or Meta. Its click counter (on by default) posts to the site's /wp-json/joinchat/v1/track-click, and the server keeps a hash of IP, user agent, channel and number for 60 seconds. No WP Consent API or Consent Mode default; events joinchat:event and joinchat:track can be cancelled.

  • Depends on a setting · JoinchatJoinchat keeps a page-view count in the browser when it opens by itself

    setting “message_delay” · by default: 10

    joinchat_views goes to localStorage when automatic opening is on (default: after 10 seconds and 2 page views). A cookieless setting moves it to sessionStorage.

    Read in its code, 16 October 2026, Joinchat 6.4.2.

    Full detail

    Joinchat writes joinchat_views to localStorage on page load when automatic opening is on (default: after 10 seconds and 2 page views). The cookieless setting (filter joinchat_get_settings) moves its keys to sessionStorage, and a negative automatic-opening delay removes all storage. The JavaScript event joinchat:starting can pause its start until joinchat_obj.resume().

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.

  • Joinchat 6.4.2, 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: Joinchat 6.4.2 on 7 November 2026, with WordPress 7.1.3.

Questions

What about other WhatsApp plugins?

See WhatsApp buttons for links, button plugins and hosted widgets.

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 Joinchat users

Chat clicks, measured only with consent.

joinchat stays on

Every feature of the complete plugin for 30 days, no card. Joinchat 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.