Meta Pixel, Conversions API and attribution

How do I compare attribution settings in Meta Ads Manager?

The Compare attribution settings view shows one ad set under several windows at once, without changing delivery. What each column counts and how to read it.

Published

You compare attribution settings in Ads Manager from the Columns menu, not from the ad set: open Columns: Performance, scroll to Compare attribution settings, tick the windows you want, choose All conversions or First conversion, then click Apply. The table then shows the same spend and the same delivery under several windows at once, and nothing about the campaign changes.

That distinction is the whole point of the view. Editing the ad set setting informs delivery, because Meta optimises for the windows you select. Comparing is only a different lens on results you already have, so it is free and reversible.

Where the comparison lives in Ads Manager

  1. Open Ads Manager on the account or campaign you want to read.
  2. Open the Columns: Performance dropdown and keep Performance selected.
  3. Scroll down and choose Compare attribution settings.
  4. Tick the windows you want: 1-day view, 1-day click, 7-day click and 28-day click. Engage-through appears as 1-day Engagement.
  5. Choose the conversion count: All conversions or First conversion.
  6. Click Apply, then export the table if you report on it.

The setting itself sits on each ad set, in the Conversion section of a website campaign, so it is not an account-wide control. If the goal is to change what an ad set optimises for rather than to read it, that is a different job, covered in how to change the attribution setting.

What each column counts

The windows are not variations on one definition. Each adds a different kind of credit:

ColumnWhat counts as a lead for the adEffect on reported CPL
1-day clicka lead within 1 day of a link click on the adthe fewest leads, so the highest CPL
7-day clicka lead within 7 days of a link clickmore leads than 1-day click, lower CPL
1-day Engagement (engage-through)a lead within 1 day of a non-link click such as a like, share, save or comment, or of a video play of 5 seconds, or 97% of a shorter videoadds leads that came without a link click
1-day viewa lead within 1 day of an impression of the adadds leads credited to a view alone
28-day clicka lead within 28 days of a link clickcomparison only, not a selectable setting

The default ad set setting combines 7-day click, 1-day view and 1-day engagement, which is the highest count among the standard options and therefore the lowest reported cost per lead. Meta attribution settings has the full list with the source for each line.

All conversions or First conversion

The conversion count is the option most people leave on its default without noticing what it does.

All conversions counts every conversion the window can claim, including repeat submissions from a person who already filled in the form. First conversion shows only the first measurable conversion after a click or a view.

For lead generation the second is usually the more honest read, because it matches a CRM that merges repeat submissions into one contact. The gap between the two columns is the number of duplicate or repeat forms in the period, which is a useful figure on its own: a large gap means your form is being submitted twice by the same people, often because a confirmation step is missing.

One spend, four readings

The clearest way to see what the view does is to run a week through it. An ad set spends €1,500:

Attribution settingLeads reportedReported CPL
1-day click50€30.00
7-day click60€25.00
7-day click + 1-day engagement68€22.06
7-day click + 1-day engagement + 1-day view90€16.67
Your CRM: leads carrying a Meta ad ID52€28.85

Every Meta row is correct under its own rule, and the spend never moved. In this example 22 of the default’s 90 leads are credited to an impression alone, which means those people saw an ad and filled in a form without clicking it. Some are genuinely influenced by the ad. Some reached the landing page another way, and your own tracking credits the route it can see.

The last row is the reason to keep a first-party count. It lands near the click-through figures because those are the leads a landing page can actually observe.

Why the date matters more than the column

Click-through changed meaning in March 2026. Meta announced on 3 March that click-through attribution for website and in-store conversions would count link clicks only, where a like, a share or a save had counted as a click before. Those interactions moved into engaged-view attribution, renamed engage-through, and the engaged view of a video ad dropped from 10 seconds to 5.

The rollout started that month and reached accounts at different times. So a 7-day click CPL from February 2026 and one from April 2026 do not rest on the same definition, even though the column name is identical. Mark the date on any report that spans the change.

Two further details decide what you can compare at all:

  • Long windows are gone as ad set settings. Click-through tops out at 7 days, views and engagement at 1 day.
  • The 7-day and 28-day view windows were removed from the Ads Insights API on 12 January 2026. A dashboard connector built on them returns nothing or the wrong thing, so check it before you quote a trend line.

Standard and incremental are not comparable

The ad set screen also offers incremental attribution, which optimises and reports on the conversions Meta’s models predict the ad caused. That is a different count from the standard one, and Meta warns against comparing ad sets that run different models in the same campaign table.

Take the warning literally. A table that mixes the two models shows a performance gap that is really a definition gap, and the usual reaction, moving budget towards the better looking ad set, moves it on an artefact. Keep one model per campaign table, or read the two models in separate reports.

What to do with the comparison

Three uses, in order of how much they change a decision.

First, sizing the gap. Put your first-party lead count next to the 7-day click column. The difference is the number of leads Meta credits that your landing page never saw. If it is a tenth of the total, the two numbers can coexist in one report. If it is half, the ad account is being credited for demand it did not create, and budget decisions need your own count.

Second, checking a creative. A creative whose results sit mostly in the view column did not send those people anywhere. Before scaling it, confirm it works on clicks.

Third, answering the client question. When someone asks why Ads Manager reports more leads than the CRM, the four columns answer it in one screenshot: same spend, different rules, and one row from your own records.

For a lead gen account the practical reading order is: your first-party CPL first, Meta’s 7-day click next, and view-through plus engagement as diagnostic columns. The comparison view gives you all of them without touching a single ad set, which is why it should be the first thing you open when a number in a report looks wrong. All the tracking questions covers the setup side, Pixel included.

Questions on this topic

All questions on this topic →

FAQ

Does comparing attribution settings change delivery?+

No. The comparison view is a reporting layer: it shows the same spend and the same delivery under several windows. Changing the ad set setting is what informs delivery, because Meta optimises for the windows you select.

Why is the 28-day click column only half filled?+

Because a campaign that has not been live for 28 days has only partial data in that column. The window runs past the start of the campaign, so there are days it cannot cover.

What does First conversion show?+

Only the first measurable conversion after a click or a view. That is nearer to a CRM that merges repeat submissions from the same person into one contact record, which is why it reads lower than All conversions.

Can I compare ad sets that use different attribution models?+

Meta warns against it. Standard and incremental attribution count different things, so a campaign table that mixes them looks like a performance difference when it is a definition difference. Compare within one model.

Ready to find out what
converts, for real?

Free to start.

Start free →