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.
Use campaign links and website call attribution to review calls from Microsoft Ads traffic.
One inquiry. Its context stays connected.
Built around your day
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.
Use consistent source and campaign information in the links you control. Make it clear which service or promotion the visit belongs to.
Check the landing page, displayed tracking number, and resulting call details. A tested path is more useful than assuming the setup works.
Review calls alongside the requested service and the team's saved result. Use comparable periods when evaluating campaigns.
The question worth asking
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
The tools behind the workflow
Use dynamic number insertion to connect website sessions, campaign information, and incoming calls.
Explore featureSee which campaigns generate calls, then connect the source with the conversation and its outcome.
Explore featureFilter call and operational reports, then download results as a spreadsheet-ready CSV file.
Explore featureBefore you start
Fit the setup to your actual campaigns, receiving team, and follow-up process.
No native connector is promised by this workflow. Campaign attribution through website tracking is separate from sending conversion events back to Microsoft Ads.
Yes. Use consistent campaign naming and review criteria so the reports compare similar kinds of inquiries.
Meet your next growth tool
Get an early look at Lead Source, built for the way your business handles calls.