← Back to Blog

Google Data Manager: No-Code UI vs the API for Your Store

Quick Answer: Google Data Manager offers two paths to activate first-party data: a no-code UI launched in December 2025, and an API for stores that need enrichment, custom logic, or multiple destinations. Both handle 3 data types under one connection — Customer Match audiences, offline conversions, and enhanced conversions for leads (Google for Developers, 2026). A May 2026 API release broadened ingestion to any non-reserved GA4 event. The decision rule is straightforward: if a supported connector fits and you want no code, use the UI; if you need custom backends or transformations, use the API.

Is there a no-code way to use Google Data Manager?

Yes — since its December 2025 launch, Google Ads Data Manager offers a UI to connect and activate first-party data without writing code (Google Ads Help, 2026). The UI sits inside Google Ads and provides pre-built connectors for common data sources — CRMs, CDPs, cloud storage buckets, and direct uploads. A marketer with admin access to the Ads account can configure a data connection, map fields, and start sending first-party data to Google’s ad systems without filing an engineering ticket.

This matters because the previous path to first-party data activation in Google Ads required either GTM server-side infrastructure, the Measurement Protocol, or a custom API integration — all of which needed a developer. The UI removed that bottleneck for the most common use cases, making first-party data activation accessible to the same person who manages the ad campaigns.

Google Data Manager’s no-code UI launched in December 2025, letting marketers connect and activate first-party data without engineering (Google Ads Help, 2026).

When should I choose the Data Manager API instead of the UI?

Choose the API when you need to enrich, transform, or apply custom logic to data, or when no out-of-the-box connector fits your backend (Google for Developers, 2026). The UI’s pre-built connectors handle standard sources well, but they don’t let you manipulate the data between your system and Google’s. If you need to hash customer data before sending, merge fields from multiple databases, apply business rules, or route the same data to several Google products in one call, the API is the path.

For WooCommerce stores, the API path typically makes sense in two scenarios: your store runs a custom checkout or subscription model that doesn’t map cleanly to the UI’s connector fields, or you’re already sending data server-side and want to consolidate your pipeline. The API isn’t better — it’s different. It trades setup simplicity for pipeline control.

Related: Google Data Manager API Just Became the Mandatory Ingestion Layer for Offline Conversions

Is the API developer-only?

Effectively yes — the API route requires engineering, while the UI is built for marketers connecting supported sources (Google Ads Help, 2026). The API expects you to authenticate with OAuth, construct JSON payloads, handle error responses, and manage retry logic. That’s engineering work, and it’s ongoing — schema changes, version upgrades, and new event types all require code updates.

That said, “developer-only” doesn’t mean “enterprise-only”. A single developer maintaining a WooCommerce store can implement the API integration in a few days and maintain it with minimal ongoing effort. The question isn’t team size — it’s whether you have engineering capacity at all. A store with no developer access and no plans to hire one should start with the UI and evaluate the API later if their data needs outgrow what the connectors offer.

What do both paths accept?

Both can handle 3 data types under one connection: Customer Match audiences, offline conversions, and enhanced conversions for leads (Google for Developers, 2026). This parity is important because it means neither path limits what data types you can activate — the choice is purely about how you connect, not what you connect.

Before Data Manager unified this, each data type had its own ingestion mechanism. Customer Match had one upload flow, offline conversions had another, and enhanced conversions for leads had a third. Data Manager consolidated all three under a single connection, whether you use the UI or the API. One authentication, one field mapping, three data types flowing through.

CapabilityNo-Code UIData Manager API
Customer Match audiencesYesYes
Offline conversionsYesYes
Enhanced conversions for leadsYesYes
Custom data enrichmentNoYes
Encryption before sendNoYes
Multi-destination in one requestNoYes
GA4 event ingestion (May 2026+)LimitedAny non-reserved event
Engineering requiredNoYes
Both the UI and the API handle 3 data types under one connection: Customer Match audiences, offline conversions, and enhanced conversions for leads — the choice is about how you connect, not what (Google for Developers, 2026).

Does the API unlock anything the UI can’t do?

The API supports encryption and sends to multiple destinations in a single request, giving more control than the connector UI (Google for Developers, 2026). Encryption means you can hash personally identifiable information before it leaves your server — a meaningful compliance advantage for stores handling sensitive customer data. Multi-destination sends mean one API call can route the same conversion event to Google Ads, GA4, and any other configured endpoint simultaneously.

For WooCommerce stores, the practical unlock is pipeline efficiency. Instead of maintaining separate integrations for each Google product — one for enhanced conversions, another for Customer Match, a third for GA4 events — the API consolidates them into a single outbound pipeline. Fewer moving parts, fewer points of failure, one place to debug when something breaks.

Related: What is Google Data Manager API v1.6 and can it replace multiple WooCommerce data connectors?

How did capabilities grow in 2026?

A May 2026 release broadened the API to send any non-reserved event to GA4 web and app streams, widening what engineering teams can automate (Google for Developers, 2026). Before this release, the API handled ads-specific data types — conversions, audiences, leads. After it, the API became a general-purpose ingestion layer for GA4 analytics events too.

