# Click-to-WhatsApp ads Keep the promise from ad to answer An ad with a useful invitation Find the right collection for your space. Open the conversation The customer asks about the collection. Qualify the request Understand the product and service needs. Complete the next step Record the real appointment or order. Ad referral From the connected ad integration Conversation Matched by supported identity Lead Qualified by business rules Outcome Confirmed by owning system Preserve the source Keep ad click identity, website UTMs and internal campaign IDs distinct. Example ad journey. Available referral data depends on your ad integration. ## Deliver on the reason someone clicked. Keep the offer, creative and opening conversation aligned. Start with the question or choice the customer expects from the ad. ## Reduce the first-step effort Use a useful opening prompt and a small number of relevant options. Avoid asking the customer to restate everything the ad already established. ## Make the response available Prepare the AI or team that receives the conversation. An unanswered chat wastes the intent the campaign worked to create. **One promise, from ad to conversation Example** Mora Studio Example ad Ceramics collection featured in the example ad Find the right piece for your space. Message us about the new collection. I saw your collection. Which vase works for a small table? ## Help the customer reach a meaningful next step. Connect the request to the relevant knowledge, product or service workflow. Ask only for the details that change qualification or fulfillment. ## Choose the useful path Use a short native form, a product choice, an appointment or a human conversation according to the customer’s task. ## Keep the outcome honest Mark a lead qualified only when it meets your business definition. Record bookings and purchases from their owning systems. ## Carry attribution through the whole journey. Preserve the ad referral or click identity when the connected ad integration supplies it. Join it to the conversation and the confirmed business event without assuming every inbound message exposes the same referral fields. ## Separate the identities An ad click identifier, a website UTM and your campaign ID are different data. Keep their provenance and use the supported join rather than manufacturing a click ID. ## Review quality as well as volume Compare spend, opened conversations, qualified leads and completed outcomes. Deduplicate repeated events and account for the chosen attribution window. ## Click-to-WhatsApp ads questions ### Is a click-to-WhatsApp ad the same as a WhatsApp campaign? No. An ad brings a customer into a conversation from an advertising placement. A WhatsApp campaign sends eligible messages to an audience that already has the required permission. ### Can we measure purchases after the conversation? Join the conversation and available ad source to a confirmed order or payment event. Define the attribution window and deduplication rules for that integration. ### Does every inbound API message include an ad click ID? Do not assume that. Preserve referral data when the connected ad integration provides it and follow the published fields of the actual integration. ### Should an AI agent greet every ad visitor? Use AI when it can answer the expected request and complete a useful next step. Keep a clear human route for complex or ambiguous enquiries. ## Connect the complete journey - [Click-to-WhatsApp ads guide](/docs/guides/whatsapp/click-to-whatsapp-attribution): Follow the setup, operating decisions and verification steps. - [WhatsApp marketing](/whatsapp-api/features/marketing): Create relevant campaigns and help customers respond. - [WhatsApp AI agents](/whatsapp-api/features/ai-agents): Answer questions, take action and hand over to your team. - [WhatsApp analytics](/whatsapp-api/features/analytics): Follow delivery, customer response and business results. - [WhatsApp resource library](/whatsapp-api/resources): Explore implementation guides, explained answers and comparisons. - [WhatsApp platform](/whatsapp-api): Explore the connected product and choose the next capability. ## Scale without losing control. Organize teams in workspaces, control API access, and trace changes through audit logs. Harbor Organization Workspaces Production Sandbox ### Delivery agent API key · Customer operations team Active Permissions Access Email Read & write SMS Read & write WhatsApp Read Read & write AL Alex Lee Admin Permissions updated ### Audit log Production API key updated Alex Lee · 09:42:18 UTC Workspace Production Resource Delivery agent WhatsApp Read Read & write Succeeded [Workspaces](/docs/guides/workspaces)[Team roles](/docs/guides/users-teams-roles)[API authentication](/docs/guides/authentication) [Explore Enterprise](/enterprise) ## Start with WhatsApp. Build across channels with Bird. [Get started](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fwhatsapp) · [Contact Sales](/demo?product=whatsapp) [Email](/email-api) · [SMS](/sms-api) · [WhatsApp](/whatsapp-api) · [Apple Messages](/apple-messages-api) · [Voice](/voice-api) ## Related resources - [Connecting WhatsApp to Bird: from buying a number to a live channel](/learn/whatsapp/connecting-whatsapp-to-bird) (video) - [Sending WhatsApp messages](/docs/guides/whatsapp/sending-whatsapp) (docs) - [What is the 24-hour customer service window on WhatsApp?](/explained/whatsapp/what-is-the-24-hour-customer-service-window) (answer) - [WhatsApp message builder](/tools/whatsapp-message-builder) (tool) [Get an implementation brief](/learn/workspace?topic=whatsapp)