How to Install Google Ads Conversion Tracking Correctly in 2026

A Google Ads account can look busy while the inbox stays quiet, or the inbox fills while Ads shows no conversion. Both are conversion tracking, not a bid. This is how to install it in 2026 with GA4, Google Ads, and Tag Manager, so a Thai lead form or a LINE click is counted once, after it happens.

This is a working note, not a service page. It does not quote a fee or a return. The page for the ads work is our Google Ads services page.

Short answer: Count an enquiry you can answer: a form that arrived, a call you can trace, or a LINE click on the button the ad was written for. Do not count a page view, a footer icon, or a failed submit. Do not stack a Google Ads tag and a GA4 import on the same event. Test on a phone, in Thai and in English, before you trust the dashboard. Digital Agency Bangkok can hold the account and the container as one brief. This article will not invent a figure for it.

What you are counting, before you install anything

Write the conversion in a sentence sales would accept. A Thai form on the landing URL submitted, and the row is in the inbox. The LINE button on that URL opened the official account you staff. A call came from the number on that page, not the footer on every post. If you cannot write the sentence, do not create the action. Bidding follows the primary. A vague action teaches the wrong lesson.

Ads, GA4, and the inbox are three lists. They will not match by themselves. Name one primary action. Keep form starts, scrolls, and button views as observations. Do not add those rows and call the total leads. Do not invent a conversion value. Leave value blank, or use a value sales already uses.

GA4, Google Ads, and Tag Manager: one job each

GA4 records what happened on the site. Google Ads decides what counts for bidding. Tag Manager fires the tags. You need the container when success never changes the URL. A Google tag in the theme is enough only if success opens a page nothing else links to. It fails when the form stays put and only shows a success line.

Link the GA4 property to the Ads account. In Tag Manager, include Conversion Linker so the ad click can be tied to the later event. Create the Ads conversion for the enquiry you named. Fire it on that event only, or import the same GA4 key event once. Not both. If the theme also pastes the same snippet, remove one copy. Name who can publish the container. If that person cannot edit the form, or the reverse, the next edit will drop the event.

Install order, without a fake score

Work on the URL the ad uses. The form or LINE button must be the real one, and a test must reach a person. If the page cannot finish the enquiry, a tag cannot repair it. That is a landing-page problem, on landing page design. A page that stalls or hides the next step makes the click expensive first. That sits next to an old website makes ads more expensive.

1. Name the primary conversion in one sentence, for Thai and for English if both ads exist.
2. On a phone, finish the form, the call, or the LINE open, in that language.
3. See whether the URL changes, or only a message appears. That chooses a thank-you pageview or a success event.
4. Send the Ads conversion through one container or one Google tag. Do not import the same event and mark both primary.
5. Test the Thai URL and the English URL. An English-only label will miss the Thai form.
6. After publish, submit once. You want one conversion, and sales should recognise the test and discard it.

A status of “recording” is not proof. The thank-you URL may have been opened from a bookmark.

Mistakes that inflate a Thai lead form

The tag often fires too early. The form is shown. Submit is clicked, including when validation fails. The thank-you page is in the menu or in search, so a pageview counts without a form. A shared button class counts the control that only opens the form.

On Thai sites the same mistake has familiar shapes. A popup and the page form share an event name, so one submit is two conversions. An English success tag copied onto the Thai page also fires on the language switch. A field fails on a phone, the person tries twice, and every click is counted. Staff tests stay in the report. A chat widget “submits,” and that event is imported as the lead form.

Counting every conversion does this quietly. Sending again after fixing a phone number is not two leads. One per ad click is the usual form setting, unless you have written a reason to count every. Do not add the form tag, the thank-you pageview, and a GA4 import of the same submit. Enhanced conversions are not a second conversion. If the form has no notice about email or phone data, do not turn them on to fill the report.

Mistakes that miss the form, or a LINE click

The usual miss is the opposite trigger. The container waits for a thank-you URL. The Thai form never goes there. It stays on the landing page and shows a success line. The person is in the inbox. Ads is empty. That is not a failed campaign until you have tested the path.

Other misses: the tag is only in the English header; the trigger wants an English label; the form plugin changed the success event and the container was not published; a consent banner holds the tag while the CRM fills; an in-app browser drops the click id. Do not invent how often that happens. Test one Thai submit from a phone, including the LINE browser, and write whether one conversion appeared.

LINE is often the real lead, and a click is not a chat. If sales judge the week by chats they answered, a button click will look better than the week felt. Do not hide that gap with a number you do not have. The footer, a desktop QR, and any URL that merely contains “line” are not the conversion. Limit the trigger to the button on the landing URL, and to the official account staff answer. A picture, a QR with no link, an iframe, or a second account the tag ignores will miss. If the button cannot be measured, ask sales which chats arrived. Do not add LINE clicks and form submits until you know they are not the same person.

Language, the thank-you page, and the phone

Thai and English are two pages. The Thai ad should land on the Thai URL. The form should succeed in Thai, including the errors. The trigger should listen on that URL. If English thank-you is one address and Thai success is another path, or only a message, one pageview rule will miss one language or count the wrong visits on the other.

Open the thank-you URL without sending the form. If it loads, a pageview is not a lead. Unlink it and prefer a success event. Test on a phone. A form that works on a laptop and fails a field there is a page miss. Call the number. Open LINE. Fix the page before you add budget.

How to test, then what to ask

Preview the landing URL, then repeat without preview. Submit a form sales can recognise and note the time. Check the inbox, GA4, and Ads. You want one of each. Two conversions means a double fire. None in Ads, with a row in the inbox, means a miss. A conversion with no row means inflation. Repeat for LINE and the other language. Until real enquiries match the inbox, do not treat the ads report as verified.

Ask whoever holds the account, including us. What is the primary conversion, in one sentence, for Thai and for English? Does it fire on success, on the click, or on a page view? Is the same event also imported from GA4 and marked primary? Can thank-you open without a submit, and is LINE limited to the landing button? Who publishes the container, and who checks the inbox? If the first answers are unclear, do not raise the bid. A larger budget on a wrong primary buys more of the wrong thing. The page for that work remains Google Ads services.

What this article will not do

• Invent a conversion rate, a cost per lead, a Quality Score, or a share of clicks that failed.
• Quote a fee for ads, tracking, or a landing page. Those figures, if published, live on the service pages.
• Name other firms, or place them in an order.
• Treat a LINE click as a chat, or a form view as a lead.
• Treat a screenshot of a tag list as proof. The test is the test.