Traffic Objective
By the AdFlint research team · Last reviewed July 2026
Maximizes clicks or landing page views to a destination on Meta, without optimizing for anything the visitor does after arriving.
Meta finds people historically likely to click and bills on impressions, with performance goals for link clicks or landing page views. Advertisers use it for content distribution, or when a site has too little conversion data to optimize on. The misunderstanding is expecting sales from it: the system is selecting habitual clickers, so conversion rates sit well below a sales or leads campaign.
Key takeaways
- Billing runs on impressions even though optimization targets clicks or landing page views, so a low CPC doesn't mean efficient spend.
- Landing page views is a higher-quality optimization than link clicks because it requires a page-load signal, but it needs the Pixel firing correctly to work.
- Conversion rates from Traffic-driven visitors run well below a Sales or Leads-optimized campaign sending equivalent volume - it's built to find clickers, not buyers.
- Its best use is content distribution or seeding a retargeting audience when there isn't enough conversion data yet to run Sales.
In practice.
Traffic optimizes delivery toward one of a few actions - link clicks, landing page views, or daily unique reach for a defined audience - while typically billing on impressions regardless of which one you pick. That distinction matters: a cost-per-link-click or cost-per-landing-page-view number in reporting is a derived metric, not what you're actually being charged for, so a cheap-looking cost per click doesn't automatically mean efficient spend if the underlying CPM and click-through rate are the real drivers.
Landing page views is the higher-quality option of the two click-based choices, because Meta waits for a signal that the destination page actually loaded, via the Pixel or App Events SDK, before counting the result, filtering out clicks that bounce before the page renders, common on slow mobile connections or heavy pages. Link clicks counts the click itself regardless of what happens after, which is cheaper and higher-volume but includes accidental taps and clicks that never resolve into a real page view. Choosing landing page views without a correctly firing Pixel effectively starves the campaign of the signal it needs to optimize, since Meta can't tell who reached the page if the tracking isn't there.
Because delivery is scored on click and page-view likelihood, it leans toward people with a demonstrated pattern of clicking things - a real, identifiable segment, but not one selected for purchase or lead intent. That's a deliberate design tradeoff, not a flaw: Traffic is built to move a lot of people to a destination cheaply, not to screen for who's likely to buy once they get there.
It fits content distribution, driving readers to an article or blog, situations where a site has too little conversion history for Meta's Sales objective or Leads objective to optimize on directly, and building a low-cost pool of site visitors to retarget later - the visitors from a Traffic campaign still populate a Website Custom Audience, which is a genuinely useful byproduct even when the traffic itself doesn't convert well in the moment.
The recurring mistake is running a Traffic campaign and evaluating it against a sales or lead goal it was never built to hit, then concluding the product or offer doesn't work when the real issue is objective mismatch. A second is defaulting to Traffic out of habit, or because it's cheap on a per-click basis, on an account that actually has enough conversion volume to run Sales or Leads directly, which would generally deliver better cost per acquisition even at a higher headline CPC. A third is picking landing page views without first confirming the Pixel fires correctly and quickly enough on the destination page to register the view.
Reading a Traffic campaign well means checking link clicks against landing page views side by side - a large gap between the two usually points to a page-load or speed problem worth fixing on the site itself, independent of the ad. Track downstream conversion rate from that traffic against a Leads or Sales campaign sending comparable volume before deciding Traffic underperformed; the comparison is often the whole point of the diagnosis, since Traffic's job was never to convert at the same rate.
Reading a blog's Traffic campaign against its newsletter
Suppose a media site spends $500 on a Traffic campaign optimized for landing page views, at an average CPC of $0.35, generating about 1,400 clicks. Of those, only 1,150 register as landing page views - a gap the team traces to slow mobile load times on the article page.
Of the 1,150 landing page views, 12 visitors go on to subscribe to the newsletter - about a 1% traffic-to-subscription rate. The same site's dedicated Leads objective campaign, sending similar visitor volume directly to the subscription form, converts at closer to 4%. The gap isn't a sign the Traffic campaign failed; it confirms the two objectives are selecting different kinds of visitors, and the site keeps Traffic running for its lower cost per visitor while treating the newsletter campaign as the one actually built to convert.
Traffic Objective compared with
The settings this gets confused with, and how to tell them apart.
- Traffic Objective vs Sales Objective
- Traffic Objective vs Leads Objective
- Traffic Objective vs Engagement Objective
- Traffic Objective vs Awareness Objective
- Traffic Objective vs App Promotion Objective
- Traffic Objective vs Advantage+ Shopping Campaigns
- Traffic Objective vs Manual Sales Campaigns
- Traffic Objective vs Conversions Objective (Legacy)
Common questions.
Does the Traffic objective bring in buyers, not just clickers?
Not reliably. Meta's delivery for Traffic optimizes for people historically likely to click or view a landing page, a group that skews toward habitual clickers, so conversion rates downstream are typically much lower than a Sales or Leads-optimized campaign sending equivalent volume.
Link clicks or landing page views - which optimization should I pick?
Landing page views generally delivers higher-quality traffic since Meta waits for a page-load signal before counting the result, filtering out clicks that never actually load the page, though it usually costs more per result and needs the Pixel firing correctly to work.
When is it worth running a Traffic campaign instead of Sales?
When the site has too little conversion data for Meta's delivery system to optimize on directly, when the goal is content distribution rather than a transaction, or when building a low-cost site-visitor audience to retarget later with a Sales or Leads campaign.
Why is my cost per click cheap but conversions aren't coming?
That's expected behavior, not a bug. Traffic billing and optimization reward clicking behavior, not purchase intent, so a low CPC with a low downstream conversion rate usually means the objective is working as designed, not failing.
You should not need to know this to advertise.
AdFlint handles the settings for you, inside the Google and Meta accounts you already own.
Try AdFlint free