Ellipse Gradient for Header

Search Ads 360 Integration Guide

Connect Search Ads 360 reporting and supported advertising resources with enterprise systems through its REST API, OAuth 2.0, scheduled workflows, and controlled data synchronization.

Search Ads 360 integration options at a glance

Search Ads 360 provides a current REST Reporting API for querying campaign, ad group, ad, keyword, conversion, and performance data, as well as supported resource mutations. Queries use Search Ads 360 Query Language and can use paged or searchStream-style retrieval. OAuth 2.0 supplies authorized access through Google accounts, refresh tokens, scopes, and advertiser or manager permissions. No general-purpose webhook framework was confirmed, so scheduled polling is the safer synchronization approach. Martini can authenticate securely, run scheduled workflows, process large result sets, map and normalize advertising data, apply governance rules, and write results to APIs, databases, warehouses, or reporting services.

Integration pointSupported by Search Ads 360?Common use casesHow Martini supports it
REST APIsYesQuery Customers, Campaigns, Ad groups, Ads, Ad group criteria, Conversions, metrics, segments, and supported mutations. Requests use Google resource paths and JSON payloads.Martini can consume the REST API from workflows, submit Query Language requests, transform responses, and expose reusable API-led integration assets.
Reporting and query accessYesThe search and searchStream-style methods retrieve filtered dimensions, segments, measures, statuses, costs, clicks, impressions, and conversions.Martini can implement query construction, pagination or controlled stream processing, date windows, and downstream loading.
Bulk / async / batch APIsLimitedLarge reporting retrieval is supported through streaming and Google API request patterns; mutation and batch capabilities vary by resource and API version.Martini can orchestrate bounded batches and inspect resource-specific responses, but the current API reference must be verified before high-volume writes.
AuthenticationYesOAuth 2.0 uses Google authorization, client credentials, access and refresh tokens, the doubleclicksearch scope, and Search Ads 360 permissions.Martini can store protected credentials and tokens in environment configuration and send bearer authorization to the REST API.
Webhooks / outbound callbacksNot confirmedNo general-purpose webhook framework for campaign, ad, keyword, or reporting changes was confirmed.Martini should use scheduled triggers and API queries rather than assume vendor-generated event delivery.
SOAP APIsLegacyOlder DoubleClick Search interfaces used legacy API patterns, but new integrations should use the current REST API where possible.Martini can consume SOAP services when required by a documented legacy dependency, with version and migration constraints explicitly managed.
File / attachment APIsNoNo general-purpose native file or attachment API for campaign-object import and export was confirmed.Martini can process files from other confirmed enterprise endpoints, but should not model Search Ads 360 as a native file integration.
Database / analytics accessNoSearch Ads 360 does not expose a direct customer database interface; data should be obtained through APIs or applicable Google export products.Martini can write retrieved data to a database or warehouse, but does not connect directly to a Search Ads 360 database.

How Search Ads 360 exposes data and business events

Search Ads 360 REST APIs

The current Search Ads 360 interface is a Google REST API for retrieving advertising resources, reporting metrics, and supported mutations. Requests use JSON and Google resource paths, with queries expressed through Search Ads 360 Query Language.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with OAuth 2.0, constructs a constrained query, invokes the REST endpoint, validates the response, maps resource fields to a canonical model, and writes or exposes the result for downstream systems.

Implementation sequence

Obtain a Google OAuth 2.0 access token
Resolve the manager or advertiser customer context
Construct a filtered Search Ads 360 Query Language request
Invoke the REST resource or reporting method
Validate the response and handle API errors
Map resources and metrics to the target model

Reporting and searchStream queries

Search and searchStream-style methods support structured reporting queries with selected resources, fields, metrics, segments, and filters. Streaming is useful for large result sets, while paged methods require explicit pagination.

Martini implementation pattern

Martini implementation pattern: a scheduled workflow manages the reporting window, processes pages or stream chunks without assuming that all data fits in one payload, applies account-specific normalization, and commits idempotent results.

