Skip to content

Capture Google Ads Data in Zoho Sales IQ Chats

Website analytics can show visits, but it does not always show which visits became chats, leads, or customers. Attaching campaign information to each Zoho Sales IQ conversation closes that gap: when a chat starts, the team can see which ad, campaign, and landing page brought the visitor to the site.

Set up the data flow in four steps

Start with consistent tagging. Add UTM parameters to each Google Ads destination URL so the campaign, ad group, and ad can be identified later. A practical convention is paidsearch for medium, google for source, the campaign name for campaign, the ad group name for term, and the specific ad for content. The exact values are flexible, but consistency matters more than the labels themselves.

Next, place the attribution code on the website through the site builder's settings or custom-code area, or through a tag manager when that is the site's script-management method. Once active, the code records the visitor's origin and keeps that information available as the visitor moves between pages.

When the visitor opens the embedded Zoho Sales IQ widget, the recorded origin information is passed with the chat. In addition to campaign fields, the first landing page and its broader page group can be retained. That distinction helps teams separate two questions: which campaign created the conversation, and which part of the website the visitor entered through.

After capture, the information can be viewed beside the chat, forwarded to a CRM for reporting, exported for spreadsheet analysis, or connected to a dashboard tool. The workflow therefore supports both immediate sales context and later marketing analysis.

Worked example: from ad click to chat

Consider a managed IT support provider advertising a free consultation. A business owner clicks the consultation ad, browses several service pages, and then starts a chat. The captured record should identify paid search as the channel, Google as the source, the managed IT campaign, and the consultation ad. It should also preserve the service page where the visit began.

That single record lets the sales team understand the context of the conversation and lets marketing compare the result with other campaigns. Without the retained fields, the chat may look like an untagged direct conversation even though the visitor arrived from a paid campaign several pages earlier.

Checks and reports to run after setup

Use this checklist before relying on campaign reports:

  • Confirm every Google Ads URL uses the same UTM naming convention.
  • Verify that the attribution code loads on the pages containing the chat widget.
  • Start a test chat from a tagged campaign URL and inspect the fields stored with it.
  • Browse to another page before starting a second test chat to confirm the original campaign information remains attached.
  • Check that the landing page and landing-page group are populated.
  • Confirm the fields appear in Zoho Sales IQ and in any CRM, spreadsheet, or dashboard destination.
  • Test an untagged visit as well, because the same process should record non-Google-Ads origins such as organic search, social posts, and other advertising channels.

Three reports are especially useful once the data is flowing. Leads by channel compares volume across paid search, organic search, social, and other sources. Customers by Google Ads campaign shows which campaigns produce paying customers rather than only enquiries. Revenue by keyword connects closed revenue to the search term associated with the visit, making it easier to review bids and budget allocation.