Google Ads Telegram tracking, from click to deposit
See which Google campaigns produce Telegram members and depositors, and send those deposits back to Google Ads so bidding can optimise for revenue rather than clicks.
See which Google campaigns produce Telegram members and depositors, and send those deposits back to Google Ads so bidding can optimise for revenue rather than clicks.
Google Ads sees the click and, with a tag on your site, what happens on your pages. When a visitor leaves for a Telegram channel, group or bot, the join, the conversation and the deposit that follows days later all happen where no Google tag can run. In Google Ads, a campaign that brings 50 depositors and one that brings none can look the same.
That matters most for Smart Bidding, which learns from the conversions it receives. If the only conversion Google records is a button tap, bidding finds more people who tap buttons. Closing the gap takes two things: a record of what each Google click turned into inside Telegram, and a way to return the deposits to Google Ads against the click that produced them.
For Meta and TikTok, an ad can point straight at a Tellmetric tracking link. For Google Ads, it should not. An ad whose final URL only redirects to Telegram risks disapproval for a destination mismatch, so Google traffic should land on a page on your own domain, with the Tellmetric snippet installed and the Telegram buttons pointing at your tracking links.
On page load the snippet reads the Google click id and the UTM parameters from the address, records the visit, and adds them to every tracking link on the page. When the visitor taps a Telegram button, the click is recorded with everything the ad passed along. Plain t.me links are counted as interest only, unless you set the snippet to route them through a tracking link.
Google adds one of three click identifiers to the landing page address. Tellmetric stores whichever one arrives, and it is the identifier that lets Google match a deposit to its click later:
To report below the level of the click id, the address also needs the campaign, ad group and ad. The Links page gives you a line for the Final URL suffix in your Google Ads campaign settings. Google replaces the curly parts with its own values on every click:
utm_source=google, so Google traffic is separated from other sourcesg_campaign_id, g_adgroup_id and g_ad_id, filled from {campaignid}, {adgroupid} and {creative}{network}Every join, message and deposit inherits these values from its click.
The tracking link opens your Telegram group, channel or bot, and your bot ties the person who joins or writes to the click. The deposit comes from wherever you take payments: a postback from your platform or tracker, a call to the event API from your backend, a hosted form, or a Telegram Stars payment in the bot. Each is recorded as an event with the original click's attribution, including the Google click id. How to track Telegram deposits covers the four options in detail.
On Pro and Agency, Tellmetric uploads deposits to Google Ads as offline conversions. The Free plan reports to Meta only. Uploads go through Google's Data Manager API, which needs no developer token on your side: you grant permission once when connecting, and Tellmetric keeps the saved sign-in encrypted.
customers/1234567890/conversionActions/987654321.Only deposits are uploaded. Events named Deposit, FTD and Purchase become Google conversions; joins, messages and leads stay in your Tellmetric reports and are not sent to Google. A background worker checks for new deposits every 30 seconds and sends them in batches. Each conversion carries:
The hashed email and phone are for enhanced conversions, which help Google match the conversion to a signed-in user. If the ad account has not accepted Google's customer data terms, Google refuses them; Tellmetric then uploads the same conversions without them and shows where to accept the terms (Goals, Conversions, Settings, Customer data).
Google rejects a conversion whose click is less than six hours old. Tellmetric holds such deposits back and uploads them on a later run, once six hours have passed since the click.
A deposit can only go to Google if its click carried a Google click id. Deposits from Meta, TikTok or other traffic, or from visitors who reached your page without a click id, are marked as skipped for Google with the reason, and they are not retried. They still appear in your reports, credited to their own source.
The worker looks back over deposits recorded in the last three days. Connect Google Ads before the traffic you want reported starts, since deposits older than that are not uploaded when you connect later.
Test mode is on for a new connection. Every upload is sent as a validation request: Google checks the account, the conversion action and each conversion, and answers as it would for a real upload, but records nothing. The deposit's details show Google's answer, so you can confirm the ids and the payload before anything counts.
When you turn Test mode off, deposits from the last three days that were only validated are uploaded for real on the next run. If an upload fails, the error is shown on the Google Ads page, and failed deposits can be put back in the queue from there.
The same connection is used to import Google Ads spend. Tellmetric reads daily cost per campaign and ad group, plus campaign-level cost that no ad group carries, such as Performance Max, so the rows add up to Google's campaign cost. The time of the last import, or its error, is shown under the Google Ads form.
Spend is joined to your results when you group the funnel table by Google campaign (id) or Google ad group (id), or by campaign name when your utm_campaign values match Google's campaign names. Rows then show spend, cost per join, cost per deposit and return on ad spend. Google spend has no country breakdown, and spend in different currencies is added as it is, so keep deposits and ad accounts in one currency.
The Google Ads page under Ad accounts adds a campaigns table per Google campaign id, with spend, cost per join, cost per deposit and return on ad spend once spend has been imported.
Tellmetric counts every deposit matched to a click, from any source. Google Ads counts the conversions it accepted, credits them under its own attribution settings, and reports them against the date of the click. Deposits without a Google click id never reach Google. Expect the totals to differ. Use Tellmetric to decide which campaigns produce revenue, and Google Ads to see what bidding is learning from.
Illustrative figures. A search campaign and a Performance Max campaign each spend €800 on the same landing page and report a similar number of button taps. Search brings 30 deposits, Performance Max 18. On cost per deposit, search costs about €27 and Performance Max about €44. Once deposits are uploaded, each campaign's bidding works from the outcome you are paid for.
gclid from the address before the snippet reads it.t.me address instead of a landing page with the snippett.me directly, so the click never reaches a tracking linkNo. Conversions go through the Data Manager API with the permission you grant when connecting, and spend is imported over the same connection.
Pro and Agency. The Free plan reports to Meta only.
No. Only deposits, recorded as Deposit, FTD or Purchase, are uploaded. Joins and messages are reported in Tellmetric by Google campaign, ad group and ad.
It is marked as skipped for Google with the reason and not retried. It still counts in your reports, under the source that brought it.
If the saved sign-in expires or its access is removed, uploads stop, the Google Ads page shows a notice and offers Connect Google Ads again. Uploads resume after you reconnect.
The Free plan requires no card. Upgrade to Pro at any time.