What Is Meta's Performance Goal Setting — Conversions vs Landing Page Views vs Link Clicks
- info wittelsbach
- 4d
- 4 min read
You launch a campaign. Meta asks you to pick a Performance Goal. Three options stare back. You pick the one that sounds closest to 'sales'. Three weeks later your ROAS is half of what your old campaigns hit.
Performance Goal is the most consequential setting in your campaign — and the one most Indian D2C founders pick on autopilot. Each goal tells Meta a completely different story about what to optimize for. Pick wrong, lose money.
First: Confirm Each Goal Means
Conversions: Meta shows the ad to people most likely to complete your chosen pixel event (purchase, add-to-cart, lead).
Landing Page Views: Meta shows the ad to people who load and stay on the destination page for at least a few seconds.
Link Clicks: Meta shows the ad to people most likely to click the ad's link, regardless of what happens next.
Each goal optimizes the auction differently. The wrong choice doesn't just slow learning — it pushes Meta to find the wrong type of user.
When to Pick Conversions
The default answer for D2C purchase campaigns — IF your account meets the volume requirement. Meta needs roughly 50 conversion events per week per ad set to optimize Conversions effectively. Below that, the model is starved and you'll see expensive, noisy delivery.
Use Conversions when: weekly purchase volume is 50+ per ad set OR your Pixel+CAPI signal is rock solid.
Switch the optimization event to Add-to-Cart or Initiate Checkout if you're under 50/week. These higher-volume events still correlate with sales but learn faster.
Never run Conversions optimization with broken CAPI. Meta optimizes for a signal it can't see — you'll burn budget.
When to Pick Landing Page Views
The most underrated Performance Goal for early-stage Indian D2C accounts. Use it when Conversions is starved but Link Clicks would bring in low-intent traffic.
Use Landing Page Views when: you're testing creative on cold audiences and Conversions hasn't seeded yet.
Why it works: Meta filters out bot clicks, accidental clicks, and impatient users. Only those who actually load and stay get counted, so the audience Meta builds has real intent.
Bridge strategy: Run Landing Page Views for 2-3 weeks to build Pixel volume, then graduate to Conversions when 50+ events fire weekly.
When (and Why) to Almost Never Pick Link Clicks
Link Clicks invites Meta to find the cheapest possible clicker. These are users who tap ads habitually, often without intent to engage with the destination. Click-through rates look great on paper. CPAs are catastrophic.
The only legitimate Link Clicks use cases: app-install style campaigns where the click IS the conversion, or hyper-narrow retargeting where every click is a known warm user. For D2C purchase campaigns, Link Clicks is almost always a margin trap.
The Bridge Strategy: How to Migrate Between Goals
Most accounts evolve through three stages. The Performance Goal should evolve with them.
Stage 1: New Account, No Volume
Run Landing Page Views with broad creative testing. Aim for 500-1000 page views per week. Track Add-to-Cart and Purchase rates manually.
Stage 2: Growing Account, 20-50 Weekly Conversions
Shift to Conversions optimized for Add-to-Cart. This is a stronger signal than Landing Page Views but more achievable than Purchase optimization.
Stage 3: Established Account, 50+ Weekly Purchases per Ad Set
Conversions optimized for Purchase. Use [CBO vs ABO logic](https://www.wittelsbach.ai/post/cbo-vs-abo-in-meta-ads-which-budget-strategy-wins-for-d2c-in-2026) to consolidate or split.
Common Mistakes Indian D2C Founders Make
Picking Conversions on Day 1 with broken Pixel. No signal, no optimization, only spend.
Staying on Link Clicks because CTR looks good. Vanity metric. Check Purchase rate per click, not CTR.
Switching goals mid-campaign. Every change re-triggers the learning phase. Stick with a goal for at least 14 days before judging.
Mixing goals across ad sets in one campaign. Confuses budget allocation, especially under CBO.
How Wittelsbach AI Picks the Right Performance Goal
Bach AI audits your account on connection — checks weekly event volume, Pixel quality, and CAPI match rate — and recommends the right Performance Goal per ad set. As volume grows, it surfaces the moment you should graduate to deeper optimization. Connect your Meta account at [app.wittelsbach.ai](https://app.wittelsbach.ai) for a free audit.
Frequently Asked Questions
Can I run multiple Performance Goals in the same campaign?
Technically yes, at the ad set level. Practically, no. Mixed goals inside one campaign — especially under CBO — confuses budget allocation. Meta can't compare apples to oranges, so it defaults to picking the highest-volume signal. Keep one Performance Goal per campaign.
Does Performance Goal affect cost per result?
Hugely. Conversions optimization typically costs 2-4x more per result than Link Clicks for the same audience and bid, because Meta is filtering harder. But the result is meaningful — actual buyers, not random clickers. The 'higher cost' is correctly priced.
Should I match Performance Goal to my Campaign Objective?
Yes. A Sales objective campaign should run Conversions Performance Goal in nearly every case. A Traffic objective campaign should run Landing Page Views. Cross-mixing objective and goal often locks you out of important auction features like Advantage+ placements.
Is Advantage+ Shopping affected by Performance Goal choice?
No — Advantage+ Shopping Campaigns hardcode the Performance Goal to Conversions optimized for Purchase. You can't change it. This is one reason Advantage+ requires a solid Pixel/CAPI setup before it makes sense to run.
How long should I wait before switching Performance Goal?
Minimum 14 days, ideally 21. Performance Goal changes re-trigger the learning phase, so you lose all accumulated optimization. Only switch if you have clear data — 50+ events fired and clearly underperforming target by 25%+ — not on a gut call after 5 days.




Comments