Microsoft Advertising Conversions API: A Measurement Plan for Service Businesses

Introduction

A form fill is not the finish line for a service business. It is only the start of the sales process.

A roofing company can receive ten forms and discover that half are outside its service area. A landscaper can record a low cost per lead while the office spends days chasing prospects who never answer. An HVAC campaign can look efficient in the ad platform even when the jobs that actually book came from somewhere else.

That gap matters because automated ad systems learn from the conversion signals advertisers send back. If every form, call, duplicate, solicitation, and wrong-service inquiry looks equally valuable, the platform has no reliable way to distinguish useful demand from noise.

On October 28, 2026, Microsoft Advertising announced that its Conversions API, or CAPI, is now generally available. Microsoft says CAPI creates a server-to-server path for sending website, CRM, offline, app, and customer-interaction events directly to Microsoft Advertising. It is designed to work alongside Universal Event Tracking, not automatically replace it.

For service businesses, the practical opportunity is straightforward: connect the ad click to the lead stages that happen after the website visit, including valid lead, qualified lead, booked estimate, and sold job. The goal is not to collect more data for its own sake. The goal is to give reporting and bidding a cleaner picture of the work the business can actually serve.

This guide gives roofers, landscapers, HVAC contractors, remodelers, tree-care companies, garage-door businesses, pest-control teams, and other local service companies a seven-step plan.

What Microsoft announced

Microsoft describes Conversions API as a server-side measurement solution that can accept website events, CRM events, offline sales transactions, and mobile events through one setup.

The October announcement says CAPI is generally available and can be implemented directly, through Google Tag Manager, or with supported technology partners. Microsoft says it can improve attribution coverage, reduce reliance on browser-only tracking, and provide additional signals for measurement and automated optimization.

Microsoft also recommends using CAPI with Universal Event Tracking, or UET, whenever possible. UET captures browser activity and page context. CAPI can add events and details from systems such as the CRM after the initial website visit.

This is not automatic proof of better campaign performance. The quality of the outcome depends on the events a business sends, whether attribution identifiers are retained, whether duplicates are prevented, whether consent is handled correctly, and whether the CRM stages reflect real sales activity.

Why this matters for service-business advertising

Most ad platforms can see a click and an on-site form submission. They cannot know by themselves whether the lead was in territory, requested a service the company offers, answered the phone, booked an estimate, or became a customer.

That information usually lives in the CRM, call-tracking system, scheduling platform, or dispatch workflow.

CAPI creates a path for returning approved events from those systems to Microsoft Advertising. A useful service-business event ladder might be:

• Lead submitted
• Valid lead
• Qualified lead
• Estimate or appointment booked
• Sold job
• Disqualified, with a reason retained in the CRM

The final item is for internal analysis. Do not send every internal field or personal detail to an ad platform. Decide which approved conversion events are necessary, permitted, and useful.

A seven-step Microsoft Advertising CAPI plan

1. Define the business outcomes before the technical setup

Start with the stages the sales team can apply consistently.

A simple definition set might be:

• Valid lead: A real person with reachable contact information asking about a service.
• Qualified lead: The requested service, property type, location, and timing fit the company's rules.
• Booked opportunity: An estimate, inspection, consultation, or service appointment is on the calendar.
• Sold job: The customer accepted the work under the business's normal sales process.

Write the definitions in plain language. Include disqualification reasons such as outside service area, wrong service, duplicate, job seeker, vendor solicitation, spam, unreachable, and project not currently served.

Do not build server-side tracking around stages employees do not update. A complicated event map with inconsistent CRM data will create precise-looking reports that cannot be trusted.

Choose one primary optimization event only after checking volume and reliability. A smaller business may need to report qualified leads while using booked opportunities as an evaluation metric. Do not force a rare sold-job event into automated bidding if it arrives too slowly or inconsistently for a useful learning signal.

2. Map each event to a real system action

For every event, identify:

