# Microsoft Ads Conversions: Goals, Revenue and Deduplication

> Choose meaningful conversion goals, counting, revenue and duplicate controls before automated bidding relies on them.

Source: https://mentionx.ai/learn/microsoft-ads/microsoft-ads-conversion-goals-revenue-deduplication  
Author: Dipuck Jones, founder of MentionX  
Updated: 8 November 2026  
Level: Practitioner

**A Microsoft conversion goal is an optimisation contract: what action qualifies, how often it counts, what value it carries and whether bidding should use it. Reliable reporting also requires explicit duplicate handling rather than assuming that a purchase name or Unique setting solves every identity problem.**

> **Key takeaways**
> - Distinguish business actions, event sources, goal definitions and attributed outcomes.
> - Include in Conversions affects ordinary conversion reporting and automated bidding inputs.
> - Counting All versus Unique is different from the All conversions report column.
> - Browser duplicates, offline duplicate keys and UET-plus-CAPI deduplication need different controls.

*Checked 8 November 2026 (CET) against Microsoft conversion, goal-type, enhanced-conversion and CAPI documentation. Goal-design advice is editorial judgement. Ledgerline's actions, values and test records are fictional and illustrative.*

## Which business actions deserve goals?

Start with the actions that represent meaningful progress for the business. A storefront purchase, a qualified bulk-order enquiry and a newsletter subscription can all be measurable, but they should not automatically have equal optimisation priority.

Create an outcome map with business meaning, system of record, event source, goal type, counting, value and intended use. The system of record establishes whether the action happened. Microsoft attribution establishes whether the action receives credit under the platform's configured rules. Those are related but different questions.

Use observational goals for useful diagnostics that should not drive acquisition decisions. A product view or basket addition can reveal funnel behaviour without being treated as equivalent to a completed order. A low-friction event can become an attractive optimisation shortcut if it is included indiscriminately.

