Google Search Ads 360 API
Browse all Google APIs✓ Official Vendor SpecMarketingAdvertisingoauth211 EndpointsREST
For Agents
Upload offline and online conversions, update conversion availability, and pull cross-engine search ad reports for Search Ads 360 (formerly DoubleClick Search).
Use for: Upload yesterday's CRM-confirmed conversions to Search Ads 360, Update a conversion's revenue value after a refund, I need to pull a campaign performance report for the last 30 days, Retrieve the saved columns defined for an advertiser
Not supported: Does not manage campaigns, keywords, ad copy, or budgets — use for Search Ads 360 conversion uploads and report generation only.
The Search Ads 360 API automates conversion uploads and report downloads for paid search and shopping campaigns managed in Search Ads 360 (the rebranded DoubleClick Search). Advertisers send offline and online conversions, update conversion availability, and pull dimension- and metric-rich reports across agency, advertiser, and engine account hierarchies. The API is the canonical interface for tying back-end revenue, CRM-defined conversions, and saved-column data into Search Ads 360 attribution and reporting.
Install Jentic One Beta
Connect the Search Ads 360 API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Search Ads 360 API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Search Ads 360 API.
Insert offline and online conversions to attribute back-office revenue to Search Ads 360 clicks
Update existing conversions with revised revenue, status, or custom dimension values
Retrieve conversions by advertiser and engine account for reconciliation
Notify Search Ads 360 of conversion availability dates so the system uses correct bid signals
Generate reports with chosen metrics, dimensions, and filters across the agency-advertiser-engine hierarchy
List saved columns and ID mappings for an advertiser to align reporting dimensions with internal IDs
Use Cases
Patterns agents use Search Ads 360 API for, with concrete tasks.
★ Offline Conversion Uploads for Bid Optimisation
Marketers feed CRM-confirmed orders, qualified leads, and lifetime-value conversions back into Search Ads 360 so Smart Bidding optimises against true business outcomes, not just on-site events. The API supports inserting and updating conversions with custom dimensions and metrics, and updateAvailability tells the system the latest conversions for a date range have been uploaded so attribution windows close correctly.
POST /doubleclicksearch/v2/conversion with conversionTimestamp, clickId, revenueMicros, and customMetric values for each new CRM-qualified order in the last hour.
Cross-Engine Performance Reporting
Agencies running paid search across Google Ads, Microsoft Ads, and Yahoo through Search Ads 360 use the reports endpoint to pull unified performance with consistent dimensions and metrics. Reports are defined inline, queued, and downloaded once ready, with saved-columns support so advertiser-specific custom dimensions appear in the output. Pipelines typically run the API daily into a warehouse.
POST /doubleclicksearch/v2/reports with statisticsCurrency, columns including campaign and impressions, and a date range, then poll GET /doubleclicksearch/v2/reports/{reportId} until isReportReady is true.
Conversion Reconciliation and Audit
When discrepancies appear between SA360 and the data warehouse, ops teams pull conversions by advertiser and engine account, compare to source-of-truth CRM rows, and update or insert missing conversions through the same API. ID mapping endpoints help line up SA360 IDs with internal click trackers during audits.
GET /doubleclicksearch/v2/agency/{agencyId}/advertiser/{advertiserId}/engine/{engineAccountId}/conversion for the audit window and PUT /doubleclicksearch/v2/conversion for any rows that need correction.
Agent-Driven SA360 Updates via Jentic
An AI agent that monitors CRM events can ship newly confirmed conversions to Search Ads 360 in near-real time through Jentic, without the engineering team writing dedicated SA360 code. The agent finds the right insert operation by intent, learns the conversion schema, and posts each conversion as soon as the CRM event lands.
Search Jentic for 'upload search ad conversion', load the POST /doubleclicksearch/v2/conversion schema, and execute it for each new CRM-confirmed order.
Key Endpoints
11 endpoints — the search ads 360 api automates conversion uploads and report downloads for paid search and shopping campaigns managed in search ads 360 (the rebranded doubleclick search).
METHOD
PATH
DESCRIPTION
POST
/doubleclicksearch/v2/conversion
Insert new conversions
PUT
/doubleclicksearch/v2/conversion
Update existing conversions
POST
/doubleclicksearch/v2/conversion/updateAvailability
Notify SA360 that conversions for a window are fully uploaded
POST
/doubleclicksearch/v2/reports
Generate a report with chosen metrics and dimensions
GET
/doubleclicksearch/v2/agency/{agencyId}/advertiser/{advertiserId}/engine/{engineAccountId}/conversion
Retrieve conversions for an advertiser and engine account
GET
/doubleclicksearch/v2/agency/{agencyId}/advertiser/{advertiserId}/savedcolumns
List saved columns for an advertiser
POST
/doubleclicksearch/v2/conversion
Insert new conversions
PUT
/doubleclicksearch/v2/conversion
Update existing conversions
POST
/doubleclicksearch/v2/conversion/updateAvailability
Notify SA360 that conversions for a window are fully uploaded
POST
/doubleclicksearch/v2/reports
Generate a report with chosen metrics and dimensions
GET
/doubleclicksearch/v2/agency/{agencyId}/advertiser/{advertiserId}/engine/{engineAccountId}/conversion
Retrieve conversions for an advertiser and engine account
GET
/doubleclicksearch/v2/agency/{agencyId}/advertiser/{advertiserId}/savedcolumns
List saved columns for an advertiser
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OAuth client secrets and refresh tokens are stored in the Jentic vault. Agents only ever see short-lived Bearer tokens scoped to doubleclicksearch, so a leaked agent context cannot be reused to authenticate elsewhere.
Intent-based discovery
Agents search by intent (e.g. 'upload an offline conversion') and Jentic returns the conversion insert, update, and report operations with input schemas attached, including the agency/advertiser/engine path parameters.
Time to first call
Direct SA360 integration: 2-4 days for OAuth, conversion schema mapping, and report polling. Through Jentic: under 1 hour for a one-shot conversion upload flow.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Search Ads 360 API through Jentic.
What authentication does the Search Ads 360 API use?
Search Ads 360 uses Google OAuth 2.0 with the doubleclicksearch scope. End-user and service account flows are both supported. Through Jentic the credentials are stored encrypted and the agent only sees scoped Bearer tokens.
Can I upload offline conversions to the Search Ads 360 API?
Yes. POST /doubleclicksearch/v2/conversion accepts a list of conversions with click ID, conversion timestamp, revenue micros, and custom metric/dimension values. Once a window of uploads is complete, call /doubleclicksearch/v2/conversion/updateAvailability so the bidder knows attribution data is finalised.
What are the rate limits for the Search Ads 360 API?
Per-project quotas appear in the Cloud Console (default ~4 requests per second per project) and conversion uploads have additional per-advertiser caps documented in the SA360 help center. Large bulk uploads should batch up to 200 conversions per request.
How do I run an SA360 report through Jentic?
Search Jentic for 'run a Search Ads 360 report', load the POST /doubleclicksearch/v2/reports schema, and execute it with your columns and date range. Jentic returns the report ID; poll GET /doubleclicksearch/v2/reports/{reportId} until isReportReady is true and download the file URLs.
Is the Search Ads 360 API free?
The API is included with a Search Ads 360 license. SA360 itself is sold to enterprise advertisers and agencies, typically on a percent-of-spend or fixed-fee basis under direct Google contracts.
How do I update an existing conversion?
PUT /doubleclicksearch/v2/conversion with the same conversion identifiers and the new field values. Use this to revise revenue after refunds or change conversion status when an order is cancelled.
GET STARTED