Marketing happens when someone finds the time, so an automated campaign looks like relief. The system can adjust targeting, creative and bids continuously. It still needs a definition of success. This guide shows how to verify that definition before AI spends against the wrong event.

Automation cannot repair a weak conversion signal

Google defines Smart Bidding as auction-time strategies that use its AI to optimise for conversions or conversion value. Conversion tracking must be enabled before those strategies can work (Google Smart Bidding, checked: 2026-10-05).

The useful word is "conversion." A form submission, a click on a phone number and a signed agreement can all be recorded as events, but they do not mean the same thing to the business. If the platform receives only the first event, it cannot infer which enquiries later became real opportunities.

Google Ads marks conversion actions as primary or secondary. Primary actions enter the Conversions column and influence bidding when their goal is used for bidding. Secondary actions stay in All conversions for observation, except actions inside a custom goal, which can be used regardless of that label (Google primary and secondary actions, checked: 2026-10-05).

That setting is the first audit point. Ask which events are primary, where each originates and whether one occurrence corresponds to one business outcome.

More campaign decisions are moving into platform automation

Google started automatically moving Search campaigns with automatically created assets and campaign-level broad match into AI Max in September 2026. Dynamic Search Ads did not move on that date. Google postponed their automatic transition to February 2027 (Google AI Max migration update, checked: 2026-10-05).

After migration, a campaign that used automatically created assets gets search term matching and text customisation by default. A campaign with campaign-level broad match gets search term matching. Dynamic Search Ads are scheduled to receive search term matching, text customisation and final URL expansion during their later transition (Google AI Max migration update, checked: 2026-10-05).

AI Max can therefore extend queries beyond existing keywords, generate text from site and ad content, and choose a final URL. Advertisers retain controls such as negative keywords, brand inclusion or exclusion, locations of interest and URL rules. Reports expose an "AI Max" match type and a "Selected by" column for landing pages (Google AI Max controls, checked: 2026-10-05).

Meta is also consolidating Sales, App and Leads campaigns around Advantage+ audience, budget and placement automation. Its Marketing API no longer creates the older Advantage+ shopping and app campaign types from version 25.0, and version 26.0 blocks legacy campaigns that have not been migrated from editing (Meta Advantage+ campaigns, checked: 2026-10-05).

These changes do not make automation bad. They raise the cost of vague measurement. A practical marketing measurement system should define the signal before the platform receives more choices.

Prove the signal from the form to the platform

Name one outcome tied to revenue

Write one sentence: "We want the platform to optimise for..." Complete it with a business event, not a page view. A qualified enquiry, booked assessment or accepted order is easier to defend than a visit to the contact page.

Then trace the event backward. Where does the team record it? Who changes its status?

Which identifier connects it with the original enquiry? If the answer lives only in someone's inbox, the campaign cannot learn it reliably.

Server-side conversion tools can send later outcomes from a CRM. Google enhanced conversions for leads combines hashed first-party form data with offline conversions imported later, using identifiers such as a hashed email and, where possible, GCLID (Google enhanced conversions for leads, checked: 2026-10-05).

Meta Conversions API accepts events from servers, websites, apps and CRM systems for measurement, reporting and optimisation (Meta Conversions API, checked: 2026-10-05). Microsoft Advertising CAPI likewise accepts website, CRM, offline-sale and app events (Microsoft Advertising CAPI, checked: 2026-10-05).

You do not need to implement those connections to complete this step. You need to identify the outcome and its owner.

Check every primary action

Open the conversion goals and list actions marked primary. For each, record its source, trigger and business meaning. Look for visits, button clicks and duplicate versions of the same form.

Use a simple acceptance test: if this event happened 100 times, would the owner call that 100 useful outcomes? Do not turn the answer into a forecast. The purpose is to expose a definition that cannot support optimisation.

Review custom goals separately because Google can use their actions for bidding regardless of the primary or secondary label (Google primary and secondary actions, checked: 2026-10-05).

Send one test enquiry and look for duplicates

Submit one test enquiry with a unique reference. Follow it through analytics, the advertising platform and the CRM. It should become one conversion at the intended stage.

Duplicate delivery is a common technical failure when both browser and server tracking report the same event. Microsoft requires the same stable eventId for the UET and CAPI versions, or it may count both (Microsoft Advertising CAPI, checked: 2026-10-05).

Meta recommends using Conversions API with Meta Pixel and sending matching event_name and event_id values. Its deduplication applies when matching events arrive within 48 hours of the first event (Meta CAPI deduplication, checked: 2026-10-05).

Record the test result in the same place as campaign changes. A duplicate fixed once can return after a tag, form or CRM connector changes.

A banner can display correctly while the tags behind it receive the wrong signal. Google consent mode uses ad_storage, analytics_storage, ad_user_data and ad_personalization. The last two cover sending user data for advertising and personalised advertising, and ad_user_data affects enhanced conversions (Google consent mode guide, checked: 2026-10-05).

Google describes basic and advanced consent modes. Basic mode blocks tags until the person interacts with the banner. Advanced mode loads tags immediately and can send cookieless measurements after a denial for conversion modelling (Google consent mode concepts, checked: 2026-10-05).

That is a technical description, not legal advice. For obligations in the EEA, use official regulatory sources or a qualified adviser. The operational test is to deny consent, inspect the signals sent and confirm that the documented configuration matches the business decision.

Do not assume platforms share one default. Microsoft Advertising says server events are processed as consent granted unless adStorageConsent is sent as denied (Microsoft Advertising CAPI, checked: 2026-10-05). For Google Customer Match users in the EEA, an unspecified or absent consent field is treated as no consent (Google Customer Match consent, checked: 2026-10-05). Google and Meta do not document a general default for tags or CAPI in the pages cited here.

Inspect what AI Max changed

If Google Ads contains migrated campaigns, review the search terms report for the AI Max match type and its source. Check the landing page report's "Selected by" column. Confirm whether text customisation and final URL expansion are enabled (Google AI Max controls, checked: 2026-10-05).

Do not change bids or budgets from this checklist. Record which decisions the platform now makes and whether the landing pages contain current, provable information. Add the February 2027 DSA date to the same ownership process used for vendor change notices.

What not to do

Do not choose an easy event as the optimisation goal merely because it produces more data. Volume cannot repair a weak definition.

Do not send raw customer email addresses or phone numbers when a product requires hashed identifiers. Google and Microsoft both document normalisation and SHA-256 hashing for enhanced conversion data (Google enhanced conversions, checked: 2026-10-05; Microsoft Advertising CAPI, checked: 2026-10-05). Hashing is a technical requirement, not a legal conclusion.

Do not assume DSA campaigns have already migrated. September 2026 applies to automatically created assets and campaign-level broad match. DSA migration is scheduled for February 2027.

Do not use platform percentage claims as a forecast. This guide gives no budget, bidding or return advice.

When you can handle this yourself

You can complete the first review internally when one person can access the ad account, submit a test form and follow the record into the CRM. Produce a one-page map of primary actions, identifiers, consent signals and AI Max changes.

Bring in help when the browser event and server event cannot be reconciled, CRM outcomes need importing, or consent behaviour differs by region. Legal assessment belongs with a lawyer or data protection professional.

The handover point is clear: give automation more control only after one real enquiry becomes one deliberate conversion and the consent state travels with it.