Get Campaign UTMs
get_campaign_utmsRead one wizard campaign’s resolved UTM parameters by channel. Returns stored and resolved values, origin, and comparison with account defaults. An empty stored mapping inherits the account defaults, or platform defaults when the account has none. A stored mapping identical to its inherited default cannot be distinguished from inheritance. Dynamic tokens are resolved for lead records and ad URLs, not stored as literal text. Does not modify UTMs.
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.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes | Wizard campaign id (the `id` from list_wizard_campaigns). |