How to See New Customer ROAS and CPA in Meta Ads Manager: Audience Segments vs a New-Customer Purchase Event

Meta Ads Manager can show new-customer numbers two ways. Meta's audience segments breakdown splits sales campaign results into new audience, engaged audience and existing customers, based on custom audiences you define. Or you send a new-customer purchase event, turn it into a custom conversion and add a custom NC-ROAS metric: NC Purchase conversion value ÷ amount spent.

For how ad platforms credit a sale in the first place, see our guide to attribution models. This post compares the two routes (how each decides who is new, what each misses, where each shows up), then walks through the columns step by step. Which new-customer CPA to trust for budget decisions, Meta-attributed or blended, is the subject of our nCPA decision framework. We checked every Meta detail below on Meta's own help and developer pages on October 24, 2026.

What is new customer ROAS?

New customer ROAS is revenue from first-time buyers divided by ad spend. New customer CPA (nCPA) is ad spend divided by the number of first-time buyers.

NC-ROAS = new-customer purchase value ÷ amount spent

nCPA = amount spent ÷ new-customer purchases

Ordinary ROAS mixes first orders with repeat orders, and repeat buyers are the cheapest people to convert. A campaign can post a strong ROAS while finding almost no one new. Splitting first-time buyers from returning ones shows which campaigns grow the customer base and which mostly reach people who already buy from you.

Both numbers in Ads Manager are Meta-attributed: they count only purchases Meta credits to your ads under each ad set's attribution setting, including view-through credit. Our guide to Meta ads attribution settings explains those windows.

---

What does Meta offer for new customers today?

Three things, as of October 2026: a reporting breakdown by audience segment, a customer lifecycle strategy that steers a sales ad set toward new customers, and an existing customer budget cap in older Advantage+ shopping campaigns, which Meta is retiring.

Audience segments breakdown

You define two segments once, at the ad account level. Meta's setup steps: in Ads Manager, open All tools > Advertising settings > Audience segments, then pick custom audiences for Engaged audience and Existing customers and click Confirm. Existing customers can come from website, app activity, catalog, customer list, offline activity, shopping and lead form sources.