• The system where it begins
• The exact action that creates it
• The employee or automation responsible
• The timestamp
• The unique event or transaction ID
• The lead or customer record it belongs to
• The approved value, if the business uses conversion values
• The owner who resolves errors

Examples: Lead submitted may begin when the website successfully creates a lead record. Qualified lead may begin when an employee changes the CRM status after review. Booked opportunity may begin when the scheduling system confirms an appointment. Sold job may begin when the CRM marks the opportunity won.

Do not trigger a booked-opportunity event from a calendar page view. Trigger it from the confirmed scheduling action. Do not trigger qualified lead when a form contains a preferred ZIP code if no one has verified the project is a fit.

Microsoft's implementation guidance supports custom events and recommends real-time delivery. For service businesses, accuracy matters more than sending an event a few seconds earlier.

3. Keep UET and capture the Microsoft Click ID

Microsoft recommends pairing CAPI with UET whenever possible.

UET records browser activity and supplies page context. CAPI adds the server-side path. Together, they can connect the website visit with later events from the CRM or scheduling system.

Enable Microsoft Advertising auto-tagging where appropriate so the landing-page URL can include the Microsoft Click ID, called msclkid. Microsoft's CAPI documentation says advertisers should capture the most recent msclkid and associate it with subsequent events when available.

A practical flow is:

• A person clicks a Microsoft ad.
• Auto-tagging adds msclkid to the landing-page URL.
• The website retains that click ID using an approved first-party or server-side method.
• The form or call record passes the ID into the CRM when possible.
• Later approved events use the same record and identifier for attribution.

Test this across mobile and desktop, multiple landing pages, forms, call flows, redirects, and scheduling handoffs. A click ID that disappears before the lead reaches the CRM cannot help connect later outcomes to the campaign.

Do not treat CAPI as permission to ignore browser consent, privacy notices, or the platform's data rules.

4. Prevent double-counting

The same form submission may be visible to both UET and CAPI. If both systems report it without a shared deduplication value, one customer action can appear as two conversions.

Microsoft recommends using the same stable eventId, compatible eventName, and UET tag ID when the same conversion is sent through UET and CAPI.

Create the event ID once at the source of the action. Store it with the lead record. Reuse it when the same event is sent through both paths.

Test:

• One form submission produces one reported conversion.
• Refreshing the thank-you page does not create a second conversion.
• Retrying a server request does not create a second conversion.
• A CRM status change sends only the intended event.
• Reversing or correcting a lead follows the approved adjustment process.
• Test leads remain identifiable and do not contaminate production reporting.

Deduplication should be part of the design, not a cleanup task after bidding has already learned from inflated data.

5. Set consent, privacy, and data rules before launch

Server-to-server does not mean rule-free.

Microsoft's CAPI documentation supports an adStorageConsent field and says events marked denied are not used for advertising purposes, including conversion attribution and retargeting. Microsoft also says identifiers such as email and phone should be hashed where used and permitted.

Before implementation:

• Confirm the website's privacy and consent language is accurate.
• Decide which events and identifiers are necessary.
• Send only data allowed by platform policy, applicable law, and the business's consent process.
• Do not send sensitive job notes, diagnosis details, payment data, private messages, or unnecessary personal information.
• Limit access to API tokens and server-side configurations.
• Document data retention and deletion responsibilities.
• Review regional requirements with qualified counsel when needed.
• Test denied-consent behavior as well as granted-consent behavior.

The business remains responsible for the data it sends. A marketing measurement project should not quietly become an uncontrolled customer-data export.

6. Validate the full lead journey

Microsoft's readiness checklist calls for account access, a UET tag ID, a CAPI authentication token, conversion goals, a consent approach, identifiers, and validation owners.

Build a test sheet that covers the whole journey:

• Ad click and landing-page arrival
• msclkid capture
• Form or tracked-call creation
• CRM record creation
• Valid-lead review
• Qualified-lead status
• Appointment booking
• Sold-job status when practical
• UET event receipt
• CAPI event acceptance
• Event ID and name consistency
• Deduplication
• Consent value
• Timestamp and time zone
• Conversion goal mapping
• Reporting delay
• Error logging and retry behavior

