Capture Google Ads Data in Tawk.co Chats
Website traffic alone does not show which paid campaigns create enquiries. By tagging ad URLs, remembering the visit, and attaching that context to each chat, you can connect a Tawk.co conversation to the campaign, ad group, and ad that started the journey.
Tag ads with a consistent UTM pattern
Tag every paid destination consistently before traffic arrives. UTM parameters are short URL suffixes that identify the medium, source, campaign, ad group, and individual ad. A consistent naming pattern matters more than the exact labels, because later reports group records by those values.
Use paidsearch for the medium and google for the source. Put the campaign name in the campaign field, the ad group name in the term field, and the specific ad in the content field. Keep spelling, spacing, and capitalisation consistent across campaigns so similar names do not split one campaign into several report rows.
Install the snippet and preserve first-touch context
Install the attribution snippet on the site, either directly through the platform's custom-code or scripts area or through a tag manager. Once active, the tool records the first-touch context and retains it while the visitor moves between pages.
That persistence is the key distinction from a one-page check. A visitor may click an ad, read several pages, and only then open chat. The chat should still carry the original campaign context rather than appearing as an unattributed direct visit.
Attach attribution and landing-page context to each chat
When a visitor opens the embedded chat widget, the attribution values travel with the conversation. In a home-cleaning example, a spring-cleaning campaign could arrive as Paid Search, Google, the campaign name, and the specific window-and-carpet ad. That chain lets a marketer distinguish a campaign that produced a chat from one that only produced a page view.
The same record can also include the landing page and its broader page group. For example, a commercial window-cleaning page can be reported both as a full URL and as part of the services section, making it easier to compare individual pages with whole site sections.
Turn chat context into decisions
Review the context inside the chat tool, send it to a CRM for dashboards, or export it for spreadsheet and business-intelligence reporting. The useful question is not simply how many chats occurred, but which source produced each one and whether those chats became customers.
Three practical reports follow from that structure. Leads by channel compare volume across paid search, organic search, social, and other sources. Customers by Google Ads campaign show which campaigns create paying customers rather than clicks. Revenue by keyword links bidding terms to the revenue those visitors eventually generate. Together, they help shift budget away from inexpensive visits that never convert and toward campaigns that produce valuable enquiries.
Check the full journey before trusting reports
Do not limit the setup to paid search. The same mechanism can record social, organic, referral, and other first-touch sources, giving one consistent view of chat-lead origin. Before relying on the data, test a tagged ad click, browse to another page, start a chat, and confirm that the channel, campaign, ad, landing page, and page group all appear correctly in the destination system.
| Field | Recommended value or meaning |
|---|---|
| UTM Medium | paidsearch |
| UTM Source | |
| UTM Campaign | Google Ads campaign name |
| UTM Term | Ad group name |
| UTM Content | Specific ad |
Naming pattern from the captured guide; keep values consistent across campaigns.