Then, on a sales campaign, click Breakdown and choose Audience segments under By demographics (Meta's steps). Meta splits results three ways:

Source: Meta Business Help Center, checked October 24, 2026. Meta notes the feature may not be available to every account yet. If you pull data through the API, the Insights API breakdowns include user_segment_key, which splits Advantage+ shopping campaign results into new and existing users by the custom audience set in the campaign.

Customer lifecycle strategy: acquire new customers

In a Sales campaign, each ad set has a Customer lifecycle strategy. Meta's guide offers Get conversions from all audiences or Acquire new customers, which excludes the existing customers you select and can also exclude engaged audiences. Meta warns this may raise your cost per result, and recommends judging these campaigns on new customer CPA from your measurement tools rather than on overall campaign CPA.

Existing customer budget cap

Advantage+ shopping campaigns let you define existing customers as a set of custom audiences and cap the share of budget spent on them. Meta's Marketing API v25.0 notes of February 18, 2026 say the cap isn't available with the new Advantage+ campaigns, and that remaining Advantage+ shopping campaigns will be paused in v26.0, which Meta estimated for September 2026.

---

How does a new-customer purchase event work?

Your tracking tool decides at checkout whether the buyer is new and sends Meta an extra event beside the standard Purchase, so Meta never has to recognize the customer itself.

Upstack Signal sends two such events. NC Purchase (it appears in Events Manager as ncPurchase) fires when the order comes from a customer Upstack has no customer record for. RC Purchase fires when Upstack already has one. According to Upstack's docs, on each purchase Upstack looks the customer up in its own customer records, built from tracked purchases plus imported Shopify orders; it doesn't look up the customer's order history in Shopify at purchase time.

Three details matter for reporting:

• Standard Purchase still fires for every order. NC Purchase and RC Purchase are added on top, so Meta's baseline reporting and optimization keep every sale.
• Subscription renewals aren't sent to Meta as purchases. The first subscription order is, so a renewal never shows up as a new or returning purchase.
• The definition is the sender's. Any tool that sends a new-customer event decides who counts as new. Ask what it checks before you trust the column.

---

Meta's segments vs a new-customer event: side by side

The two routes answer slightly different questions. Meta's segments ask whether Meta can place the person in an audience you gave it; a new-customer event asks whether this order is the customer's first.

Sources: Meta's customer list matching and website custom audience pages, and Upstack's docs, checked October 24, 2026.

The matching row is the one to watch. Meta matches a customer list to its own profiles, and the more identifiers you provide, the better the match rate. Anyone it can't match isn't in your Existing customers segment, so their repeat order shows up as new. A website custom audience won't backfill and may lack events from some iOS 14 users.

Our take. Use both. The segments breakdown costs nothing once your audiences exist and is a good check on how much of a campaign's spend reaches people who already buy. The new-customer event gives you nCPA and NC-ROAS on every ad and an event you can optimize toward. When the two disagree, the gap is usually matching or the engaged audience definition, not a broken event.

How to add NC Purchase, nCPA and NC-ROAS columns in Ads Manager

These steps follow Upstack's guides to creating and sharing the custom conversion and adding the columns, plus Meta's own pages where noted. You need admin access to the business portfolio that owns the pixel, not only to the ad account.

1. Acknowledge the event. After the first new-customer order, open your pixel in Events Manager, find ncPurchase on the Overview tab, click Review, then acknowledge and confirm the custom event.
2. Create the custom conversion. Go to Custom Conversions > Create custom conversion. Name it NC Purchase and choose the ncPurchase event. Pick Purchase as the standard event for optimization: Meta requires a standard event category when a custom conversion is built on a custom event. Add a URL rule of doesn't contain doesnotexist, which matches every page. Leave the value field empty so Meta uses the order value sent with the event. Meta allows 100 custom conversions per ad account.
3. Share it. On the Custom Conversions page, open the row's menu, click Share > Share with an Ad Account, and tick every ad account that will use it.
4. Add the count and cost columns. In Ads Manager, open Columns > Customize columns > Custom conversions > NC Purchase, and tick Total and Cost. Total is the new customers Meta credits to your ads; Cost is your nCPA.
5. Create NC-ROAS. In the same dialog, click Create custom metric (Meta's steps). Set the formula to NC Purchase conversion value ÷ Amount spent, name it NC-ROAS and pick the numeric format. Choose who can see it: only you, or everyone with access to the ad account. Meta says you can't edit or delete a formula once it's shared.
6. Apply. Tick NC-ROAS under custom metrics and click Apply. Repeat steps 1 to 4 for RC Purchase if you want returning-customer columns beside the new ones.
7. Wait for new orders. Meta doesn't fill a new custom conversion with past results: the columns start from purchases after you create and share it. Allow 24 to 48 hours of new traffic before you read them.

---

Should you optimize campaigns for NC Purchase?

Test it on one campaign first. Changing an ad set's optimization event sends it back into Meta's learning phase.

Meta says an ad set usually exits the learning phase after about 50 results in the week after its last significant edit. New-customer purchases are a subset of all purchases, so a low-volume ad set can stay in learning longer. Upstack's docs suggest starting with your highest-spend or highest-volume campaign, running it beside a Purchase-optimized campaign for 2 to 4 weeks, and comparing new-customer rate, CAC and ROAS before you move budget. Keep standard Purchase active either way, and use RC Purchase for retargeting and retention ad sets.

Remember what the columns can't tell you. They're Meta's attribution of new customers, so they carry the same view-through credit and modeling as Meta's other numbers; our post on Meta reporting more purchases than Shopify explains those effects. For new-customer CAC across every channel against your Shopify revenue, use a blended number, as the nCPA framework describes.

---

Frequently asked questions

Can you see new customer ROAS in Meta Ads Manager without a custom event?

Partly. Meta's audience segments breakdown splits a sales campaign's results into new audience, engaged audience and existing customers, so you can read spend and results for each segment. It depends on custom audiences you define, and Meta notes it may not be available to every account yet.

Why are my NC Purchase columns empty?

As Upstack's docs note, Meta doesn't fill a new custom conversion with past results, so the columns start from purchases after you create it. Check that the ncPurchase event is acknowledged in Events Manager and that the custom conversion is shared with the ad account you're viewing, then allow 24 to 48 hours of new orders.

Why doesn't the audience segments breakdown match my NC Purchase count?

They define "new" differently. Meta's segments put a first-time buyer who visited your site before into engaged audience if you defined one, and can count a returning customer as new when it can't match them to your customer list. NC Purchase checks the buyer against the sending tool's customer records at checkout.

Does NC Purchase replace the standard Purchase event?

No. Keep standard Purchase running for every order so Meta's baseline reporting and optimization see every sale. NC Purchase and RC Purchase are extra events that split those orders into new and returning customers.

Should I judge campaigns on NC-ROAS or blended new-customer ROAS?

Both, for different decisions. NC-ROAS in Ads Manager compares campaigns and ads inside Meta. Blended new-customer ROAS, built from all spend and all new customers in Shopify, tells you whether the business is acquiring customers profitably. Our nCPA framework shows how to read the two together.

See Upstack Signal, which adds new-customer CPA and ROAS columns to your Meta Ads Manager.