Best Microsoft Ads Account Audit Settings

The best Microsoft Ads account audit settings are the ones that make the account's identity, authority, measurement, structure, and delivery boundaries explicit. Start with account currency and time zone, then review users and billing, UET and conversion goals, account and campaign organization, network and location behavior, import settings, budgets, bids, and the evidence that campaigns can serve as intended.

There is no universal “perfect” Microsoft Advertising configuration. Microsoft says an account's currency affects billing and cannot be changed after setup; its time zone controls the account and campaigns, and changing it can affect reporting and daily spend patterns. Those settings deserve a careful audit before a campaign review because a wrong scope can make every later metric misleading. This article is educational guidance, not a guarantee of platform performance or account-specific legal, financial, privacy, or compliance advice.

What should a Microsoft Ads account audit check first?

An account audit should answer five questions before it recommends a campaign change:

Identity: Is this the correct account, business, market, currency, and time zone?
Authority: Can the right people access, edit, approve, and pay for it?
Measurement: Are UET, conversion goals, consent, values, and scopes defined and tested?
Structure: Do campaigns, ad groups, products, locations, languages, budgets, and naming reflect real decisions?
Delivery: Can the intended ads reach the intended audience with an approved budget and a usable landing page?

Record the setting, current value, expected value, evidence, owner, and impact of a change. The goal is a reproducible account review, not a collection of platform defaults that someone labels “best.”

Check the account boundary before the campaign data

Microsoft Advertising has a manager-account layer above accounts, campaigns, and ad groups. Microsoft's account-organization guidance explains that accounts hold settings such as currency, time zone, payment arrangement, primary payment method, and users. Confirm that the audit is operating in the intended account and not a neighboring client, market, test, or former account.

Capture the account name, account number, manager relationship, business owner, billing country or region, website, market, and primary contact. If the account is part of an agency or multi-brand structure, document who owns the account and who is allowed to approve a change. A clean campaign report from the wrong account is still a failed audit.

Which Microsoft Ads account settings deserve the closest review?

Confirm currency before interpreting cost or changing accounts

Microsoft's currency guidance says the account currency is selected when the account is created and cannot be changed afterward. If the wrong currency was selected, Microsoft directs advertisers toward creating a new account and importing the campaign information. That makes currency an account-creation decision, not a routine reporting preference.

Verify the currency against the approved billing and reporting model. Check that budgets, bids, conversion values, revenue imports, invoices, and internal reports use the same interpretation. A currency symbol in a dashboard is not enough evidence: confirm the account setting and the source of any imported value.

Do not silently convert an account's historical costs into another currency and then compare them with native account values. If a business needs a management-currency view, document the exchange-rate date, method, and owner while preserving the original account currency. If a new account is required, treat the import as a migration with a separate QA record.

Review account time zone and reporting consequences

Microsoft's time-zone documentation says the account time zone is the default for campaigns and that changing it switches the campaign time zone as well. Microsoft also warns that the change can affect the apparent amount of spend in a day and recommends monitoring while reporting settles. That is a reason to audit the setting, not a reason to change it casually.

Confirm that the time zone matches the business's reporting owner, billing interpretation, schedules, daily budget review, and historical reporting. When a business operates across markets, distinguish account reporting time from customer-local targeting or scheduling behavior. Do not assume that changing the account time zone is a harmless way to make a report align with a local office.

If the time zone is wrong, document the before and after values, the date of change, affected reports, budget boundaries, schedules, automated rules, imports, and the people who approved it. Reconcile the transition rather than treating the first post-change day as directly comparable with the previous series.

Audit user access and approval ownership

List every user, manager relationship, role, last-known owner, business email, and reason for access. Remove former staff or agencies according to the organization's access process, and ensure at least one responsible owner can administer billing, tags, campaigns, and recovery. Avoid sharing a login when individual access and an approved role can provide accountability.

Separate the ability to view, edit, publish, manage billing, manage users, and approve changes where the organization's risk model requires it. A user audit is not complete if it checks only whether someone can sign in; it should show who can make an irreversible or expensive change and how that change is reviewed.

Keep the access record outside the article or campaign notes if it contains personal or security-sensitive information. The audit should record the control and its owner, not expose credentials, recovery codes, payment details, or unnecessary personal data.

Verify billing and payment readiness

