how to connect collect chat with google ads for conversion tracking
For Google Ads tracking, please see our guide here - https://collectchat.help.center/article/1022-google-analytics
Always happy to help 
Sibel from Collect.chat
Hi,
We implemented collect chat in our website. We can measure the times the bot was used, but we can’t connect the data to the right source. This is because it is an i-frame.
Is there a way to the right data in Google Ads and Analytics? Some workaround or different setup?
Kind regards,
Jeroen
I understand your frustration with the i-frame preventing proper source tracking in Google Ads and Analytics.
It’s a common challenge when a tool like Collect Chat is embedded in that way, as the i-frame creates a separate browsing context, making it hard for tools like Google Tag Manager (GTM) to read the necessary tracking information directly from the parent page or connect the bot’s interactions back to the user’s initial source (like a Google Ad click).
The link Sibel provided is helpful for general Google Analytics event tracking, but it often falls short when you need the granular, reliable, source-connected data required for effective Google Ads conversion tracking and bidding optimization.
You’re right that you need a workaround or a different setup.
While the Collect Chat API allows you to push event data (like a completed chat) to Google Analytics or Facebook Pixel, for accurate and robust Google Ads conversion tracking, particularly when dealing with i-frames and the increasing limitations of browser-side tracking, a server-side solution is much better.
A superior, future-proof solution involves using the Collect Chat Webhooks or API to send data to a server, and then using that server data to communicate directly with the Google Ads API.
You can achieve this by setting up a server-side tracking infrastructure.
This typically involves using the Collect Chat API to send the conversion event data, along with necessary user and source identifiers, to a service like Stape or your own Google Cloud Platform environment.
From there, you use a server-side instance of Google Tag Manager to process this data and send it directly to Google Ads using the Google Ads API, often leveraging the Google Tag Manager server container’s ability to create more reliable and consistent user identifiers.
This method bypasses the i-frame issues and the limitations of client-side tracking, ensuring your conversions are attributed correctly to the original Google Ads click source, which is critical for optimization.
This server-side approach allows you to send richer data to Google Ads, including user details for enhanced conversions, which significantly improves match rates and campaign performance.
The Collect Chat API allows you to push data about specific user actions, which you can use to define your most valuable conversion events, such as a lead submission or a specific step completion, and track these as standard events like ‘lead’ or ‘purchase’ via the server.
While it involves a bit more initial setup, integrating the Collect Chat API with Google Tag Manager server-side and a platform like Stape or Google Cloud Platform gives you the control and accuracy you need to reliably connect the bot usage to the correct source in both Google Ads and Google Analytics.