Overview
WhatsApp Click to Chat provides a lightweight mechanism for websites to offer one-click messaging to a business WhatsApp number. Unlike the full WhatsApp Business widget, Click to Chat is typically implemented as a simple floating button or link that opens a WhatsApp conversation when clicked. It requires no JavaScript SDK, sets no cookies, and has the smallest possible tracking footprint — functioning purely as a navigation action rather than an embedded application.
What This Script Does
WhatsApp Click to Chat can be implemented with zero client-side scripts.
- Link-based implementation: The simplest form is a direct link to
wa.me/{phone_number}?text={pre-filled_message}orapi.whatsapp.com/send?phone={number}. When clicked, the visitor's device opens the WhatsApp application (mobile) or WhatsApp Web (desktop) with the business number pre-filled. - Button rendering: A styled HTML button or floating action button on the page links to the
wa.meURL. No JavaScript is required for the core functionality — it's a standard hyperlink. - No scripts loaded: The core Click to Chat functionality does not require loading any JavaScript from WhatsApp or Meta domains.
- No cookies set: No cookies, localStorage, or sessionStorage entries are created on the host domain.
- No data collected: No visitor data is transmitted to WhatsApp or Meta until the visitor explicitly clicks the button and initiates a conversation. The
wa.meredirect itself does not set cookies. - Third-party plugins: Some websites use third-party plugins to add floating WhatsApp buttons with animations, availability schedules, or pre-chat messages. These plugins may introduce their own cookies or scripts beyond the core Click to Chat functionality.
Consent & Compliance
WhatsApp Click to Chat falls under the functional consent category.
Under GDPR and ePrivacy, the core Click to Chat implementation (a hyperlink to wa.me) has no ePrivacy implications. It sets no cookies, stores no data on the device, and makes no network requests until the visitor clicks. There is nothing to consent to from a cookie perspective. If third-party plugins are used to render the button, those plugins should be assessed independently.
Under CCPA/CPRA, no personal information is collected or processed until the visitor initiates a WhatsApp conversation. At that point, WhatsApp's own privacy terms govern the messaging interaction.
Should You Block This Without Consent?
No. WhatsApp Click to Chat is a simple hyperlink with no tracking, no cookies, and no data collection. Blocking it would remove a communication channel for no privacy benefit. Visitors must explicitly click the button to initiate any data exchange. Use the native wa.me link implementation rather than third-party plugins to maintain the zero-tracking footprint.
Consent Categories
Also Known As
Industries
Tracked Domains (2)
whatsapp.comFunctionalwa.meFunctionalFrequently Asked Questions
Does WhatsApp Click to Chat require user consent?
No. Click to Chat is typically a plain hyperlink to wa.me with no JavaScript, no cookies, and no data collection. There is nothing to consent to. No network requests are made to WhatsApp or Meta until the visitor explicitly clicks the link.
What does WhatsApp Click to Chat actually load?
The core implementation is a standard HTML link to wa.me/{phone}. No scripts are loaded from WhatsApp or Meta domains. No cookies are set on the host domain. Data is only transmitted when the visitor clicks and their device opens the WhatsApp application.
How does ConsentStack treat WhatsApp Click to Chat?
ConsentStack classifies WhatsApp Click to Chat as functional. It is never blocked by the consent layer. If a third-party JavaScript plugin is used to render the button, that plugin should be assessed separately as it may introduce its own cookies.
Related Vendors
Manage consent for WhatsApp Click to Chat
ConsentStack automatically detects and manages WhatsApp Click to Chat trackers so your site stays compliant with global privacy regulations.