How to identify users coming from a Click to Chat WhatsApp ad published on Facebook

Index:

1. Introduction
2. In Thread Context
3. Customizing the conversation in the Builder
4. Identifying user context in Blip Desk

Introduction

Click to WhatsApp is a new ad format from Meta that shortens the consumer's journey, taking people from major social networks directly to WhatsApp with just one click.

Click to WhatsApp is an option to streamline the customer's journey in the marketing funnel, as it allows any user to start a conversation with a number without adding it to their contacts, with just one click.  

But to fully leverage the potential of WhatsApp in lead generation and qualification using Click To WhatsApp ads, it's important to ensure that users have a good experience in the conversational channel. Reducing frictions and creating personalized experiences that will lead the lead to the conversion point!

In Thread Context

Conversations initiated from Click To WhatsApp ads arrive at Blip with valuable information about the ads.

When a user clicks on a Click to WhatsApp ad and sends a message to the company, the advertising company receives a message notification including the referral property, which provides additional context about the ad that originated that message: what we call In Thread Context.

As soon as the user sends the first message, Blip saves this In Thread Context information in the contact extras, allowing you to use these identifiers to direct the user in the conversational flow.

Customizing the conversation in the Builder

In order to create personalized conversational flows, leading the user straight to the topic they have shown interest in when interacting with your Click To WhatsApp ads. Let's use the variables stored in the contact's extras to define the exit conditions of the intelligent contact's conversational flow.

In the Builder, identify the block where the targeting rules will be configured:

Click on the block and open the “exit conditions” option.

In the exit conditions, we will check if the “variable” “contact.extras.sourceid” “exists.” Then, determine to which conversational flow your contact should be directed.

With this rule, all users initiating conversations from ads will be directed to the chosen flow without distinguishing between ads.

You can also create a condition by checking if the variable is equal to a specific ID, making the conversation even more personalized for each of your ads.

In this case, we will configure the exit condition as “variable” “contact.extras.sourceid” “is” “equal to”, and specify the values of the ad IDs in the field below.

Identifying user context in Blip Desk

With the variables from the In Thread Context saved in the extras of contacts, sellers or agents using Blip Desk can have even more context about the user's interests who interacted through an advertisement.

In addition to the ad ID, it's possible to open a preview of the ad by clicking on the link that appears in the variable SourceURL.

Remember: after concluding the service, it may be beneficial to remove the variable from the contact's extras, preventing the user from always being directed to this conversational flow.

And don't forget! With the Click Tracker, Blip provides you with a clear view of the results of your ads, allowing you to direct your investments into strategies that work for your business.

For more information, visit the discussion on the subject at our community or videos on our channel. 😃