Google Ads

Performance by device

Splits spend, clicks, conversions, CPA and ROAS by device (mobile, desktop, tablet) for the period, next to the previous period of the same length. Use when: the user asks about mobile versus desktop, or before setting device bid modifiers. Do not use when: the campaign uses Smart Bidding and the user wants to act on the split — Smart Bidding already bids per device, so the split is information, not an instruction. A device with very little spend is not evidence. Mobile usually shows a worse conversion rate on considered purchases and a better one on calls and local intent; look at the landing page before blaming the device. If you are unsure which account, campaign or period the user means, ask them — do not guess ids or dates.

post/api/v1/tools/google_get_device_performance/execute

Request

  • Base URL: https://adako.ai
  • URL: https://adako.ai/api/v1/tools/google_get_device_performance/execute
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Optional 8-128 character key. A successful envelope is cached for 24 hours; replaying the key with the same arguments returns it again with Idempotent-Replayed: true, and replaying it with different arguments answers 409.

Request body

Response

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

successunknown required
toolstring required
dataobject required

Machine-readable result.

markdownstring required

The same result written for a person or a model.

proposal_idstring

Present for writes. Nothing changes on the ad platform until it is approved.

approve_urlstring

Where a person approves the proposal.

request_idstring required

Changes

No recorded changes to this operation across all 1 revision of this API.