What changed: one setup for sales, app and leads
On May 29, 2025, Meta began rolling out its streamlined Advantage+ setup for sales and app campaigns, starting with selected advertisers. Instead of choosing between an Advantage+ shopping campaign and a manual one, you build one campaign, and it runs as Advantage+ when three settings are on. Leads campaigns work the same way.
- Advantage+ campaign budget: one campaign budget that Meta distributes across your ad sets in real time.
- Advantage+ audience: on in at least one ad set, so Meta can search beyond the audience you describe.
- Advantage+ placements: no placement choices or exclusions at ad set level.
Switch one off and the campaign is no longer Advantage+. In Meta’s Marketing API, version 24.0, released October 8, 2025, stopped the creation and editing of the old Advantage+ shopping and app campaigns, and from version 25.0, scheduled for the first quarter of 2026, they can’t be created on any version. Migrating an old campaign puts it back into the learning stage, with no workaround, so do it in a quiet week.
What you still control
These settings still change results:
- Bid strategy. Meta recommends bidding without a cap. If you need limits, use a cost cap, a bid cap or a minimum return on ad spend (ROAS). A campaign that starts on minimum ROAS can’t switch strategy later.
- Hard audience limits. Advantage+ audience never expands your locations, minimum age, languages or the custom audiences you exclude. With it on, the minimum age can be set from 18 to 25.
- Account-level placement exclusions. They still apply, and the campaign stays Advantage+.
- New versus existing customers. The existing-customer budget cap retired with the old shopping campaigns; old campaigns still using it will be paused with version 26.0. Instead, Meta suggests two ad sets, one for existing customers and one excluding them, with a daily spend target and cap.
- The conversion event and the creative. The rest of this guide covers both.
One check sits outside Meta: in the sales app I built for the Glass Railing Store team, the sales Meta reports are checked against real Shopify orders.
Why the Conversions API matters more now
When Meta picks the audience, the event you optimize for becomes your targeting. If Meta sees only some of your sales or leads, it learns from only some of your customers.
The Meta Pixel reports from the browser; the Conversions API sends events from your server or CRM. Meta recommends a redundant setup, sending the same events through both, because the server can share website events the Pixel may lose to connection problems or page loading errors, plus offline events from your CRM.
Meta defines event coverage as the 7-day average share of Pixel events that the Conversions API also covers, and flags events below 75%. It advises sending events in real time or as close to it as possible, and says more reported conversions can help lower your cost per result.
I give server events the same consent rules as the Pixel: if a visitor declines tracking, neither one sends their data. The Canadian rules are in privacy, consent and tracking in Canada.
Clean event data: deduplication and match quality
Two sources bring two risks: double counting, and events Meta can’t match to a person.
Deduplicate the Pixel and the server
Send each event with the same name and ID from both: the Pixel’s eventID must match the Conversions API’s event_id. Meta only deduplicates events received within 48 hours of the first one with that ID. The alternative, matching on fbp or external_id, works only when the browser event arrives first, so I use event IDs.
Raise event match quality
Event Match Quality, shown for each event in Events Manager, is a score out of 10 for how well a server event’s customer information can match it to a Meta account. For now it covers web events only. It matters because only matched events count for attribution and delivery optimization; unmatched ones serve basic measurement.
- Send
action_sourcewith every event, plus the page URL and the browser’s user agent with website events. - Include
event_idandexternal_idon every event. - Add the strong keys Meta lists: email, phone number, name and IP address. Meta’s Business SDK hashes what needs hashing; a custom build must follow Meta’s hashing rules itself.
- Refresh the
fbpandfbccookie values regularly if you send them; they change.
Creative volume, and how to test it
With audience and placements automated, I treat the creative as the targeting. Different ads reach different buyers, so three near-identical ads give Meta little to choose from.
Andromeda, the ad retrieval system Meta described on December 2, 2024, narrows tens of millions of ad candidates to a few thousand relevant ones, and Meta built it expecting the number of ad creatives to grow significantly as advertisers adopt generative AI tools. The same post says more diverse ads can drive better advertiser outcomes.
Volume means different ideas, not 20 versions of one ad. For each product or service I plan:
- Angles: the problem, the result, the price, the proof and the objection buyers raise most.
- Formats: vertical video, a still image and a carousel or a before and after.
- A hook in the first seconds and a version for each placement.
- Real customers and projects, like the testimonial reel I cut for Glass Railing Store’s Meta ads and the installation films for both brands.
To test, I put new concepts in their own ad set with a daily spend target, which Meta treats as a best effort, not a guarantee. I judge each concept on cost per sale or qualified lead, not clicks, then move winners into the main ad set.
Connect lead forms to your CRM
Instant forms make it easy to leave your details, which helps volume and can hurt quality.
Get every lead to sales in minutes
Meta can push each new lead to a webhook in real time, with a delay of up to a few minutes, and many CRMs offer real-time syncing of lead ads data. For the brands I lead, every Meta lead reaches the sales team in under five minutes through a pipeline I built with AI automation.
Send the outcome back to Meta
The Conversions API for CRM sends each lead’s progress back to Meta, so a campaign can optimize for the Conversion Leads performance goal instead of form fills. Meta says this may yield higher quality leads that are more likely to convert. The goal currently works with instant forms only, and Meta asks for:
- The 15 to 17-digit Meta lead ID, stored in your CRM.
- At least 200 leads a month.
- Data uploaded at least once a day, ideally in real time.
- A target stage, such as a booked site visit, reached within 28 days of the lead, with a conversion rate between 1% and 40%.
Send every stage as it changes, with the lead ID. Meta estimates under a day to connect through a Meta Business Partner or three to four weeks for a custom build, then two to four weeks of learning. Under 200 leads a month, still track every lead’s outcome in your CRM, so you know which campaigns bring customers, not just contacts.
What to do, in order
- Audit your events: match quality, coverage and duplicates for each event you optimize for.
- Add the Conversions API with the same event names and IDs as the Pixel, sent in real time.
- Raise match quality with email, phone number and IP address, collected with consent.
- Set your hard limits: locations, minimum age, languages, customer exclusions and account-level placement exclusions.
- Rebuild on Advantage+: one campaign per goal, plus an existing-customer ad set if you limit their spend.
- Start a creative pipeline: new concepts every month, tested in their own ad set.
- Close the lead loop: leads to sales in minutes, CRM stages back to Meta daily, and the Conversion Leads goal past 200 leads a month.
This is the order I follow in Google Ads and Meta Ads management, where spend is tied to Shopify orders and CRM leads. For Google’s version of the same shift, read AI Max and Performance Max in 2026.
Sources
- Advantage+ Campaign Experience for Sales and AppMeta for Developers, June 2025
- Advantage+ Campaign Experience for Sales, App, and Leads (Marketing API v25.0)Meta for Developers, October 2026
- Version 24.0 changelog (Graph API and Marketing API)Meta for Developers, October 2025
- Advantage+ audienceMeta for Developers, October 2026
- Advantage campaign budgetMeta for Developers, October 2026
- Best Practices: Conversions APIMeta for Developers, October 2026
- Handling Duplicate Pixel and Conversions API EventsMeta for Developers, October 2026
- Dataset Quality API (event match quality, event coverage, data freshness)Meta for Developers, October 2026
- Meta Andromeda: Supercharging Advantage+ automation with the next-gen personalized ads retrieval engineEngineering at Meta, December 2024
- Retrieving Leads (lead ads webhooks)Meta for Developers, October 2026
- Conversions API for CRM Integration (Conversion Leads requirements)Meta for Developers, October 2026
- Conversions API for CRM: developer implementationMeta for Developers, October 2026




