Routeless has implemented Google Ads conversion tagging and paid-media reporting pipelines, not a custom direct Google Ads API client or generative ad-creative system. Verified work includes Google Ads conversion configuration on Routeless landing pages and Funnel-delivered Google Ads data modeled in BigQuery and dbt. The page documents that boundary so reporting evidence is not misrepresented as campaign mutation.
Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28
Routeless contains Google Ads conversion tagging, while a separate marketing-data platform contains managed Google Ads exports, BigQuery permissions, dbt staging models, client marts, and reporting services.
The evidence supports conversion measurement and reporting integration only. It explicitly does not support direct Google Ads API development, campaign deployment, offline conversion upload, or generative creative claims.
A paid landing surface loads the Google tag and sends a configured conversion event after the defined website action.
Evidence: Verified in Routeless landing templates, analytics loader, and conversion-event scripts.
A managed Funnel export writes Google Ads campaign data to client-specific BigQuery datasets with infrastructure-defined permissions and schedules.
Evidence: Verified in the marketing-data platform's Terraform client and export modules.
dbt staging models normalize the exported fields, then campaign marts feed authenticated reporting views without exposing warehouse credentials to the browser.
Evidence: Verified in the Google Ads staging models, client marts, and BigQuery analytics service.
Conversion tags use a public Google Ads conversion identifier in the browser. Reporting data is delivered through a managed connector into restricted BigQuery datasets, where service-account and warehouse permissions remain separate from website code.
Public conversion IDs remain in page configuration because browsers need them. Managed connector and BigQuery credentials are restricted to infrastructure and server processes. Client datasets and service accounts are separated by deployment configuration.
Website events degrade without blocking the user flow when analytics is unavailable. Data exports and warehouse transformations expose failed schedules or model runs separately from the site. Reporting must retain the latest completed data window rather than presenting an interrupted load as current.
Website conversion surfaces with optional Google Ads conversion configuration and locked analytics event contracts.
Managed Google Ads exports modeled in BigQuery and dbt for authenticated reporting.
The audited evidence does not show a custom direct Google Ads API client. Routeless has implemented conversion tagging and Google Ads reporting data delivered through a managed connector into BigQuery and dbt.
Yes. The verified pattern lands managed Google Ads exports in client-specific BigQuery datasets, normalizes them with dbt, and serves the modeled data to authenticated reporting.
No verified repository evidence supports that claim. Creative generation, asset approval, and campaign mutation would need a separately scoped and evidenced implementation.
Not on its own. A tag records the configured website event. Revenue attribution needs transaction or CRM data, deduplication rules, consent-aware identifiers, and an agreed attribution model.
Google Ads reporting official site. The Google Ads reporting name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.
Share the account access, records, expected events, and the workflow that must recover when delivery fails.