This is a significant shift for WooCommerce stores that were using Measurement Protocol to send server-side events to GA4. The Data Manager API now covers that use case plus the ads-side data types in one integration. Stores that previously maintained two server-side pipelines — Measurement Protocol for GA4, the Conversions API for Google Ads — can now consolidate into one.

The store sales addition in the same release also matters. For WooCommerce stores with offline or in-person revenue, the API can now ingest those transactions alongside online conversions — giving a single view of all purchase data flowing into Google’s systems.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

Either path works, provided you pass the 2 EEA signals — ad_user_data and ad_personalization — so the data stays usable (Tag Manager Help, 2026). Consent compliance isn’t a path-specific requirement. It’s a data requirement. Whether you send through the UI or the API, Google’s systems expect those two signals attached to every record that involves EEA traffic.

In the UI, consent signals are mapped as fields during connector setup. In the API, they’re included in the request payload alongside the event data. The mechanics differ, but the obligation is identical: no consent signals, no data activation for EEA users. Stores that skip this step don’t get an error — they get silently unusable data, which is worse because it looks like everything is working until the campaign reports don’t match reality.

What is the simplest decision rule?

If a supported connector fits and you want no code, use the UI; if you need enrichment, custom backends, or multiple destinations, use the API (Google for Developers, 2026). Most WooCommerce stores without a dedicated developer start with the UI and graduate to the API as their data needs grow. That’s not a compromise — it’s a reasonable path that gets first-party data flowing immediately while preserving the option to upgrade later.

For stores that want neither the UI’s manual connector maintenance nor the API’s engineering overhead, a managed server-side pipeline handles the ingestion end to end. Tools like Transmute Engine sit between your WooCommerce events and Google’s ingestion layer — routing conversions, audiences, and GA4 events through a single managed endpoint without the store owner configuring Data Manager directly. That’s a third path: let the pipeline handle the plumbing while you focus on the store.

Related: Google Data Manager Map View Is About to Show Your WooCommerce Data Stack

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • Two paths, same data types: Google Data Manager’s no-code UI (December 2025) and the API both handle Customer Match, offline conversions, and enhanced conversions for leads under one connection.
  • The API adds control: encryption, multi-destination sends, and custom transformations are API-only — choose it when you need pipeline flexibility.
  • May 2026 expanded the API to GA4: any non-reserved event can now flow through the Data Manager API, consolidating what used to require Measurement Protocol separately.
  • Consent is non-negotiable on both paths: pass ad_user_data and ad_personalization for EEA traffic or the data is silently unusable.
  • Start with what fits your resources: no developer means the UI; custom needs mean the API; want neither overhead? A managed pipeline handles it.
Is there a no-code way to use Google Data Manager?

Yes — since its December 2025 launch, Google Ads Data Manager offers a UI to connect and activate first-party data without writing code. The UI provides pre-built connectors for common data sources, so marketers can set up data flows without involving engineering.

When should I choose the Data Manager API instead of the UI?

Choose the API when you need to enrich, transform, or apply custom logic to data, or when no out-of-the-box connector fits your backend. The API gives you control over the data pipeline that the UI’s pre-built connectors don’t offer.

Is the API developer-only?

Effectively yes — the API route requires engineering, while the UI is built for marketers connecting supported sources. If your team doesn’t have a developer available, the UI path is viable for most standard use cases.

What do both paths accept?

Both can handle 3 data types under one connection: Customer Match audiences, offline conversions, and enhanced conversions for leads. This means neither path limits what data types you can work with — the choice is about how you connect, not what you connect.

Does the API unlock anything the UI can’t do?

The API supports encryption and sends to multiple destinations in a single request, giving more control than the connector UI. It also allows custom data transformations before ingestion, which the UI’s pre-built connectors don’t support.

How did capabilities grow in 2026?

A May 2026 release broadened the API to send any non-reserved event to GA4 web and app streams, widening what engineering teams can automate. This effectively made the API a replacement for Measurement Protocol in many server-side use cases.

Which path handles consent correctly?

Either path works, provided you pass the 2 EEA signals, ad_user_data and ad_personalization, so the data stays usable. Consent compliance is a data requirement, not a path requirement — both the UI and the API enforce the same signals.

What is the simplest decision rule?

If a supported connector fits and you want no code, use the UI; if you need enrichment, custom backends, or multiple destinations, use the API. Most WooCommerce stores without a dedicated developer start with the UI and graduate to the API as their data needs grow.

References

  1. Google Ads Help (2026). About enhanced conversions for leads. Source
  2. Google for Developers (2026). Data Manager API developer guides. Source
  3. Google for Developers (2026). Upgrade from Measurement Protocol to the Data Manager API. Source
  4. Google for Developers (2026). Data Manager API: store sales and GA event ingestion. Source
  5. Tag Manager Help (2026). Updates to consent mode for EEA traffic. Source