Google Ads Conversion Tracking Checklist for Germany

SS
Shihabus Sakib
October 06, 2026
  • 9 mins read
Marketing colleagues reviewing website enquiry tracking on a laptop.
In this article

Before using Google Ads conversion figures to change your budget, check five things: what counts as a conversion, where the data comes from, whether enquiries are missing or counted twice, how tracking responds to consent, and whether the results match meaningful business outcomes.

This Google Ads conversion tracking checklist is for small-business owners and marketing staff running enquiry-generating campaigns in Germany. It helps you assess an existing setup and identify what needs attention. Technical checks alone do not establish that the underlying data processing is lawful.

Consider a small IT support company whose advertising report shows more conversions than its team can match to enquiries. Before increasing spending, the owner needs to understand that difference. A faulty trigger could explain it, but reporting settings may also be responsible. Reliable conversion measurement helps you connect advertising decisions with your broader digital marketing strategy.

Define the Business Action You Need to Measure

Start by writing down exactly what each conversion represents. For an enquiry campaign, a successfully received contact form is different from a click on the “Submit” button.

A conversion is an action configured for measurement in Google Ads. Its name should describe the outcome accurately. “Completed enquiry” should mean the form was accepted successfully, rather than opened, attempted or rejected because a required field was missing.

For the hypothetical IT company, distinguish between:

  • An interaction: someone opens the contact form.
  • A completed enquiry: the website successfully receives the submission.
  • A qualified enquiry: the team confirms that the request fits its services and intended customers.

These actions answer different business questions. Measuring them separately can be useful, but a form opening should not automatically carry the same weight as a completed enquiry.

Ask whoever manages the website to confirm the trigger: the condition that causes the measurement code to run. If the trigger only detects a button click, request evidence that it distinguishes successful submissions from failed attempts.

Check the Conversion Source and Bidding Settings

Identify how each action reaches Google Ads and whether the campaign uses it to guide bidding. An action’s name does not reveal either.

Identify Google Ads and GA4 Measurement Sources

The tools have different responsibilities:

Tool Role in your measurement setup
Google Ads Reports advertising conversions and uses selected conversion goals for automated bidding.
Google Analytics 4, or GA4 Measures website and app activity. Relevant events can be used to create Google Ads conversions.
Google Tag Manager Manages measurement tags and the triggers that activate them.


Google explains how to
create Ads conversions from Analytics events. Check whether your enquiry is measured through a direct Ads conversion tag, an Analytics-derived conversion, or both. 

Using both routes does not automatically create a problem. Investigate whether separate conversion actions represent the same enquiry and unintentionally contribute to the total or bidding goals you rely on.

Request a simple record of each action’s name, source, trigger and purpose. This gives you more useful evidence than a screenshot showing only the overall conversion total.

Review Primary and Secondary Conversion Actions

Primary actions normally contribute to the “Conversions” column and are eligible for bidding when the campaign uses their associated goal. Secondary actions normally appear in “All conversions” for observation.

There is an important exception: actions included in a custom goal can be used for bidding even when marked secondary. Review the campaign’s selected goals alongside each action’s classification, following Google’s conversion-goal guidance. 

For an enquiry campaign, check whether contact-page views or form openings have accidentally become bidding outcomes alongside completed enquiries. The selected goals should reflect the business result you want the campaign to produce.

Test for Missing and Duplicate Enquiries

Test the form journey itself. A tag being installed does not show that its trigger matches a completed enquiry.

Use identifiable test details so your team can separate test submissions from genuine prospects:

  1. Ask the implementation owner to open the relevant debugging tools.
  2. Submit an incomplete form and record which events run.
  3. Submit a valid form and confirm that the business receives it.
  4. Reload or revisit the confirmation page.
  5. Record the results and any changes required.

First test the form under the relevant consent state. Then repeat the necessary journeys with different consent choices, as explained in the next section.

Test action What to check What the finding could mean
Submit an incomplete form Does the completed-enquiry event run despite a validation error? The trigger may measure an attempted submission.
Submit a valid enquiry Does the intended event run, and does the business receive the enquiry? Missing measurement and missing delivery require separate investigation.
Reload or revisit the confirmation page. Does the same completed enquiry trigger another event? Repeat-event protection may need review.
Inspect conversion actions. Do separate actions represent the same enquiry? Reporting or bidding may include overlapping outcomes.


Four checks for failed submissions, successful enquiries, repeat events and overlapping conversion actions.


The aim is to establish a dependable relationship between a completed enquiry and its measurement. Investigate triggers that record failed submissions or repeatedly record the same outcome.

Also review the action’s conversion counting setting. “One” counts one conversion per ad interaction for that action; “Every” counts each conversion. “One” can suit lead generation, but it is not a system for identifying unique people or removing duplicates across different actions. 

Where supported and appropriate, a unique transaction ID can help prevent duplicate recording within the same conversion action. Google’s transaction ID guidance explains the mechanism. It does not merge different conversion actions, and the ID must not contain information that identifies a customer. 

Verify How Tracking Responds to Consent

Review the applicable requirements and test the actual data flow. The appearance of a cookie banner does not establish that measurement follows the visitor’s choice.

In Germany, § 25 TDDDG generally requires consent before storing information on, or accessing information from, a user’s device. Its exceptions concern transmission over a public telecommunications network and operations strictly necessary to provide a digital service expressly requested by the user. Advertising measurement should not be treated as exempt simply because the business finds it useful. Einzelnorm

Processing personal data also requires a separate GDPR assessment. Where consent is relied upon, the European Data Protection Board’s consent guidelines explain requirements, including freely given, specific, informed and unambiguous consent, with withdrawal as easy as giving consent. 