Use test records with clearly labeled names. Confirm that events appear in the correct account and conversion goal. Compare platform counts with CRM records over a reasonable validation window.

Do not switch bidding to a new event on launch day. Let the business verify data quality and volume first.

• Build a controlled Microsoft Advertising test

7. Use a qualified-lead scorecard

CAPI should improve business decisions, not merely raise the conversion count.

Review these metrics weekly:

• Spend
• Clicks
• Raw leads
• Valid leads
• Qualified leads
• Booked estimates or appointments
• Sold jobs when the sales cycle allows
• Cost per raw lead
• Cost per qualified lead
• Cost per booked opportunity
• Qualification rate
• Booking rate
• Sales rate
• Revenue or approved value when reliable
• Top disqualification reasons
• Percentage of leads with msclkid retained
• CAPI event acceptance and error rate
• Duplicate-event rate
• Time from lead creation to stage update

Read the scorecard from the bottom of the funnel upward. If raw lead cost falls while qualification and booking rates weaken, the campaign is not necessarily improving.

Change one major variable at a time when practical. Preserve a stable baseline before changing the bidding goal, campaign structure, targeting, and landing page together.

• See the qualified-lead framework for service businesses

A practical event map for a local service company

Use an event map such as:

• lead_submitted: Triggered after a lead record is successfully created.
• qualified_lead: Triggered after a trained employee confirms service, territory, property, and timing fit.
• appointment_booked: Triggered after the scheduling system confirms an estimate, consultation, or service appointment.
• job_won: Triggered after the CRM records an accepted job, if the timing and data quality support it.

For each event, record the system of truth, event owner, unique ID, timestamp, consent state, approved identifiers, conversion goal, and validation method.

The event names above are planning examples. Match the final implementation to Microsoft Advertising's current field requirements and the business's own CRM structure.

When to start, and when to wait

A business may be ready when:

• UET is installed and validated.
• Auto-tagging and click-ID retention work.
• The CRM records source and lead stages.
• Staff apply qualification rules consistently.
• Consent and privacy processes are documented.
• Someone owns monitoring and error resolution.
• The campaign has enough stable activity to evaluate the new signals.

Wait when:

• Forms or calls regularly fail to reach the team.
• Staff do not update lead stages.
• No one can define a qualified lead.
• Tracking produces duplicate conversions.
• The privacy policy or consent flow is unclear.
• The CRM cannot retain attribution fields.
• The business expects CAPI to repair poor campaign strategy or weak sales follow-up.

CAPI can strengthen the measurement connection. It cannot create clean operations that do not exist.

What to do this week

• Write definitions for valid lead, qualified lead, booked opportunity, and sold job.
• Pull 30 recent leads and check whether the CRM stages are complete.
• Confirm UET is installed and test the primary website conversion.
• Turn on or verify Microsoft auto-tagging where appropriate.
• Check whether msclkid reaches the CRM.
• List the systems that create qualification, booking, and sale events.
• Choose a direct API, partner, or server-side tag-manager path.
• Assign one technical owner and one business-data owner.
• Build a test plan before changing campaign optimization.

Work with Backyard Marketing

Reliable advertising starts with a lead system that follows the customer past the click.

Backyard Marketing helps service businesses connect campaign strategy, landing pages, lead tracking, and practical reporting around the outcomes that matter: qualified opportunities and booked work. If your reporting stops at forms and calls, we can help you map the next measurement step without losing sight of the day-to-day sales process.

• Talk with Backyard Marketing about your lead system

Sources

• Microsoft Advertising, “Build, steer, and measure your campaigns with AI: What's new in Microsoft Advertising this October” (October 28, 2026)
• Microsoft Learn, “Conversions API (CAPI) - Microsoft Advertising API”
• Microsoft Advertising Help, “FAQ: Universal Event Tracking”
• Microsoft Advertising Help, “How does conversion tracking work?”