Click-to-WhatsApp Ads
Ad-to-conversation routing is planned — not available today.
Click-to-WhatsApp ads are Meta ad campaigns where clicking the ad opens a WhatsApp conversation with the business. Wavy's backend can receive inbound WhatsApp messages through the Meta webhook, but there is no integration with the Meta Ads API, no ad creation or management interface, and no tracking path that links an ad click to a specific conversation in the workspace inbox. The capability is planned. This page is not indexed because no ads integration exists.
What does not exist
Removed from this page because it is not built.
The following were referenced in placeholder content but are not part of any live ads offering.
- Meta Ads API integration — The backend has a Meta WhatsApp client for messaging, but no Meta Marketing API client for creating, managing, or reporting on ad campaigns. No ads endpoint is called.
- Ad creation interface — There is no workspace UI for designing a click-to-WhatsApp ad, setting a budget, defining targeting, or launching a campaign. The ads page in the workspace is a placeholder.
- Ad-to-conversation attribution — When an inbound message arrives via webhook, there is no field or parameter that links it to a specific ad campaign. The conversation is created from the contact's phone number, not from an ad click ID.
- Ad performance metrics — There is no cost-per-click, cost-per-conversation, click-through rate, or return-on-ad-spend tracking. No ads data is ingested or stored.
What does exist
The messaging path that would receive ad clicks — and its limits.
Wavy can receive the WhatsApp conversation that an ad click opens, but it cannot attribute that conversation to the ad.
- Inbound webhook receiver — The
/webhooks/metaendpoint receives inbound messages and creates conversations. If a user clicks a click-to-WhatsApp ad and sends a message, that message reaches the inbox — but without any ad attribution data. - Contacts and conversations — The contact is created from the inbound phone number, and the conversation is tracked in the inbox. This is a standard inbound flow, indistinguishable from any other first message.
- Ads page placeholder — The workspace has an ads route, but it is a placeholder page with no backend ads service behind it. No ad campaign can be created or managed from it.
- No Meta Marketing API scope — The access token used by the WhatsApp client is scoped to messaging. It does not include the ads management scope, and no code requests it.
The intended path
What click-to-WhatsApp ads would look like when built.
If and when click-to-WhatsApp ads are built, the intended path would integrate with the Meta Marketing API to create and manage ad campaigns that use the click-to-WhatsApp objective. When a user clicks the ad and sends a message, the inbound webhook would need to receive an ad attribution parameter — such as a campaign ID or referral source — and link the resulting conversation to the ad campaign for performance tracking.
This would require a Meta Marketing API client with ads management scope, an ad creation and management UI in the workspace, an attribution field on inbound messages, and a reporting surface for cost-per-conversation and campaign performance. None of that work has been started. This page will be updated and the noindex directive removed when an ads integration reaches a configuration-dependent state.
Questions
Click-to-WhatsApp ads — straight answers.
Can I create click-to-WhatsApp ads through Wavy today?
No. There is no Meta Ads API integration, no ad creation UI, and no ads management interface. The ads page in the workspace is a placeholder.
If I run click-to-WhatsApp ads manually, will Wavy receive the conversations?
Yes, if your webhook is configured. When a user clicks your ad and sends a message, the inbound webhook creates a conversation in the inbox. However, Wavy cannot attribute that conversation to the ad — it appears as a standard inbound message.
Can I see which conversations came from my ads?
No. There is no ad attribution field on inbound messages. The conversation is created from the contact's phone number without any campaign or ad-click reference.
Does Wavy track ad spend or ROAS?
No. No ads data is ingested. There is no cost-per-click, cost-per-conversation, or return-on-ad-spend metric because no Meta Ads API integration exists.
Will click-to-WhatsApp ads be added in the future?
It is a planned capability. When it reaches a configuration-dependent state — a Meta Marketing API client exists, ads can be created, and conversations are attributed to campaigns — this page will be updated and the noindex directive removed.
Ads integration is planned, not shipped.
Explore Wavy's available messaging, automation, and campaign capabilities today. When click-to-WhatsApp ads are built, this page will say so plainly.