Get Account UTM Defaults
get_account_utm_defaultsRead the ACCOUNT-level UTM defaults - the tracking parameters every campaign channel inherits unless it stores its own.
KEYWORDS: utm, utms, utm_source, utm_medium, utm_campaign, utm_term, utm_content, tracking parameters, account default, defaults, inherited, placeholder, UPDATE ME
USE THIS TOOL WHEN THE USER ASKS:
- "What are our default UTMs?" / "What UTM settings does the account use?"
- "Which channels have customised UTM defaults?"
- As the baseline before judging whether a campaign overrides anything.
INHERITANCE RULE - READ BEFORE ANSWERING ANY UTM QUESTION:
UTMs are inherited, never blank. A campaign channel with an empty stored
mapping does NOT have "no UTMs" - it tracks with the account's UTM defaults,
and where the account set nothing it tracks with the Metadata platform default.
Roughly half of all channel rows in production are in that inherited state.
NEVER report "no UTMs configured" from an empty stored field: report the
resolved value and its origin.
ORIGIN IS PER CHANNEL, not per key: a channel with an empty stored mapping
inherits the account default whole, so a channel whose resolved mapping differs
at all from that is stored on the campaign and every one of its values is an
override. The per-key `same_as_default` flag says whether that one key happens
to match the default anyway.
ORIGIN VALUES:
- campaign_override: stored on this campaign channel, differs from what it would inherit.
- account_default: inherited from this account's UTM defaults.
- platform_default: inherited from the Metadata-wide default (account set nothing).
- not_set: the channel really has no UTM mapping (non-sponsored channels only).
HONEST LIMIT: a campaign that stores a mapping identical to the default it
would inherit is reported as inherited. The platform returns resolved values
with no provenance, so that case cannot be distinguished - say so rather than
claiming the campaign has no override.
TRACKING TIMING AND TOKEN MEANING:
Leads using server-resolved campaign UTMs use the current saved mapping when the platform processes them, without waiting for an ad republish. Captured URL or caller-supplied values can follow a different ingestion path, so do not generalize this timing to every new lead. Native click-time macros retain values captured from the lead's click URL. Ad click URLs have a separate publication timeline: a draft uses the saved mapping at launch, and launched ads use it on their next campaign publish. Saving a launched Microsoft Ads campaign triggers a live UTM push. AD_NAME is a dynamic token, not necessarily an individual ad name: standard experiments use their ad group name when present, otherwise their creative name; native ad structures use the native ad's own name. CAMPAIGN_NAME uses the wizard campaign name. Saving a launched campaign can also queue an asynchronous existing-lead UTM refresh. Do not assume historical rows are immutable or that all old rows have already refreshed. Verify the saved mapping with get_campaign_utms and actual lead values and ingestion timing separately from live ad click URLs; a supplied or backfilled lead creation date alone does not prove when its UTMs were resolved.
Takes no parameters - the account comes from the caller's credentials.
There is no cross-account lookup.
RESPONSE SHAPE:
{
"channels": {
"LINKEDIN": {"origin": "account_default", "values": {"UTM_SOURCE": "Acme", ...}},
"FACEBOOK": {"origin": "platform_default", "values": {"UTM_SOURCE": "Metadata", ...}}
},
"platform_default": {"UTM_SOURCE": "Metadata", "UTM_MEDIUM": "AD_CHANNEL", ...},
"notes": ["..."]
}
A channel reported as platform_default was never customised on this account; the
values shown are the ones campaigns actually inherit, not a blank.
READ-ONLY. No tool here edits the defaults (set_campaign_utms edits ONE campaign
channel's mapping, never the account defaults).Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||