The [Google primary-and-secondary lesson](https://mentionx.ai/learn/google-ads/google-ads-conversion-goals-primary-secondary) explains the transferable need to separate optimisation and observation. Microsoft uses its own goal settings and reporting terminology; do not assume Google's labels and exceptions map one to one.

## How should you choose the goal type?

Microsoft documents destination URL, event, duration and pages-viewed website goals, along with app and offline routes. Particular goal categories and features can have different availability. Product, store-visit or in-store-transaction options should not be assumed available to every advertiser.

A destination-URL goal can work when a reliable confirmation page represents the action. Review matching conditions carefully. A broad rule may include failure or support pages, while a narrow rule may miss valid URL variations. Test both qualifying and non-qualifying examples.

An event goal needs a corresponding UET event and matching conditions. Creating the goal does not install the event. A GA4 purchase event also does not automatically become a Microsoft event with correct revenue. Inspect the actual destination and parameters.

Traditional offline goals use a separate import architecture and do not require browser UET merely to exist. Choose the type that reflects the real action and available evidence, not the type that happens to be easiest to create in the interface.

## What does Include in Conversions change?

Microsoft allows goals to be included in the Conversions columns. Its documentation explains that clearing this setting removes those ordinary goal outcomes from automated bidding calculations and leaves them available through All conversions reporting.

Review campaign-specific goal selections as well as account-level definitions. A sensible account catalogue does not guarantee that a particular campaign is optimising to the intended subset. Record the actual relationship between the campaign and its goals.

| Illustrative action | Proposed role | Required review |
| --- | --- | --- |
| Confirmed online purchase | Candidate bidding outcome | Valid value, counting and duplicate controls |
| Qualified office enquiry | Candidate for a separate lead programme | Reliable CRM definition and feedback cadence |
| Basket addition | Diagnostic observation | Must not silently compete with purchases |
| Newsletter subscription | Retention or diagnostic context | Separate permission and commercial interpretation |

Microsoft documents a view-through reporting exception where that feature is available: Include in Conversions does not govern view-through columns in exactly the same way. Review those metrics separately rather than extending the ordinary click-conversion rule to every reported measure.

Changing goal inclusion is a substantive optimisation change. Keep the rationale, date, affected campaigns and expected feedback implications. A cleaner report is not a sufficient reason to alter bidding inputs without commercial approval.

## How do All and Unique counting differ?

The counting choice concerns how qualifying outcomes are counted in relation to an ad click and goal. Unique does not mean one person for life, one household or one verified customer. It is not a fraud filter or a universal order-deduplication mechanism.

For purchases, counting multiple genuine orders can be appropriate if the business wants those outcomes represented. For enquiries, repeated submissions from one click may not represent additional value. Choose based on the business action, then verify the current documented behaviour and actual goal setup.

Do not confuse the All counting option with the All conversions report column. A goal can have a counting rule and also be included or excluded from ordinary Conversions reporting. These are separate dimensions, and a spreadsheet should record both.

Test repeats deliberately. A page refresh, a duplicate integration and two genuine purchases are different cases. If all three produce the same observed pattern, the implementation may not distinguish business events well enough for the chosen goal.

## What should revenue mean?

Agree a value basis with finance. Options such as fixed value, variable value or no value have different uses. For a storefront, actual order values may be useful, but tax, shipping, discounts, cancellations and refunds need an explicit treatment.

Event value and revenue are not interchangeable merely because both are numeric. Verify the field Microsoft uses for conversion revenue and the currency supplied. A variable-value goal with a fallback can hide missing payload data if the report still shows a plausible default amount.

Microsoft can express reported values in the account currency, but currency conversion does not correct an inconsistent financial definition. A tax-inclusive order and a tax-exclusive order remain different bases even after both are shown in euros.

For qualified leads, label expected values as estimates and avoid stacking full sale value at every stage. In an illustrative Ledgerline journey, a raw enquiry, qualified enquiry and won bulk order may all concern one opportunity. Counting each as an independent full-value sale inflates the optimisation signal and business report.

## Where do duplicate controls belong?

For browser UET, do not assume the platform automatically removes every duplicate, test event or overlapping goal. Duplicate installations, repeated triggers and multiple goals matching one action can inflate results. Prevent these at the event and goal-design layers.

Microsoft's current CAPI guide documents browser-and-server deduplication using compatible events with the same UET tag context and stable event identity. This is a specific mechanism, not proof that all browser events across every integration automatically deduplicate.

Traditional offline imports have their own duplicate key involving click ID, goal name and conversion time. Reuploading the same logical outcome with a different timestamp can create a different record rather than a harmless retry. Preserve the original business identity and timestamp.

Keep identifiers distinct. A click ID links an advertising interaction, an event ID supports a particular event's identity and a transaction identifier can support commerce or adjustment workflows. One field should not be casually substituted for another because all look like strings in a table.

## How should scope, windows and attribution be reviewed?

Review the account or manager scope of the goal and tag relationships. Broad sharing can be useful for a legitimate multi-account design, but it can also create attribution confusion across sites. Select the scope deliberately and verify any settings that cannot later be changed freely.

Record click and any relevant view windows, counting, configured attribution model and report date basis. Microsoft's documentation contains different model references in different contexts, so do not teach that every account uses only last-click attribution. Inspect the actual supported configuration.

A change in windows or model can alter reported credit without changing business orders. Preserve the change date and avoid comparing periods as though the measurement definition were constant. This is particularly important when judging a bid strategy after a goal migration.

Test corrections and refunds with the actual supported route. Online adjustment availability, traditional offline adjustments and CAPI transaction workflows have different requirements. Do not promise that every account can restate every historical event through one generic button.

> **Pro move:** Add separate columns for counting rule, reporting inclusion, campaign selection and duplicate mechanism. Combining them into one “primary conversion” label hides four independent decisions.

## How should a goal migration be governed?

Treat a move from one purchase source to another as a measurement release. Compare the proposed source with the current one under an approved observational arrangement before making it the optimisation authority. Keep test outcomes controlled and avoid including two representations of the same purchase in bidding merely to make comparison easier.

Write a cutover record with affected campaigns, old and new goal identities, counting, value basis, scope and expected reporting differences. Preserve historical interpretation rather than renaming a goal so broadly that readers cannot tell when its source changed.

After the authorised switch, review mature outcomes and the reconciliation ledger. A temporary difference may reflect lag or attribution, while a persistent value shift may indicate a changed financial basis. The business should be able to reverse a defective migration without inventing new transactions or losing the audit trail of what the bidding system was told.

## Worked example: Ledgerline

Ledgerline's illustrative purchase report includes a destination-URL goal and an event goal for the same order. Both are included in Conversions, and the commerce app and tag manager can each send the event. The team initially considers switching to Unique as a complete fix.

Review shows that the real issue spans event duplication and overlapping goal definitions. The team chooses an authoritative purchase signal, defines repeat-order handling and checks the value basis. It leaves basket actions observational and creates a separate qualified-enquiry design for bulk orders.

### Walkthrough

1. Map each business action to its system of record and event source.
2. Inspect goal type, matching conditions, scope and campaign selection.
3. Record counting separately from Include in Conversions.
4. Compare purchase value and currency with the agreed business basis.
5. Test refreshes, duplicate integrations and genuine repeat purchases.
6. Verify the specific duplicate mechanism for browser, offline or CAPI routes.
7. Document any goal migration and a reconciliation period before changing bidding reliance.

The example does not claim that every discrepancy is a duplicate. Consent, attribution, timing and business definitions must still be considered.

## Common mistakes

Using Unique as a universal deduplication or fraud solution overstates its role. Using All conversions as if it meant every business order confuses a platform column with the system of record. Both can distort acquisition decisions.

Another mistake is allowing an estimated fallback value to hide missing revenue parameters. Finally, avoid reporting raw enquiries and won sales as additive independent revenue when they are stages of the same opportunity. Measurement should represent the business process, not reward the number of events configured.

## Try it yourself

Build a goal catalogue with action, source, type, scope, conditions, counting, reporting inclusion, campaign use, value basis, currency and duplicate mechanism. Use fictional records and leave live settings unchanged.

Create four test cases: one valid purchase, one refresh, one genuine repeat order and one overlapping goal. State the expected result at event, goal, attributed-report and business-record levels. Then identify which assumption would most affect bidding if it were wrong and assign an owner to verify it.

## Quick quiz

**1. Is the All counting option the same as the All conversions column?**

*Answer:* No. Counting and reporting inclusion are separate settings and should be documented separately.

**2. Does Unique provide universal order or fraud deduplication?**

*Answer:* No. Its counting scope is tied to the goal and advertising interaction, not a complete customer-identity or fraud system.

**3. Can a plausible fallback value hide missing revenue data?**

*Answer:* Yes. Inspect actual payloads and business records rather than assuming a non-zero report proves correct variable values.

## What should be approved before bidding relies on a goal?

Approve the business meaning, source, conditions, counting, value, scope and duplicate tests. Keep attribution and correction limitations visible so a clean-looking conversion total does not become false financial certainty.

Previous: [Microsoft Ads UET: Event Contracts and Layered Tracking QA](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-uet-events-tag-helper-qa) · Next: [Microsoft Ads Consent: Privacy Signals and Measurement Limits](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-consent-privacy-measurement)

Or return to the [Microsoft Ads for Marketers track](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-for-marketers).

Related: [Microsoft Ads Budgets and Bidding: Pacing With Reliable Goals](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-budgets-bidding-pacing) · [Microsoft Ads UET: Event Contracts and Layered Tracking QA](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-uet-events-tag-helper-qa) · [Microsoft Ads Offline Conversions, Enhanced Data and CAPI](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-offline-enhanced-conversions-capi)

## Common questions

**Is All counting the same as All conversions reporting?** No. Counting and reporting inclusion are separate dimensions. Record both along with campaign goal selection and the business action.

**Does Unique prevent all duplicate orders or fraud?** No. It is a goal counting rule tied to the advertising interaction, not a universal customer, order or fraud identity system.

**Does account-currency conversion fix inconsistent revenue?** No. Currency conversion does not reconcile different tax, shipping, discount, refund or value definitions. Agree the financial basis before interpreting return.

## Sources

- [How does conversion tracking work?](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_uetv2howctworks)
- [Conversion goals - Conversions versus all conversions](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_convsvsallconvs)
- [What are conversion goals and goal types?](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_uetv2ctgoaltype)
- [Enhanced conversions](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_uet_enhancedconversions)
- [Conversions API (CAPI)](https://learn.microsoft.com/en-us/advertising/guides/uet-conversion-api-integration?view=bingads-13)
- All accessed 8 Nov 2026 (CET).

## Frequently asked questions

### Is All counting the same as All conversions reporting?

No. Counting and reporting inclusion are separate dimensions. Record both along with campaign goal selection and the business action.

### Does Unique prevent all duplicate orders or fraud?

No. It is a goal counting rule tied to the advertising interaction, not a universal customer, order or fraud identity system.

### Does account-currency conversion fix inconsistent revenue?

No. Currency conversion does not reconcile different tax, shipping, discount, refund or value definitions. Agree the financial basis before interpreting return.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/microsoft-ads/microsoft-ads-conversion-goals-revenue-deduplication