Author Archives:

Supercharge your integration workflow with the Google Pay & Wallet Developer MCP server

Google has announced the new Google Pay & Wallet Developer MCP server, an open-standard tool designed to securely connect AI development assistants and IDEs with real-time API and account context. The server allows developers to remain within their development environment to search official documentation, validate Wallet pass definitions, check integration status, and manage merchant accounts. Ultimately, this integration aims to reduce friction and accelerate development workflows by minimizing context switching and providing up-to-date, grounded AI support.
This entry was posted in Uncategorized on by .

Data Manager API now supports sending events to Google Marketing Platform destinations and IP ingestion for Google Ads Customer Match

Google Marketing Platform event ingestion

The Data Manager API has introduced support for sending offline conversion events to Google Marketing Platform products, including Campaign Manager 360, Search Ads 360, and Display & Video 360.

The AdIdentifiers object now includes dclid, impressionId, matchId, and encryptedUserIds. Check out the Get started guide to see which fields are required for uploading conversions that occur away from your website.

If you're currently using the Campaign Manager 360 API for conversion uploads, we recommend reviewing our upgrade guide to explore the advantages of the Data Manager API. These include a unified schema across all Google advertising products, encryption of user identifiers such as email and phone number, and the ability to route events to multiple destinations in a single request.

Composite data & IP ingestion for Google Ads Customer Match

In addition, you can now send IP addresses in Google Ads Customer Match uploads using the new CompositeData field.

Composite data allows you to include IP data, either on its own or alongside user identifiers like email address, phone number, and address information. Providing IP addresses along with their corresponding observation timestamps in IpData will help drive higher match rates for Google Ads Customer Match beginning in Q3 2026.

While we'll continue to support the user_data field for user identifier uploads, we recommend sending user identifiers using composite_data to ensure your integration is ready for future improvements and features.

Get started

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server. You can also contact us through the support page if you have an issue or need help with the API.

If you’re interested in becoming a data partner, please fill out the Partner Interest Form.

- Lindsey Volta, on behalf of the Data Manager API Team
This entry was posted in Uncategorized on by .

Google Chat external interoperability with Microsoft Teams via NextPlane OpenHub is now available

Organizations often need to collaborate with customers, partners, and suppliers who use Microsoft Teams. NextPlane OpenHub was built to bridge this Google Chat and Microsoft Teams divide, and it is now launching external interoperability to allow communication across organizational boundaries. OpenHub directly connects Google Chat users to people on external Microsoft Teams tenants, making cross-platform collaboration more seamless.

This release supports external interoperability between Google Chat and Microsoft Teams, including presence, 1:1 chat, group chat, Channels and Spaces, file sharing, and meeting and call initiation. A single Google Workspace environment can connect to multiple external Microsoft Teams tenants via OpenHub, enabling cross-tenant collaboration through a single interoperability layer. OpenHub is designed to provide a familiar cross-platform collaboration experience without requiring all parties to use the same collaboration platform.

OpenHub is also designed to support enterprise governance and deployment requirements. It is deployed as a dedicated single-tenant service, can run in a customer-owned GCP project, and keeps customer data under customer control. It uses customer-managed identities and does not require fake user accounts, Nextplane-controlled user accounts, cross-tenant impersonation, or a proxy Teams tenant.

For Google Workspace admins and IT decision-makers, this can help reduce deployment friction through tightly scoped, auditable permissions aligned with customer best practices. Ongoing configuration and management are handled through the existing Google Admin console and Microsoft Teams admin center, without requiring a separate OpenHub administration console. This is especially important for Google Workspace customers working with external organizations, because it avoids imposing a separate portal or a new management process on customers, partners, and suppliers.

Examples of how this can be used include:

  • Collaborate with customers, partners, and suppliers who use Microsoft Teams
  • Support cross-Teams tenant collaboration from a single Google Workspace environment
  • Maintain cross-platform communication during multi-company projects, joint ventures, or extended partner workflows
  • Enable interoperability when domain validation requirements make internal interoperability difficult to deploy

Getting started

  • Admins: This feature requires administrator consent on both sides of the connection, and Workspace and Teams admins must register NextPlan OpenHub as an enterprise application with their respective platforms before use. Configuration is managed at the domain level through the Google Admin console and Microsoft Teams admin center. OpenHub does not require a separate administration console and is managed through existing platform controls. Visit the NextPlane site to learn more about connecting Teams and Workspace. 
  • End users: There is no end user setting for this feature.

Rollout pace

Availability

  • Business: Business Starter, Standard, and Plus
  • Enterprise: Enterprise Starter, Standard, and Plus