Check billing country or region, payment arrangement, payment method, account balance or invoice status, tax or business details, spending limits, and the contact responsible for payment issues. Confirm that the payment method is authorized for the intended account and that a campaign pause caused by billing failure has an owner and an escalation path.

Do not infer that a campaign is ready because it is enabled. A billing hold, missing business verification, policy review, disapproved ad, or payment issue can prevent delivery. Record the status and the evidence that supports it, then separate billing blockers from optimization suggestions.

Confirm the site and tracking ownership

Identify the website, landing-page owner, tag owner, consent owner, analytics owner, CRM or order owner, and person who can test a conversion. A Microsoft Ads account audit should not recommend a new goal if no one can verify the page event or reconcile it with the business record.

Microsoft's UET setup guidance says advertisers need a Universal Event Tracking tag on the website before using conversion tracking or remarketing. Check which UET tag is installed, where it is deployed, whether it covers the intended pages, how consent is handled, and whether the tag ID is the one associated with the account's goals.

Which Microsoft Ads tracking settings should an audit verify?

Tracking settings should explain what happened after an ad interaction and whether the event is suitable for optimization. A goal can be technically active and still be unsuitable if it counts the wrong page, uses the wrong UET tag, has the wrong account scope, reports a misleading value, or is excluded from the conversion column used by bidding.

Test UET on the intended pages

Confirm that the UET tag fires on the pages that matter, including the landing page, product or service page, form, booking flow, cart, checkout, confirmation, and any post-conversion route the business has approved. Check the tag ID in the site implementation against the ID shown in Microsoft Advertising. Test both the normal path and relevant redirects, consent states, subdomains, and browser experiences.

Microsoft's UET dashboard documentation describes a Test tab for checking data received by a tag. Use the platform test together with a business-side test: a tag event arriving in Microsoft does not prove that the correct form submission, accepted order, appointment, or qualified lead was recorded.

For visitors in the European Economic Area, the United Kingdom, or Switzerland, confirm the site's approved consent implementation and how consent signals are transmitted to UET. Do not collect or send more personal data than the business and its privacy process permit. Record the consent owner and the implementation version without putting identifiers or sensitive values in the audit report.

Review goal scope and optimization inclusion

Microsoft's conversion-tracking explanation says UET is required for website conversion tracking and that a goal must be selected for inclusion in “Conversions” if it is to optimize campaign performance. Events excluded from that column may still appear in “All conversions,” so the audit should state which column is being used for reporting and bidding.

For each goal, record:

goal name, owner, account scope, UET tag, event definition, and page or parameter condition;
count rule and whether repeated actions from one ad interaction should count separately;
conversion window, attribution method, and the date those settings changed;
value, currency, transaction identifier, and whether the value is gross, adjusted, or imported;
inclusion in “Conversions” versus “All conversions”; and
the business stage represented by the event, such as lead, qualified lead, accepted order, or purchase.

Do not promote every micro-event into the optimization column. A product view or button click may help diagnose a page, but it may not be the outcome the account should buy. Conversely, a valuable offline or qualified outcome should not be omitted from the review simply because it requires a different import or reconciliation process.

Check conversion windows and attribution against the buying cycle

Microsoft documents a conversion window as the period after a user completes an action during which the platform records conversion data for a goal. The appropriate window depends on the business's decision cycle, not on a generic default. Compare the chosen window with lead follow-up, sales acceptance, subscription renewal, order confirmation, or other approved outcome timing.

Avoid changing the window and attribution method at the same time as a bid strategy, landing page, campaign structure, or tracking implementation. Annotate the change and preserve the prior definition so a later conversion-rate movement is not mistaken for a campaign improvement.

Reconcile platform conversions with the source of truth

For lead generation, compare goal events with submitted forms, answered calls, booked appointments, qualified records, duplicates, spam, and rejected or unserviceable contacts. For ecommerce, compare events with accepted orders, transaction IDs, currency, refunds, returns, cancellations, and fulfilled revenue. For subscriptions or applications, define the stage that represents real value and the owner who confirms it.

If the account reports conversions but the business record does not, classify the discrepancy before changing settings. Common causes include duplicate tags, confirmation-page reloads, missing consent, cross-domain transitions, phone or CRM disconnects, incorrect UET IDs, wrong goal scope, time-zone differences, and a value or currency mapping error.

How should campaigns and account structure look after an audit?

