List Entities

Lists the entities (campaigns, ad groups/ad sets, ads, keywords) of one connected ad platform with their IDs. platform: google_ads | meta (facebook/instagram) | tiktok | linkedin | microsoft | chatgpt_ads; when omitted, the only connected ad platform is used (platform_note says so) and with several or none connected the reply lists the connected services. entity: campaigns | ad_groups (adsets on Meta, adgroups on TikTok) | ads | keywords (Google Ads) | campaign_groups & creatives (LinkedIn). account = that platform's account id (customer_id also works for Google Ads); empty = the connected/default account. parent_id narrows children to one parent (the campaign id for ad groups/ad sets, the ad set id for ads). describe(platform) lists which entity names a platform accepts.

DATES: rows carry when each item was created, last changed and is scheduled to run, so new / still learning / untouched for months / changed yesterday is measured, not guessed. Google Ads: created_time (exact, Google keeps it 30 days), created_within_90d, updated_time (last 90 days; empty = unchanged for 90+ days), campaign start_time/end_time. Meta: created_time, updated_time, start_time/stop_time (campaign), start_time/end_time (ad set). TikTok: created_time, updated_time, ad group start_time/end_time. LinkedIn: created_time, updated_time, start_time/end_time (ISO, UTC). Microsoft: ad group start_date/end_date only (the API exposes no creation date). Before attributing a result to a change, compare these dates with the report period (get_report with start_date/end_date or a day breakdown).

Google Ads specifics (platform='google_ads'):

PAGING (all platforms): every matching row is kept. `limit` = rows in this response (no upper bound; 0 = as many as fit in one response, about 380 KB). `total_rows` is the full count; `serving_count` / `serving_summary` are computed over all rows. When has_more is true, call list_entities with page_token=next_page_token for the next rows (no credits, the account is not queried again); offset=next_offset also works. Keyword and ad rows are flat (one object per row).

CURRENT BIDS: ad group rows carry `max_cpc` (and `target_cpa` when set), keyword rows carry `max_cpc` plus `effective_max_cpc` and `bid_source`. A percentage change to a bid is relative to the current bid shown here; without it, a percentage would be sent as an absolute number and can LOWER the bid instead. `bid_source: AD_GROUP_CRITERION` means the keyword carries its own bid and OVERRIDES the ad group: raising the ad group bid then changes nothing for that keyword. Average CPC from a report is not a substitute — it is what was paid, not the ceiling that was set, and it is usually lower.

ACTIVE / RUNNING / LIVE = `is_serving: true` (derived from `serving_status`), NOT `status: "ENABLED"`. They are different things: a campaign whose end date has passed still reads status=ENABLED while the Google Ads UI shows it as "Ended". Which campaigns are active comes from is_serving; `serving_status` + `status_reasons` (ENDED, PAUSED, NOT_ELIGIBLE, MISCONFIGURED, PENDING...) account for the rest. status=ENABLED alone does not mean active; the Google Ads interface shows serving state. `serving_summary` gives the counts.

For campaigns it ALSO returns the bidding strategy (bidding_strategy), daily budget (daily_budget), targets (target_cpa / target_roas) and the max CPC ceiling (max_cpc, in account currency; null means no ceiling is set AT CAMPAIGN LEVEL). When max_cpc_note is present the campaign uses a portfolio strategy and max_cpc was not read.