Measurement: settings and routing evidence

What the scan really checks

Open Results → Measurement in Simple view, Campaigns → Measurement in Expert view, or /measurement. Select the advertiser and choose Scan conversion settings.

The scan reads the effective conversion account, enabled/non-removed conversion actions, non-removed Search campaigns, campaign conversion goals, goal configuration, and custom goals. It flags configurations such as no eligible enabled action, secondary actions included by custom goals, and page-view or engagement actions selected for optimization.

A primary action can be eligible through a biddable campaign goal; a custom goal can also select a secondary action. Eligibility describes settings, not observed auction behavior.

Why settings cannot prove tracking

Tag firing happens in the visitor browser or server tagging system. Entryway does not currently run a browser/tag inspection session on your website.

Consent behavior depends on the visitor state, consent banner, region, and implementation. This scanner does not exercise those combinations.

Lead delivery requires evidence from the form or call provider, destination, CRM, and pipeline. Google Ads settings do not provide that full path.

Attribution reconciliation requires comparable event identifiers, dates, lookback windows, source records, and delay handling. A configured conversion action alone cannot prove a particular lead was attributed correctly.

Actual bidding outcomes also depend on bidding strategy, serving eligibility, budgets, learning, and auctions. The app can inspect selected goal settings but cannot infer hidden auction decisions from them. These checks can be expanded with separate integrations and tests; they are not impossible, just not delivered by this scan.

Reading the result

Use the capture time and per-inventory coverage. Complete means the bounded configuration query completed, not that tracking is healthy. Limited or unavailable means some evidence is missing; it is not a clean bill of health.

Each inventory is capped at 1,000 rows or three pages. Scans exceeding the saved-evidence size limit fail instead of saving an apparently complete result. The library shows the latest 30 scans. Export configuration produces a CSV with the configuration-only limitation.

The scanner performs Google reads and saves evidence. It does not change conversion settings or consume AI inference tokens.

Record a routing test

Start from a saved scan and choose its campaign and enabled conversion action. Name the test, choose form/call, and record the intended location and destination.

Use the synthetic reference in an approved external test environment. Check consent/test setup, event and deduplication, destination, CRM record, pipeline, and conversion return. Entryway does not submit forms or place calls for you.

For each pass or failure, record a note, evidence reference, and observation time. Avoid storing personal lead details in notes; use a restricted external receipt or test-record reference. Only conversion return can be marked outside scope.

Corrections add a new revision. A failed step keeps the run unresolved. Passed · manually recorded means a person recorded the evidence, not that Entryway independently verified it. Synthetic tests remain separate from business-outcome totals; exclude test activity in external systems as well.

Tools for deeper checking

Use Google Tag Assistant to inspect tag and consent behavior, and compare synthetic receipts with the destination/CRM system. A successful test is evidence for the tested conditions, not every visitor or future deployment. Never upload a synthetic lead as a real advertising conversion.