Content Moved? Use Search to Locate
Business professionals discussing data charts and graphs in a modern office setting.

Google Ads Enhanced Conversions: Audit Data Sources Before Bidding

Google Ads is simplifying enhanced conversions, but the underlying measurement workflow may be getting harder to govern.

Starting in April 2026, Google Ads began accepting user-provided data simultaneously from website tags, Data Manager, and API connections. Starting in June 2026, enhanced conversions for web and enhanced conversions for leads began moving to one unified on/off setting instead of separate implementation-method choices. Google also states that offline conversion imports and enhanced-conversion-for-leads uploads moved to the Data Manager API beginning June 15, 2026, with those uploads blocked in the Google Ads API for affected legacy workflows.

The interface may be simpler. Your data architecture may not be. Before changing a conversion action, campaign, or Smart Bidding input, document every system that sends, transforms, imports, or receives conversion data.

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

Why the data map matters

Google’s unified setting does not mean a business has only one source of conversion data. A typical WordPress or WooCommerce account may involve:

  • Google tag or Google Tag Manager containers
  • WordPress, WooCommerce, form, or checkout plugins
  • Google Ads Data Manager connections
  • Google Ads API or approved third-party integrations
  • CRM, marketing-automation, HubSpot, Zapier, or similar workflows
  • Scheduled offline conversion imports and spreadsheet-based processes

Some of these are direct Google data sources. Others are upstream systems that capture, enrich, or pass customer data into an import workflow. The operational question is the same: who owns each conversion event, and how does Google receive it?

A website form submission and a later qualified-lead or closed-sale import can be intentionally different conversion events. Problems arise when the same lead or transaction is sent through multiple paths without a documented event definition, identifier, or duplicate-prevention method. That can make Google Ads totals difficult to reconcile with the CRM, payment system, or backend order records.

For each conversion action, record the system of record, destination, primary or secondary bidding status, event name, conversion value, currency, timestamp, and duplicate-control method. Preserve GCLIDs where available. For lead workflows, also document which first-party fields are collected, normalized, hashed, and sent, and whether the same data is used in both website and offline workflows.

Enhanced conversions use hashed first-party customer data to improve matching potential. They do not guarantee that every conversion will be attributed. The data remains customer data, so the implementation should be reviewed against Google’s customer-data terms, consent configuration, and the organization’s applicable privacy requirements.

What to do next

  1. Inventory every sender. Search the WordPress admin, theme code, plugins, GTM workspaces, CRM, automation tools, scheduled jobs, Data Manager, and API documentation for conversion-related workflows.
  2. Separate direct and indirect sources. Label website tags, Data Manager, and API connections separately from the CRM or connector systems that prepare data for those sources.
  3. Assign ownership. For every conversion action, identify the event owner, bidding status, identifier used, value source, consent signal, and duplicate-prevention method.
  4. Test consent timing. Confirm that the consent default is set before measurement tags fire and that updates occur after the visitor makes a choice. Check ad_storage, analytics_storage, ad_user_data, and ad_personalization as applicable to the implementation.
  5. Validate real payloads. Test controlled submissions and purchases for GCLID capture, order or transaction ID, value, currency, timestamp, hashed customer data, and consent fields.
  6. Review diagnostics before changing bids. Compare Google Ads diagnostics and reported conversions with CRM records, payment data, and backend transactions.
  7. Control migrations. When replacing a legacy offline conversion action, Google recommends waiting for the longer of three conversion cycles or four weeks before moving the new action to primary and the legacy action to secondary.

Conversion modeling can estimate otherwise unobservable links between ad interactions and conversions when consent choices, browser restrictions, or privacy controls limit direct measurement. Modeled conversions are estimates, not direct records of individual conversions. Treat observed, enhanced, imported, and modeled data as different measurement layers when evaluating lead quality, revenue, and campaign efficiency.

The practical decision this week is not simply whether the unified enhanced-conversions setting is enabled. It is whether your team can explain, on one page, who sends each conversion, where it goes, which identifiers it includes, how consent is recorded, how duplicates are prevented, and which actions are allowed to influence bidding.

Sources

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.

Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.