Implementation sequence

Calculate the reporting period and lookback window
Submit the filtered reporting query
Process each page or stream result incrementally
Normalize dates, time zones, currencies, and dimensions
Write rows using deterministic synchronization keys
Record the checkpoint and processing outcome

Scheduled synchronization

No general-purpose Search Ads 360 webhook framework was confirmed for campaign, ad, keyword, or reporting changes. Scheduled polling and API-side filters are therefore the safer design for recurring synchronization.

Martini implementation pattern

Martini implementation pattern: a Scheduler Trigger starts a workflow at a controlled cadence, which retrieves changed or recalculated data, applies business rules, and retries transient Google API failures with bounded concurrency.

Implementation sequence

Start the workflow on a controlled schedule
Load the account and reporting configuration
Retrieve current data with filters and a lookback window
Apply validation, deduplication, and business rules
Persist results and update the synchronization checkpoint
Monitor failures and retry eligible work

Supported resource mutations

Search Ads 360 supports mutations for selected resources and fields, but writable operations, partial failures, request limits, and batch behavior depend on the API version and resource reference.

Martini implementation pattern

Martini implementation pattern: an API or scheduled workflow validates an approved change, checks permissions and resource support, submits the mutation, inspects per-operation errors, and records an auditable outcome rather than treating HTTP success as universal success.

Implementation sequence

Validate the requested resource and writable fields
Apply approval and account-scope business rules
Submit the supported mutation request
Inspect operation-level success and failure details
Retry only safe transient failures
Record the final mutation result for reconciliation

Common Search Ads 360 integration patterns

Pattern 1: Synchronize Search Ads 360 performance to a warehouse

When to use this pattern

Use this pattern for daily or intraday campaign, ad group, keyword, conversion, and metric reporting. It is appropriate when reporting data must be retained for trend analysis, finance reporting, or cross-account dashboards.

Integration direction
Search Ads 360
Martini
BigQuery
Example Mapping
Search Ads 360 FieldCanonical FieldTarget Field
customer.idadvertiser_idadvertiser_id
campaign.idcampaign_idcampaign_id
metrics.clicksclick_countclick_count
metrics.conversionsconversion_countconversion_count
Martini implementation pattern

A scheduled workflow submits a date-filtered query, processes pages or stream chunks, normalizes account time zones and currencies, and upserts rows using customer, resource, date, and dimension keys. Late conversion changes are handled through a lookback window; transient quota and server errors use bounded retries.

Martini capabilities used
  • workflows
  • API consumption
  • scheduling
  • data mapping
  • business rules
  • error handling

Pattern 2: Govern campaigns and budgets

When to use this pattern

Use this pattern when an organization needs to identify campaigns outside approved status, budget, bidding, or targeting policies and optionally submit approved changes to supported writable resources.

Integration direction
Search Ads 360
Martini
Governance API
Example Mapping
Search Ads 360 FieldCanonical FieldTarget Field
campaign.statuscampaign_statusstatus
campaign.budgetdaily_budgetapproved_budget
campaign.biddingStrategybidding_strategypolicy_bidding_strategy
Martini implementation pattern

Martini retrieves campaign configuration, evaluates policy rules, and sends exceptions to a governance application. Approved mutations are submitted only after verifying the selected API version, resource permissions, writable fields, and partial-failure behavior; ambiguous requests are reconciled before retrying.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • validation
  • error handling

Pattern 3: Reconcile conversions and revenue

When to use this pattern

Use this pattern when marketing and finance teams need to compare Search Ads 360 conversions with orders, leads, or revenue from an enterprise application. It accounts for attribution and conversion latency.

Integration direction
Salesforce
Martini
Search Ads 360
Example Mapping
Search Ads 360 FieldCanonical FieldTarget Field
Opportunity.Idsource_conversion_referenceconversion_reference
Opportunity.Amountrevenue_valueconversion_value
conversion.dateattributed_event_dateevent_date
Martini implementation pattern

