Updated the component to Google Ads API v25 with reworked campaign change detection and opt-in batching across all polling triggers:

• Updated the default API version for new connections to v25, matching Google's current major release; updated the minimum supported version to v22, so v22 through v25 are all selectable and connections pinned below v22 are automatically upgraded
• Updated the New and Updated Campaigns trigger to read the Google Ads change history instead of storing a copy of every campaign between recurrences, a breaking change; totalCampaigns is no longer returned, oldValue and newValue now carry the campaign resource directly rather than wrapped in a query row, a timeRange object was added alongside syncedAt, and detection is bounded by Google's 30-day change history window
• Added opt-in batching to the New and Updated Campaigns, Account Change History, and Campaign Budget Alerts triggers, dispatching each record individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
• Updated Get Account Reports and Get Detailed Lead Reports to group their Page Size and Page Token inputs into a Pagination structured object
• Added connection setup guidance for Google's passkey requirement; from August 5, 2026 a passkey is required to authorize new Google Ads API access, and a new passkey can take up to 7 days to become usable
• Added output schemas to 14 actions for improved field mapping during configuration
• Added inline action calling support across all actions for improved example output during configuration

Enabled the OAuth 2.0 connection to drive both the Google Ads and Data Manager APIs from a single connection.

• Exposed the Scopes field so integration builders can append the Data Manager scope (https://www.googleapis.com/auth/datamanager) to the existing Ads scope. The default remains the Ads scope only, so Ads-only integrations are unaffected.
• Extended createDataManagerClient to accept the unified OAuth 2.0 connection in addition to the dedicated Data Manager OAuth 2.0 connection. When the OAuth 2.0 connection is used, the Data Manager API version is pinned to v1.

Builders who opt in by adding the Data Manager scope will trigger a one-time re-consent for affected end-users, as the granted scope set changes.

Added Ingest Offline Conversions action using the Google Ads Data Manager API to replace the deprecated Upload Click Conversions action, which will stop accepting requests after June 15, 2026.

This action uses a new dedicated Data Manager OAuth 2.0 connection, separate from the existing Google Ads OAuth connection:

• No Developer Token required — the Data Manager API does not use the developer-token header
• Configurable API version — defaults to v1
• Scoped to the Data Manager API only — does not affect existing Google Ads OAuth connections

Raised minimum supported Google Ads API version from v20 to v21 ahead of v20's June 2026 sunset. Connections explicitly configured for v20 will be auto-upgraded to v21 by the existing validateApiVersion floor check.

Various modernizations and documentation updates

Various modernizations and documentation updates

Updated default Google Ads API version from v22 to v23 and raised minimum supported version from v19 to v20:

• Default API version updated to v23 — default for all new connections, bringing support for Performance Max channel reporting, AI-powered audience definitions, and enhanced invoice granularity.
• Minimum supported version raised to v20 — Google sunset v19 on February 11, 2026; connections configured with v19 will now fall back to v20.
• Campaign date fields updated — trigger queries now use campaign.start_date_time and campaign.end_date_time (v23 replaces the previous start_date/end_date fields).
• Existing integrations unaffected — connections using v20, v21, or v22 can continue using their configured version.
• GAQL query review recommended — users with queries referencing CallAd, CallAdInfo, Campaign.url_expansion_opt_out, or the legacy video metric names (video_views, average_cpv, video_view_rate) should review these fields before upgrading, as they are removed or renamed in v23.

Updated default Google Ads API version to v22 with new EU Political Advertising requirements:

• Default API version updated to v22 — applied to all new connections.
• EU Political Advertising field required — campaign creation and location targeting now require the Contains EU Political Advertising field when using v22.
• Existing integrations unaffected — connections can continue using v19, v20, or v21 by specifying the API Version connection field.

Added inline data sources for accessible customers and sub-accounts to enhance data selection capabilities