Skip to main content
Flowella records how each WhatsApp conversation started and writes it to the HubSpot contact. Use these properties to see which Click to WhatsApp ads, links and QR codes bring you leads. For links that lead to your own website, use HubSpot’s standard UTM tracking alongside them.

What Flowella writes to HubSpot

Flowella writes four contact properties in the Flowella Properties group. It creates them in HubSpot the first time it writes one. This needs CRM contacts (auto-create on new WhatsApp chat) under Unlocked on the Capabilities card in Settings → HubSpot. See Capabilities. All four are single-line text properties. Flowella entry point takes these values: ad wins: a conversation with an ad click ID is ad even if the message also matched an entry point.

When Flowella writes the properties

Flowella writes the ad properties again each time the contact messages you in that conversation. Messages in conversations that didn’t come from an ad don’t write anything, so link, qr and direct only reach HubSpot when the contact completes a Flow. A few rules decide which values you see:
  • Flowella keeps the attribution on the conversation, and there is one conversation per contact on each of your WhatsApp numbers.
  • If the contact taps an ad again later and messages you, Flowella replaces the stored click with the new one.
  • A conversation keeps the first entry point it matched.
  • Flowella doesn’t clear these properties. For example, a contact first comes from an ad, then completes a Flow in another conversation that didn’t. Flowella entry point changes, but the ad properties keep their old values. If the contact then messages you again in the ad conversation, Flowella entry point goes back to ad.

Click to WhatsApp ads

When someone taps a Click to WhatsApp ad on Facebook or Instagram and messages you, Meta adds the ad’s details to the message. These include the click ID (ctwa_clid), the ad ID and the ad’s URL. Flowella stores them on the conversation. See Meta’s text messages webhook reference for the fields Meta sends. This works for every organisation, with or without entry points.
Meta doesn’t send a click ID for ads shown in WhatsApp Status. Flowella only records an ad when the click ID is present, so conversations from these placements show as direct, or as the entry point their message matched.

Lead events sent to Meta

When a contact who came from a Click to WhatsApp ad completes a WhatsApp Flow, Flowella sends a LeadSubmitted event to Meta’s Conversions API for Business Messaging. Meta can then attribute the lead to your ad. Flowella sends the event automatically when all of these are true:
  • The conversation has a click ID from the ad.
  • The contact completes the Flow within 7 days of messaging you from the ad.
  • Flowella hasn’t sent a LeadSubmitted event for that click before. It sends one per click, however many Flows the contact completes.
Flowella sends the event even if the contact isn’t linked to a HubSpot contact. The event carries a currency and a value, which default to USD and 0. If your organisation has entry points, change them in the ad attribution panel. Meta decides where these events appear in its reporting. See Meta’s Conversions API for Business Messaging documentation. For the ad set-up in Meta Ads Manager, see Click to WhatsApp ads.
Early access. Entry points, which give you tracked WhatsApp links and QR codes, are available to selected organisations. Ad attribution works for every organisation.
Each entry point has a tracked link and a trigger phrase, the first message WhatsApp fills in for the contact. When a contact’s message matches the trigger phrase, ignoring capital letters and spaces at either end, Flowella links the conversation to the entry point. If the contact edits the message before sending it, the conversation isn’t linked. When the contact completes a Flow, Flowella writes link or qr to Flowella entry point. It doesn’t write the entry point’s name to HubSpot. To compare individual links and QR codes, use the counters on the Entry points page. See Entry points. For links in your emails, ads and social posts that lead to your website, use HubSpot’s tracking URLs with UTM parameters. When visitors arrive from a tracking URL, HubSpot saves the UTM details and shows them in its traffic analytics and sources report. See HubSpot’s guide to creating tracking URLs. Flowella doesn’t read or change HubSpot’s own source properties, such as Original Source. When WhatsApp is a follow-up channel, for example a workflow that sends a Flow after a website form, the contact keeps the source HubSpot recorded for that visit. A WhatsApp chat link (wa.me) opens WhatsApp, not your website, so HubSpot can’t see UTM parameters on it. To tag chats from your own wa.me links without entry points:
  1. Give each link its own prefilled first message. See Click-to-chat.
  2. In HubSpot, build a workflow that enrols on the Flowella Text Reply trigger.
  3. Branch on Last WhatsApp reply message, and set your own campaign property for each prefilled message.
Contacts can edit the prefilled message before they send it, so treat this as a best-effort signal. The ad click ID is more reliable, because contacts can’t remove it.

Report on attribution

Once these properties are on your contacts, you can report on them in HubSpot, for example contacts by Flowella entry point, or leads by Flowella ad id. See Reporting and dashboards.

Common questions

Flowella writes it when a contact completes a Flow, or when a contact messages you in a conversation that came from an ad. A contact who chats without completing a Flow, and didn’t come from an ad, has no value.
The ad may have run in WhatsApp Status, where Meta sends no click ID. Without a click ID, Flowella can’t link the conversation to the ad.
For ads, use Flowella ad id and match it to the ad in Meta Ads Manager. For links and QR codes, Flowella entry point only says link or qr. Use the counters on the Entry points page, or tag the prefilled message as described above.
Last modified on October 24, 2026