The account structure should match the decisions the owner needs to make. Naming is useful only when it helps a person locate a campaign, understand its scope, and compare its results without opening every setting.

Keep account, campaign, and ad-group responsibilities distinct

Use the account for identity, currency, time zone, access, billing, and shared measurement ownership. Use campaigns for meaningful delivery boundaries such as market, product or service line, budget, network, goal, or business objective. Use ad groups for tightly related queries, ads, products, or themes that share a landing-page and messaging decision.

Avoid splitting campaigns for labels that do not change budget, targeting, measurement, or approval. Also avoid putting unrelated products or markets in one campaign merely because their names fit a spreadsheet. The right level is the level at which the business can make and evaluate a distinct decision.

Audit naming and status conventions

Document a naming convention that identifies market, product or service, campaign surface, objective, and lifecycle state without embedding fragile information that will become false. Check whether active, paused, deleted, draft, limited, disapproved, and ended entities are being included or excluded from reports.

Do not treat a paused campaign as evidence that its historical settings were removed. Review status filters before concluding that an account contains no legacy keywords, ads, locations, or conversion paths. Keep the status rule in any exported audit so another person can reproduce the result.

Check network, language, location, and device boundaries

Confirm where ads are eligible to show, which languages and locations are selected, whether location intent matches the business's service or shipping boundary, and how device adjustments or targeting choices are applied. Record the difference between a person physically located in a market and a person showing interest in it when the platform exposes those choices.

Review exclusions and expansions with the same care as positive targeting. An account may appear well targeted while reaching people outside a service area, shoppers who cannot receive the product, or queries that cannot be handled. A targeting setting is correct only relative to the business promise and operational capacity.

Match budgets and bidding to measurement readiness

For each campaign, record budget type, current budget, shared-budget membership, bid strategy, bid limits or targets, conversion goal set, and the business outcome expected from it. Check whether the strategy's inputs are present, stable, and aligned with the campaign route. Do not recommend an automated strategy merely because the control is available.

If the account has a small or changing data set, describe the uncertainty rather than inventing a sample threshold. A campaign can spend efficiently against the wrong event if the goal is not qualified, and a campaign can appear weak when the site or tag is broken. Fix the measurement and delivery boundary before interpreting bid results.

Review ads, assets, and landing pages together

Check that ad text, images or assets where applicable, final URLs, tracking parameters, product or service claims, prices, offers, availability, policies, and page content agree. Test mobile and desktop paths, redirects, page errors, form submissions, phone links, checkout, and consent behavior.

An enabled ad is not a ready ad. Policy review, missing assets, destination errors, business verification, billing status, or a mismatch between the ad and page can change delivery. Record the actual blocker and owner instead of placing a generic “optimize ad” note in the audit.

What should an audit check in Microsoft Ads imports?

Import can save setup time, but it is a migration process rather than proof that the Google Ads account and Microsoft Advertising account are equivalent. Microsoft says import options can change budgets, bids, bid strategies, statuses, conversion goals, locations, and other entities, and that some Google Ads items require special review.

Set the import scope before running it

Microsoft's Import campaigns directly from Google Ads guidance describes quick and customized import flows. Before running an import, record the source account, destination account, selected campaigns, entities, currency handling, schedule, status handling, budget and bid adjustments, and any UET or conversion-goal association.

Do not use a recurring import schedule until the owner understands what a later run can update, pause, remove, rename, or overwrite. A one-time import and a synchronization schedule have different operational risks. Keep the import name, owner, approval, and rollback or pause procedure in the audit record.

Review currency and unsupported settings

If the source and destination currencies differ, the import flow may offer conversion or allow the advertiser to opt out and adjust bids and budgets. Review the converted values before enabling campaigns. Never assume that a numerically identical budget means the same spending boundary in a different currency.

Microsoft's documentation on what gets imported notes that not all information is imported and that entities can be skipped or mapped when settings are unsupported. Check campaign and ad-group statuses, locations, demographics, networks, ad formats, audiences, product data, conversion goals, bids, budgets, and final URLs after the import rather than accepting the completion message as QA.

Treat imported conversion goals as a separate validation

An imported goal may have a name, value, attribution method, or scope that looks correct but still points to the wrong tag or event in the destination account. Confirm the UET tag, goal type, account scope, inclusion in “Conversions,” window, attribution, value, and source-of-truth reconciliation in Microsoft Advertising.