Note that separate NextPlane licensing is required to enable interoperability.

Resources

This entry was posted in Uncategorized on by .

Share chats, canvases, and generated media from the Gemini app securely via Google Drive

We are introducing the ability for Workspace users on the web to share snapshots of their chats, canvases, and generated media in the Gemini app. Because this feature is powered by the same underlying technology as Google Drive, it uses the familiar, consistent sharing interface you already rely on for Google Docs and other files. You can still choose to allow conversation sharing via link.

With this update, members of your organization can easily share Gemini workflows and build on top of what others have created, scaling AI competency and collaboration across teams and enabling new ways for educators and students to teach and learn.

Getting started

  • Admins: This feature will be ON by default and can be managed via a new Admin console setting. Additionally, sharing is governed by your organization’s existing Drive sharing policies. If Drive content is set to be shareable outside the organization, your Gemini assets will be as well. Visit the Help Center to learn more.

  • End users: If enabled by your admin, you can share your Gemini conversations, canvases, and media from the web interface using the standard Drive sharing menu.

Rollout pace

Availability

  • Available to all Google Workspace customers

Resources

This entry was posted in Uncategorized on by .

Prevent account takeovers with Device Bound Session Credentials (DBSC), now generally available in the Chrome browser for Windows

Previously available in beta, Device Bound Session Credentials (DBSC) in the Chrome browser on Windows is now generally available and enabled by default for Google Workspace users.

DBSC strengthens account security after users are logged in and helps bind a session cookie — small files used by websites to remember user information — to the device a user authenticated from. Even if malware was present on the user’s device, DBSC reduces the risk of session theft and makes it meaningfully more difficult for malicious actors to exploit stolen session cookies.

With this change to general availability, Workspace admins no longer need to take action to enable DBSC in the Admin console. Organizations can also bolster protections with more granular account attributes when using DBSC together with context-aware access (CAA). To monitor DBSC binding events, admins can view the audit logs available in the security investigation tool.

An example of the audit log and log details for a DBSC event in the admin console

Getting started

  • Admins: This feature is ON by default for all Google Workspace customers, and there is no administrator control to disable it.
  • End users: There is no end user setting for this feature.

Rollout pace

Availability

  • Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts

Resources

This entry was posted in Uncategorized on by .

The “What” and “Why” on Meridian: Ads DevCast E6

Measuring the true impact of your marketing spend is complex, especially when you look across channels and mediums. In Episode 6 of Google’s Ads DevCast, "The 'What' and 'Why' on Meridian," we sit down with Product Manager Katie Munro and Developer Relations Engineer Jeff Li to explore Meridian, Google's open-source Marketing Mix Modeling (MMM) framework, and how it helps advertisers make data-backed strategic budget decisions.

Watch the full episode

Hear the full episode

Here is a summary of the talking points from our discussion on what Meridian is, how the math works, and the newly announced surfaces to help you implement it.

What is Meridian?

Meridian is Google's open-source Marketing Mix Modeling (MMM) framework. It provides a holistic, privacy-safe view of marketing ROI by analyzing aggregated historical data across all channels (digital, TV, print) alongside non-advertising factors (seasonality, economic conditions). It helps you determine the incremental lift of your marketing (sales caused by ads) versus baseline sales (sales that would have happened anyway).

The Core Math: Hill Curves & Adstock

Meridian uses statistical models to capture the real-world behavior of advertising:

  • Hill Curves: Models diminishing returns, showing where you have room to increase spend (headroom) and where you have saturated a channel.
  • Adstock: Models the lagged effect and decay of advertising over time, capturing the delay between seeing an ad and making a purchase.

The Measurement Trifecta

Meridian completes the modern measurement framework:

  • Attribution (GA4): For day-to-day tactical campaign tweaks.
  • Incrementality Experiments (Meridian GeoX): To test specific hypotheses in the real world.
  • MMM (Meridian): For macro-level, strategic budget planning.

New Meridian Releases from GML 2026

We discuss three major additions designed to make MMM more accessible and accurate:

  • Meridian in GA360: A turnkey, integrated MMM solution within Google Analytics 360 that uses existing behavioral data to provide cross-channel ROI insights without requiring a data science background.
  • Meridian Studio: A Google Cloud-based enterprise platform to build and scale models, featuring native agentic AI to automate data quality checks, suggest model health improvements, and assist in scenario planning.
  • Meridian GeoX: An open-source geo-based incrementality solution that acts as a calibration engine, allowing you to run geographic experiments and feed "ground truth" causation data back into your Meridian model.

Next Steps:

This entry was posted in Uncategorized on by .