# Microsoft Ads campaigns

> Use campaign links and website call attribution to review calls from Microsoft Ads traffic. Explore the workflow with Lead Source.

Canonical page: https://getleadsource.io/use-cases/microsoft-ads/

For Microsoft Ads campaigns

## Keep search inquiries visible after the click.

Use campaign links and website call attribution to review calls from Microsoft Ads traffic.

[Explore the walkthrough](https://getleadsource.io/demo/)[See the workflow](https://getleadsource.io/use-cases/microsoft-ads/#workflow)

Microsoft Ads campaigns Illustrative journey

- 01 Source Microsoft search campaign

- 02 Conversation Visitor calls the website number

- 03 Next step Request and outcome reviewed

One inquiry. Its context stays connected.

[Your workflow](https://getleadsource.io/use-cases/microsoft-ads/#workflow)[What to reviewThe tools](https://getleadsource.io/use-cases/microsoft-ads/#review)[Common questions](https://getleadsource.io/use-cases/microsoft-ads/#questions)

Built around your day

### Start with the way you work.

An advertising report shows the visit. Your receiving team hears the request. Connect those parts of the journey so you can review search inquiries with the campaign information available for the visit.

01

#### Name campaigns for a useful review

Use consistent source and campaign information in the links you control. Make it clear which service or promotion the visit belongs to.

02

#### Test the website call journey

Check the landing page, displayed tracking number, and resulting call details. A tested path is more useful than assuming the setup works.

03

#### Compare relevant outcomes

Review calls alongside the requested service and the team's saved result. Use comparable periods when evaluating campaigns.

The question worth asking

### What kind of inquiry followed the search visit?

Keep the available source details with the conversation and recorded outcome. Review that evidence alongside the advertising platform's own reports.

Bring these details into the review

01 Campaign context

02 Website-to-call connection

03 Saved lead outcomes

The tools behind the workflow

### Bring the right details together.

[Website attribution & number swappingUse dynamic number insertion to connect website sessions, campaign information, and incoming calls.Explore feature](https://getleadsource.io/features/website-attribution/)[Call trackingSee which campaigns generate calls, then connect the source with the conversation and its outcome.Explore feature](https://getleadsource.io/features/call-tracking/)[Custom reports & CSV exportsFilter call and operational reports, then download results as a spreadsheet-ready CSV file.Explore feature](https://getleadsource.io/features/report-exports/)

Before you start

### A few useful details.

Fit the setup to your actual campaigns, receiving team, and follow-up process.

Does this include a native Microsoft Ads connector? +

No native connector is promised by this workflow. Campaign attribution through website tracking is separate from sending conversion events back to Microsoft Ads.

Can I compare this traffic with other sources? +

Yes. Use consistent campaign naming and review criteria so the reports compare similar kinds of inquiries.

[Explore all use cases](https://getleadsource.io/use-cases/)[Browse all features](https://getleadsource.io/features/)[Compare platforms](https://getleadsource.io/compare/)

Meet your next growth tool

### Let’s connect the dots on your calls.

Get an early look at Lead Source, built for the way your business handles calls.

[Explore the walkthrough](https://getleadsource.io/demo/)[Explore the platform](https://getleadsource.io/platform/)