How the traffic objective works
When you create a Meta campaign, the objective tells the delivery system what result you are buying. Traffic tells it to buy visits to a destination. Meta then looks through your audience for the people it predicts are most likely to tap the ad and arrive — not the people most likely to enquire or buy once they get there.
Two settings inside the campaign decide what “a visit” actually means. The conversion location chooses the destination: your website, your app, a Messenger or WhatsApp thread, a phone call, or an Instagram or Facebook profile. The performance goal then chooses between maximising link clicks and maximising landing page views, which is the difference between paying for a tap and paying for a page that finished loading.
Why the traffic objective matters
It is the objective to reach for when there is genuinely nothing better to optimise towards. A brand-new pixel with no purchase or lead history, a blog article, an event page, a product still in soft launch — in all of those cases asking the system to find buyers is asking it to guess. Traffic gives it a job it can actually do.
It also matters because it flatters reports. Clicks are the cheapest result Meta sells, so a traffic campaign will almost always show a lower cost per result than a leads or sales campaign running beside it. That gap is a difference in what is being bought, not evidence that the traffic campaign is working harder.
Common mistakes with the traffic objective
The most expensive mistake is using traffic when you want enquiries. The system is being scored on arrivals, so it learns to find people who tap readily and leave quickly. You end up buying a busy analytics chart and an empty inbox.
The second is picking link clicks over landing page views on a slow site. In Nepal most of this traffic arrives on mobile data, and a page that takes several seconds to paint loses a large share of the taps you paid for. Optimising for landing page views forces Meta to prefer people whose connection and patience survive the wait, and it exposes the loss instead of hiding it.
How to act on it
Treat traffic as a starting position, not a destination. Run it while the pixel gathers events, optimise for landing page views rather than link clicks, and compare the two counts every week — a wide gap between them is a site speed problem, not a targeting problem.
As soon as the account is recording real enquiries or purchases, move the budget to the objective that matches the outcome you are paid for and let traffic keep only the jobs it is honest at: content promotion, retargeting pools and audience building. If you want that transition planned properly, the Meta Ads service page sets out how the objectives fit together across a full account.