A workflow retrieves enterprise outcomes and Search Ads 360 conversion data, maps identifiers and values, applies attribution-window and duplicate rules, and produces a reconciliation result. Any write-back is conditional on documented support for the selected conversion resource and is isolated from read-side reconciliation.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • deduplication
  • error handling

Pattern 4: Publish cross-platform marketing reporting

When to use this pattern

Use this pattern when Search Ads 360 must be combined with Google Analytics 4, Campaign Manager 360, Display & Video 360, or another source for a consolidated reporting API or dataset.

Integration direction
Search Ads 360
Martini
Reporting API
Example Mapping
Search Ads 360 FieldCanonical FieldTarget Field
campaign.resourceNamecanonical_campaign_keycampaign_key
segments.datereporting_datedate
metrics.costMicroscost_amount_microscost
customer.currencyCodeaccount_currencycurrency
Martini implementation pattern

Martini orchestrates source retrieval, standardizes campaign identifiers, dates, currencies, and channel dimensions, applies completeness checks, and exposes or loads the consolidated result. Source-specific failures are isolated so one unavailable account does not silently invalidate the complete dataset.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • orchestration
  • validation
  • monitoring

Applications commonly integrated with Search Ads 360

Search Ads 360 can be incorporated into broader Google Marketing Platform, analytics, sales, and data-warehouse architectures. The exact product linkage and write-back capabilities should be validated for each account and API version.

Application Scenario Direction Martini Pattern
Google Analytics 4 Compare advertising performance with onsite engagement, analytics events, and conversion outcomes. Search Ads 360 → Martini → Google Analytics 4 A scheduled Martini workflow retrieves Search Ads 360 metrics, combines them with GA4 data obtained through the applicable integration, normalizes campaign identifiers and dates, and publishes a reporting dataset or API.
Campaign Manager 360 Reconcile search activity with Floodlight conversions and broader campaign measurement. Search Ads 360 → Martini → Campaign Manager 360 Martini orchestrates API retrieval from the relevant Google products, applies shared campaign and conversion mappings, and writes a reconciled dataset while recording account and attribution context.
Display & Video 360 Combine search, display, and video performance for cross-channel planning and measurement. Search Ads 360 → Martini → Display & Video 360 A scheduled workflow retrieves and transforms channel-level data, standardizes currencies and time zones, and loads a warehouse or reporting API for consolidated analysis.
Google Ads Compare or consolidate performance and governance data across Google advertising platforms. Google Ads → Martini → Search Ads 360 Martini consumes the applicable APIs, maps campaign and account identifiers into a canonical model, applies validation rules, and exposes normalized results to downstream governance or reporting systems.
BigQuery Store historical campaign, cost, conversion, and performance data for analysis and modeling. Search Ads 360 → Martini → BigQuery A scheduled Martini workflow queries defined reporting windows, processes paged or streamed results, normalizes dimensions and measures, and writes idempotently to BigQuery through the configured database or API path.
Salesforce Relate advertising conversions to lead and opportunity outcomes for marketing performance analysis. Salesforce → Martini → Search Ads 360 Martini maps approved Salesforce lead or opportunity outcomes to Search Ads 360 conversion requirements where the selected API version supports the operation; otherwise it publishes a reconciled dataset without assuming write-back support.
Snowflake Centralize Search Ads 360 data with sales, finance, and marketing datasets. Search Ads 360 → Martini → Snowflake A scheduled workflow retrieves incremental reporting data, applies lookback and deduplication rules, and loads Snowflake using deterministic keys and versioned mappings.
Looker Studio Present campaign and conversion performance to marketing stakeholders. Search Ads 360 → Martini → Looker Studio Martini prepares a normalized reporting dataset or controlled API façade for the dashboard layer, rather than attempting to control dashboard configuration directly.