Do not assume Google Analytics goals, hosted conversions, custom events, or data-driven attribution map exactly to a Microsoft Advertising goal. If the import documentation identifies an unsupported or transformed item, record the transformation and recreate or adjust it only after the destination measurement owner approves it.

Review imported statuses before spending

Search active, paused, deleted, and otherwise non-active statuses after an import. Confirm that unsupported locations did not expand the campaign beyond the intended market and that a campaign containing no supported targets did not remain eligible unintentionally. Check every imported ad, keyword, product, negative, extension or asset, landing page, and policy status that can alter delivery.

Start with the smallest approved scope that proves the destination setup works. Monitor the first reporting cycle, compare spend and conversion records, and pause or correct the import if the destination is not honoring the business boundary. This is a control decision, not a recommendation to use a particular volume or waiting period.

A practical Microsoft Ads account audit checklist

Use the following record for each audited account. Replace “pass” with evidence; a checkbox without evidence is not a completed audit.

Account identity: account number, manager relationship, business, website, market, billing country, owner, and audit date.
Currency: native account currency, billing interpretation, conversion-value currency, reporting currency, and any migration risk.
Time zone: account time zone, campaign alignment, schedule interpretation, reporting owner, and documented changes.
Access: users, roles, manager links, billing authority, admin owner, former-user review, and approval path.
Billing: payment method, payment status, invoicing or prepay arrangement, tax or business details, and escalation owner.
UET: tag ID, pages covered, test evidence, consent behavior, tag owner, and discrepancy status.
Conversion goals: event definition, scope, UET tag, inclusion column, window, attribution, count, value, currency, and source-of-truth match.
Structure: campaign and ad-group boundaries, naming, status filters, network, language, location, device, budget, bid strategy, and goal set.
Destination: ad or asset, final URL, page content, form or checkout, mobile path, policy status, tracking parameters, and operational promise.
Import: source, destination, selected entities, currency treatment, mapping warnings, schedule, owner, post-import QA, and pause procedure.
Decision record: issue, severity based on business impact, owner, smallest corrective action, evidence needed, and condition for closure.

When a report cannot answer one of these items, describe it as an open evidence gap. Do not fill a missing value with a presumed default or call the account healthy because the interface did not show an error.

Common Microsoft Ads account-audit mistakes

Treating defaults as best settings

A default time zone, bid strategy, import option, conversion window, or network setting may be convenient but is not automatically right for the business. State the account requirement and test the setting against it.

Changing currency or time zone to fix a report

Currency is not a cosmetic display preference, and time-zone changes affect account and campaign reporting context. Fix the reporting model or create a controlled migration plan instead of changing a foundational setting to make one dashboard look familiar.

Auditing campaign metrics before account scope

CTR, CPC, spend, conversion rate, and ROAS are not interpretable when the report uses the wrong account, currency, time zone, status filter, network, goal column, or attribution window. Verify scope first.

Counting UET activity as a verified conversion

A UET tag can receive events while the wrong event is being counted, consent is missing, the goal is scoped to another account, or the source record has no corresponding lead or order. Test the entire business path.

Importing Google settings without reviewing the destination

Microsoft and Google Ads have different capabilities, names, mappings, networks, locations, product requirements, and status behavior. An import completion message is not a campaign launch approval.

Giving every user broad access

Broad access increases the chance that a billing, tracking, import, or campaign change lacks an accountable owner. Match access to the work and retain a reviewable approval path.

Fixing every finding in one pass

An audit should identify what breaks the business contract and what evidence proves the repair. Changing currency, time zone, tags, goals, campaigns, bids, budgets, and imports together makes the outcome difficult to verify. Order the work by impact and preserve the before-state.

The bottom line for Microsoft Ads account audits

The strongest Microsoft Ads account audit begins with foundational settings: account identity, currency, time zone, access, billing, and website ownership. It then verifies UET, consent, conversion goals, attribution, values, structure, targeting, budgets, ads, pages, and imports. Each finding should name the current state, expected state, evidence, owner, and smallest action that closes the gap.

Use Microsoft's current documentation for settings that can change or have irreversible consequences, especially currency, time zone, UET, and imports. For a broader audit workflow, see the existing Google Ads audit tools guide and free audit guide for online stores; adapt their questions to Microsoft's account model rather than assuming the products behave identically.