Google’s EU user consent policy imposes separate requirements for covered products and users. These include obtaining the specified consent, retaining consent records and providing clear revocation instructions. Platform policy should be assessed alongside the applicable law. 

Assign responsibility for checking the wider marketing privacy requirements, including privacy information, vendor arrangements and international transfers. These questions extend beyond whether a conversion tag works.

Understand Basic and Advanced Consent Mode

Consent Mode communicates consent choices to Google tags and adjusts their behaviour. It does not obtain valid consent itself.

Google’s Consent Mode documentation distinguishes two implementations:


Basic Consent Mode blocks Google tags before consent; advanced mode can send cookieless pings with denied defaults.

“No advertising cookies” therefore does not necessarily mean “no information sent to Google”. Google’s documentation describes technical behaviour; it does not determine whether your particular implementation is lawful.

Ask the implementation owner which approach is used and what information leaves the website before acceptance, after rejection and after acceptance.

Test Acceptance, Rejection and Withdrawal

Use fresh browser sessions or reset stored consent between tests. Check:

  • No interaction with the banner.
  • Rejection of optional purposes.
  • Acceptance of the relevant purposes.
  • Partial acceptance.
  • Withdrawal after previously granting consent.

Google’s Tag Assistant consent-debugging guidance explains how to inspect default states and subsequent updates. Ask the tester to check that defaults are established before relevant tags run and that choices update the intended settings.

Inspect stored information and network requests as well. Network requests are the browser’s communications with external services. Compare observed behaviour with the documented implementation and its privacy assessment.

As practical quality control, keep a dated record of the findings, responsible person and required fixes. Repeat relevant tests after changes to forms, tags, consent settings or website plugins.

Reconcile Reported Conversions with Business Records

Compare equivalent figures before diagnosing a tracking failure.

A successful Tag Assistant test provides evidence about technical behaviour during that journey. Whether an outcome appears as a Google Ads conversion also depends on the relevant advertising interaction, attribution and conversion settings.

Google Ads and GA4 can report different totals. Google’s Analytics-to-Ads guidance describes differences involving counting and attribution. For example, two analytics lead-form key events may produce one imported ads conversion when the action uses the “One” setting. 

When comparing reports, check:

  • The specific conversion action and reporting column.
  • The counting method.
  • Date ranges, time zones and reporting delays.
  • Attribution settings and how conversion dates are reported.

Attribution means assigning credit for an outcome to marketing interactions. Modelled conversion figures also cannot necessarily be matched individually to enquiries in your inbox.

Then assess enquiry quality separately. For the hypothetical IT company, a genuine home-computer repair request might be measured correctly but fall outside a campaign seeking business support contracts. That finding calls for a targeting or messaging review.

Distinguish three possible findings:

Finding Appropriate next step
The recorded event does not match a completed enquiry Review the trigger and implementation.
Reports use different counting or attribution methods Explain the difference before changing tracking.
Enquiries are genuine but unsuitable Review targeting, advertising messages and landing-page content.

Resolve unexplained discrepancies before treating a rising conversion total as evidence that a larger budget is justified.

Build the Skills to Assess Your Tracking

Business owners and marketing staff responsible for measurement may find GCI’s Certified Digital Marketing Specialist (SEO, SEM & Analytics) relevant. Its published curriculum includes measurement strategy, GA4, tag management, data accuracy, and cookies, tracking, and consent management. These topics relate directly to assessing reports and discussing findings with your implementation team. 

Review the course syllabus to check whether its coverage matches your responsibilities and knowledge gaps. Confirm the teaching language before enrolling: the page lists German/English while also specifying good German language skills. Completing the course does not, by itself, validate your tracking setup.

Frequently Asked Questions

01 Does hashing customer data make enhanced conversions anonymous? +

Do not assume that it does. Hashing transforms information into a coded value, but enhanced conversions use hashed customer data for matching. Google’s enhanced-conversions guidance describes how first-party customer information supplements conversion measurement. Before enabling the feature, assess the data, purpose, disclosures and applicable permissions. Using first-party customer data responsibly requires attention to how information is collected and reused, even when its format changes.

02 Do I need server-side tracking before checking my conversions? +

No. Start by checking your existing conversion definitions, sources, triggers and consent behaviour. Server-side tracking is a separate implementation decision and does not remove privacy obligations.

03 What should I request from my agency for a tracking review? +

Request a list of conversion actions showing their sources, triggers, counting settings and use in bidding. Also ask for test results covering successful and failed form submissions and different consent choices.The records should identify when testing took place, what problems were found and who is responsible for any corrections.

04 Can I test conversion tracking before launching a campaign? +

Yes. You can test whether the form works, the intended events run and tags respond to consent choices before advertising begins.However, a functional test does not prove that Google Ads will attribute a future conversion to an advertising interaction. That requires a relevant advertising interaction and subsequent processing.

05 Does clicking a telephone number count as an actual enquiry? +

A telephone-number click initially shows that someone activated the calling link. It does not confirm that a call connected or that a relevant conversation took place. If you measure these clicks, name the action accordingly. Keep them distinct from received or qualified enquiries when reviewing campaign results.

06 What should I retest after changing a contact form? +

Repeat the tests for incomplete and successful submissions. Confirm that the business receives the enquiry, the intended event runs and revisiting the confirmation page does not unexpectedly record the same outcome again. If tags or their loading sequence have changed, also test the relevant consent choices. Record the date and findings of the review.

07 Does a low conversion total necessarily indicate a tracking error? +

No. A low total may reflect fewer people completing the intended action. Consent choices, counting methods and processing delays can also affect the results shown. First check whether the measurement works technically. Then compare recorded results with actual enquiries before concluding that the problem lies with tracking or campaign performance.

Here your growth begins.

Unleash your potential. Learn anytime, anywhere.