Google Ads

Performance by hour and day of week

Splits performance by hour of day and by day of week, in the account timezone. This is the evidence a schedule decision needs. Use when: the user is thinking about dayparting, or asks when their ads perform best. Do not use when: there is little data. Splitting a month across 168 hour-and-day buckets leaves most of them empty, and acting on an empty bucket is how campaigns lose their best hours. Returns the hour-of-day table and the day-of-week table separately, because the full 168-cell grid is almost never readable or reliable. Hours are in the account timezone, which may not be the user's. Before recommending a schedule, check the bidding strategy: Smart Bidding already varies bids by time of day, so a schedule mostly removes volume rather than improving efficiency. 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_hourly_performance/execute

Request

  • Base URL: https://adako.ai
  • URL: https://adako.ai/api/v1/tools/google_get_hourly_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.