How to build a Search Ads 360 integration in Martini

Objective

Establish Google authorization and protect the credentials needed for Search Ads 360 access.

Instructions in Martini

  • Configure the Google Cloud OAuth client and required scope.
  • Store client credentials, refresh tokens, and customer identifiers as protected environment configuration.
  • Validate advertiser or manager permissions before production execution.

Objective

Select a schedule or controlled API request because general-purpose Search Ads 360 webhooks were not confirmed.

Instructions in Martini

  • Use a Scheduler Trigger for recurring reporting synchronization.
  • Define reporting windows, lookback periods, and account-specific schedules.
  • Use an exposed Martini API when an upstream application must request a controlled refresh.

Objective

Query the current REST Reporting API using only the resources, fields, metrics, segments, and filters required by the workflow.

Instructions in Martini

  • Construct a Search Ads 360 Query Language request.
  • Choose paged retrieval or searchStream processing based on result volume.
  • Carry customer context and resource names through each result.

Objective

Coordinate API calls, pagination, stream chunks, validation, enrichment, and downstream writes as a maintainable workflow.

Instructions in Martini

  • Bound concurrency and preserve account isolation.
  • Separate retrieval, transformation, and persistence stages.
  • Record checkpoints and processing outcomes.

Objective

Convert Search Ads 360 resources and metrics into a canonical model suitable for the destination system.

Instructions in Martini

  • Normalize time zones, currencies, dates, identifiers, and metric units.
  • Map Campaigns, Ad groups, Ads, criteria, and Conversions to target fields.
  • Preserve source resource names for reconciliation.

Objective

Apply governance, completeness, attribution, and idempotency rules before writing or mutating data.

Instructions in Martini

  • Validate required fields and account scope.
  • Use deterministic keys for reporting upserts.
  • Verify writable fields and approvals before submitting mutations.

Common Search Ads 360 data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
CustomersDefine manager or advertiser account context for access and reporting queries.BigQuery, Snowflake, Salesforce, reporting APIsMartini stores explicit customer context, validates account permissions, and carries the identifier through workflow mappings.
CampaignsRepresent campaign status, budgets, bidding, targeting, and performance dimensions.Data warehouses, governance services, Google marketing reportingMartini queries selected fields, normalizes status, budget, currency, and time-zone values, and verifies writable fields before mutations.
Ad groupsOrganize ads, keywords, targeting criteria, and performance within campaigns.BigQuery, Snowflake, marketing reporting systemsMartini links ad groups to customer and campaign keys, processes paged or streamed results, and applies deterministic upsert keys.
AdsStore advertising creatives and serving status.Campaign reporting, governance applications, data warehousesMartini maps creative and status fields into a canonical model and preserves source resource names for reconciliation.
Ad group criteria / keywordsRepresent keywords, targeting, bids, match types, and status within ad groups.Optimization tools, warehouses, reporting APIsMartini transforms match-type, bid, status, and hierarchy fields and validates account and campaign relationships.
ConversionsCapture conversion events and conversion-related performance, including applicable Floodlight activity.Salesforce, finance reporting, BigQuery, SnowflakeMartini applies attribution lookback windows, deduplicates events, normalizes values and dates, and reconciles late-arriving changes.

Authentication and security considerations

OAuth 2.0 and account authorization

Search Ads 360 access uses Google OAuth 2.0 with a Google Cloud project, authorization code exchange, access and refresh tokens, and the documented doubleclicksearch scope. Effective access also depends on the Google user's Search Ads 360 advertiser or manager permissions.

Protect credentials and scope access

  • Store client credentials, refresh tokens, scopes, and customer identifiers in protected Martini environment configuration.
  • Restrict the Google Cloud project, authorized users, advertiser accounts, and requested scopes to the integration requirement.
  • Plan for revoked tokens, consent changes, user offboarding, and permission changes.
  • Expose only normalized, authorized operations through any Martini API façade.

