Skip to content

Capture UTM Parameters in Tawk.to and Connect Chats to Campaign Results

Traffic counts alone do not show which advertising work creates enquiries. When a visitor starts a Tawk.to chat, the useful question is which channel, campaign, and message brought that person to the site — and whether they later became a customer. Capturing attribution data with the chat makes that connection visible in the chat record, your CRM, or a reporting dashboard.

A four-step setup that survives browsing

A practical setup has four parts:

  • Install the attribution snippet on the website, using site settings or a tag manager such as Google Tag Manager, following the platform-specific instructions for WordPress, Wix, Squarespace, Netlify, or another platform in use.
  • Let the snippet record the visitor's arrival source and classify it into channels comparable to those used in Google Analytics, such as Paid Search, Organic Search, Paid Social, and Display.
  • Store that arrival data in the visitor's browser so it survives page-to-page browsing and a later return visit.
  • Attach the stored data automatically when a new Tawk.to chat begins.

The distinction matters because URL-only capture fails in a common journey: a person clicks a Facebook advertisement, lands on the homepage, reads several other pages, and only then opens a chat. By that point the UTM values may no longer appear in the address bar. Browser storage preserves the original arrival information for the chat event instead of depending on the final page URL.

What a chat record should show

Consider a visitor who arrives from a Facebook advertisement, browses the site, and starts a sales chat. The chat can carry a structured breakdown rather than a single raw source value:

  • Channel: Paid Social
  • Channel Drilldown 1: Facebook
  • Channel Drilldown 2: Brand Campaign
  • Channel Drilldown 3: TechHub Solutions

That hierarchy is more useful than an isolated UTM string. It lets a team answer progressively narrower questions: which broad channel worked, which network within it worked, and which campaign or brand activity produced the conversation. The same pattern can be applied to search traffic, where the drilldowns would instead identify the search network, campaign, and keyword where available.

Where to use the captured data

Once attribution data travels with each chat, there are three natural places to use it. First, agents can see the arrival context directly in the Tawk.to conversation, which helps them understand why the visitor may be asking a particular question. Second, the data can be sent to a CRM such as Salesforce, HubSpot, Pipedrive, or Zoho CRM, so leads and later customer outcomes can be reported against the original campaign; confirm which CRM connectors are available in your account before planning this step. Third, automation tools can route the same fields to Google Sheets or Excel, and from there to Looker Studio or Power BI for filtering, charts, and dashboards. A useful checklist before relying on the data is to test one paid-social visit, one paid-search visit, and one organic visit; browse to a second page before chatting; then confirm that the channel, drilldowns, UTM values, and click IDs appear correctly in the chat and in the destination system.

Why broader, cleaner attribution matters

Capturing every arrival, not only tagged advertising clicks, prevents a partial picture. Organic Search, Organic Social, and Direct Traffic can be recorded alongside Paid Search and Paid Social, so monthly reporting covers all leads rather than only the paid subset.

Cleaner categorisation also reduces manual work. Campaign tagging often drifts when several people or agencies manage accounts: the same search platform might appear as different raw source values. Automatic channel categorisation groups those variants under a consistent channel, such as Paid Search, making reports easier to compare over time.

Click IDs add another layer. Google Click ID, Facebook Click ID, and Microsoft Click ID can be passed with the chat, which supports offline conversion setup in advertising platforms when a lead or customer outcome needs to be sent back. Additional context — such as days from first visit to first chat and the number of visits before the conversation — helps distinguish immediate enquiries from considered journeys.

Four reports to build first

Four reports turn chat attribution into budget decisions:

  • Leads by Channel: compare monthly lead volume across Paid Search, Organic Search, Paid Social, and other channels. If organic search produces most leads while most spending sits in paid search, that imbalance is worth reviewing.
  • Leads by Meta Ads Network: separate Facebook, Instagram, Messenger, and other Meta placements to see which network creates enquiries, then concentrate spend where results are strongest.
  • Customers by Google Ads Campaign: count customers, not only chats, for each campaign. Brand, competitor, product, and service campaigns can then be funded according to realised customer value.
  • Revenue by Keyword: include the searched keyword in Google Ads UTM tagging through tracking templates, capture it with the chat, and use the resulting revenue view to decide where higher bids or greater impression share are justified.

Together, these views move reporting from clicks and visits toward leads, customers, and revenue.

Worked example — owner confirmation required

A worked example is most useful when it is built from verified details. A team could document the lead types it covered before implementation, the conversion points it connected afterwards, the dashboard or CRM fields it used, and the specific budget change and outcome that followed. Until those details are confirmed, no customer result is claimed here; the example remains a template for recording what actually happened.

Getting started

Start by installing the attribution snippet, running the three-visit test described above, and confirming that channel and drilldown fields arrive with a new chat. Then send those fields to the CRM or spreadsheet destination you actually use and build the leads-by-channel report first. That sequence gives a complete lead-source picture — paid and organic — and creates the foundation for campaign, network, keyword, customer, and revenue reporting. Check the current signup page for trial length and terms before you begin.