Operational considerations for Search Ads 360 integrations

Quotas, pagination, and throughput

Google quotas and request limits require bounded concurrency, selective fields and filters, backoff for throttling, and retries for transient 429 and 5xx responses. Use pagination for paged methods and controlled chunk processing for searchStream results.

Data correctness

  • Use deterministic keys based on customer, resource, date, dimensions, and segments.
  • Use lookback windows for late conversions and attribution changes.
  • Normalize account time zones, currencies, date boundaries, and monetary units.
  • Inspect operation-level errors for supported mutations rather than relying only on HTTP status.

Lifecycle and testing

Confirm the supported API version and resource fields before deployment. Version mappings, test representative accounts and queries, monitor schema changes, and treat unknown response fields as compatible additions where possible.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond a single script

Martini separates authentication, retrieval, transformation, business rules, persistence, and monitoring in reusable workflows. This makes scheduled reporting, account isolation, pagination, lookback windows, and downstream delivery easier to maintain than independent scripts.

Controlled integration assets

Martini can consume the Search Ads 360 REST API, expose a controlled REST façade, map data into canonical models, and connect the result to databases, warehouses, and enterprise APIs without exposing Google credentials to every consumer.

Operational resilience

  • Apply bounded retries and error routing for quotas and transient failures.
  • Persist checkpoints and deterministic keys for restartable synchronization.
  • Validate mutations and isolate partial failures.
  • Centralize environment configuration and monitoring for production support.

Frequently asked questions

How can Search Ads 360 be integrated with enterprise systems?

Search Ads 360 can be integrated through its REST Reporting API using OAuth 2.0. Enterprise workflows can query advertising resources and metrics, process paged or searchStream results, and send normalized data to warehouses, databases, reporting APIs, or other business applications. Scheduled polling is the safer synchronization method because a general-purpose webhook framework was not confirmed.

Can Martini integrate with Search Ads 360?

Yes. Martini can consume the Search Ads 360 REST API, authenticate with Google OAuth 2.0, submit supported queries, process large result sets, map advertising data, schedule synchronization workflows, and expose a controlled API façade for internal consumers.

Do I need a connector to integrate Search Ads 360 with Martini?

No. A dedicated Search Ads 360 connector is not required. Martini can integrate using Search Ads 360's documented REST API and OAuth 2.0 authentication through workflows and APIs.

Is there any extra Lonti cost to integrate Search Ads 360 with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Search Ads 360. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Google, cloud infrastructure, databases, or other third-party services depending on subscription, API usage, and deployment model.

Which Search Ads 360 integration methods should be used?

New integrations should generally use the current REST Reporting API with Google OAuth 2.0. Search and searchStream-style methods support reporting retrieval, while mutations should be implemented only for resources and fields confirmed as writable in the selected API version. Legacy SOAP-style interfaces should not be selected for new development unless migration constraints require them.

Does Search Ads 360 provide webhooks or event notifications?

A general-purpose webhook system for campaign, ad, keyword, and reporting changes was not confirmed. Martini integrations should normally use scheduled workflows, API-side filters, status fields, and reporting windows rather than assume vendor-generated callbacks.

How does synchronization with Search Ads 360 work?

A scheduled Martini workflow can query explicit manager or advertiser customer contexts, process pages or stream results, and use deterministic keys for idempotent writes. Incremental designs should include a lookback window because conversion values and attribution can change after the original interaction date.

Can Martini expose an API façade for Search Ads 360?

Yes. Martini can expose a controlled REST API that accepts approved reporting or synchronization requests, applies authorization and validation, invokes Search Ads 360 through a workflow, and returns a normalized response without exposing Google credentials or account-specific implementation details.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Search Ads 360 to your enterprise systems

Use Martini to build a secure, maintainable Search Ads 360 integration around OAuth 2.0, REST reporting queries, scheduled synchronization, data transformation, and operational controls.

EXPLORE MARTINI
BOOK A DEMO