An agency proposes switching your Meta campaigns to incremental attribution. Its presentation shows fewer credited purchases and a different acquisition cost. Before approving a campaign change, establish whether the proposal concerns a different reporting view, a different delivery model, or an experiment measuring additional business. Those decisions require different evidence.
Meta standard attribution credits conversions under selected interaction and time settings. Incremental attribution uses Meta’s models to predict which conversions an ad caused and can inform both delivery and reporting. Inspecting incremental results does not require switching an existing campaign’s delivery model. Compare campaigns under the same reporting model, then evaluate any proposed delivery test against a defined business outcome and operating constraints. Neither model is a universal winner.
This comparison is for established e-commerce teams deciding how to evaluate a proposed change. It concerns website conversion workflows. An app-only acquisition campaign needs its own eligibility and measurement review; the setup described here should not be transplanted to it.
What changes between standard and incremental attribution?
Meta’s attribution-model documentation describes standard attribution through selected time windows and user behaviors. Its incremental-attribution explanation describes machine-learning predictions about whether an ad caused a conversion. Both influence how results are interpreted; choosing a delivery model also influences optimization.
Keep three decisions on separate lines in the review:
Decision What the team changes What the evidence can answer --- --- --- Inspect another reporting model The reporting view used to examine existing delivery How the same campaign is represented under another model Test another delivery model The campaign configuration being used to buy media Whether that intervention merits continuation under a defined evaluation Run an incrementality experiment A designed exposure contrast and outcome analysis What additional outcome the tested intervention produced, subject to design and uncertainty
The table is a buyer-side decision framework. It prevents a reporting comparison from quietly becoming authorization to rebuild campaigns or increase spend.
A lower modeled count can prompt a useful question about credited demand. It does not establish that a particular customer would have purchased anyway, that the difference is wasted budget, or that selecting another model will recover that budget. Those conclusions go beyond the observation.
Compare the models by the decision they support
Start with the desired action, then identify which evidence is missing.
Criterion Standard attribution Incremental attribution Buyer check --- --- --- --- Basis for credit Selected eligible interactions and time settings Meta’s predictions about ad-caused conversions Label every result with its model Reporting inspection Existing settings need to be recorded Modeled results can be inspected without selecting it for delivery Preserve both views for the same campaign and dates Delivery proposal Retain the current documented configuration A proposed configuration must satisfy the current setup requirements Inventory the controls the business would lose or change Financial interpretation Credited revenue still needs an accounting definition Modeled credited revenue still needs an accounting definition Reconcile value, refunds, currency and customer status Causal validation Rules alone do not establish added demand A modeled result is not your own controlled experiment Match the evaluation to the decision’s risk
The reporting distinction follows Meta’s results guidance. The financial checks and decision rules are editorial recommendations, rather than additional Meta requirements.
Retaining standard delivery can be reasonable while evidence is repaired or an operating constraint is resolved. Testing incremental delivery can be reasonable when the setup is supported and the business can evaluate the change. Neither decision requires declaring all alternative attribution useless.
Check current eligibility and constraints before proposing a switch
Meta’s incremental-attribution setup instructions, checked November 12, 2026, list Sales, Engagement or Leads objectives; Website or Website and app conversion locations; and maximize-number or maximize-value conversion goals. They state that bid controls cannot be used with incremental attribution. They also state that a published campaign’s attribution model cannot be changed: changing the model requires a new campaign.
These constraints belong in the proposal before budget is approved. A business that depends on a particular bid control needs to assess the consequence of losing that control. A new campaign is also a real intervention, with its own identity, configuration and operating history. Calling it a simple reporting adjustment hides the actual work.
Record the objective, conversion location, goal, available model selector, current bid controls and publication state from the account being reviewed. Keep a dated, redacted configuration export or screenshots. Documentation establishes supported workflows; it does not establish what is visible or appropriate in a private account.
Meta warns that setup experiences can differ during rollout. Its standard-settings page also describes ongoing changes to click-through and engage-through treatment. Preserve the definitions shown in the account instead of silently comparing periods with different meanings. A name that looks unchanged can still need a definition check.
Inspect alternate reporting before changing delivery
Meta’s reporting instructions say modeled incremental results can be viewed even when incremental attribution was not the campaign’s selected delivery model. They describe the Columns menu’s Compare attribution models option and recommend comparisons within the same model.
Use that inspection to prepare the question:
Export the campaign identifiers, dates, spend, selected delivery model and current reporting definitions.
Inspect the available incremental reporting alongside the existing view for the same scope.
Compare candidate campaigns under one common reporting model at a time.
Record the unresolved business question separately from the observed numerical gap.
Keep transaction reconciliation nearby. If one report uses gross order value while finance uses net sales after returns, choosing an attribution model does not remove that difference. The server-side tracking guide covers collection and event integrity; this page assumes the team can establish what its purchase signal means.
If an interface label differs from the help page, preserve the label and exported definition actually encountered. Do not activate another campaign merely to obtain a comparison column. Inspection should end with a reproducible observation and a decision about whether intervention is warranted.
A fictional example: normalize the comparison first
Consider two hypothetical campaigns, each spending $12,000 during the same reporting interval. Campaign A used standard delivery; campaign B used incremental delivery. Assume the account provides these modeled reporting views. These are invented teaching numbers, not Sharply Labs results or expected platform behavior.
Same reporting basis Campaign A Campaign B --- ---: ---: Standard-model credited purchases 240 200 Incremental-model credited purchases 150 160 Spend divided by standard-model purchases $50 $60 Spend divided by incremental-model purchases $80 $75
Comparing A’s $50 standard-model cost with B’s $75 incremental-model cost mixes definitions. Comparing both under the standard model favors A on that metric; comparing both under the incremental model favors B. The reversal shows why the reporting basis matters. It does not identify the better commercial intervention.
Neither row proves new-customer contribution, realized margin, or a causal treatment effect. The campaigns may have different audiences, offers, timing or exposure. Equal spend and aligned dates do not create random assignment or a credible counterfactual.
The difference between A’s 240 and 150 is also not a count of purchases that could have been acquired for free. Treat it as a model-dependent difference in credited outcomes. Do not multiply it by an acquisition cost and label the product “recoverable waste.”
For financial evaluation, specify whether the primary outcome is paid orders, first-time customers, net revenue or contribution. The e-commerce contribution-margin framework helps establish the value contract before a different reporting number authorizes more spend.
Build a delivery test around one commercial question
A useful question is narrow enough to answer: “Under the supported configuration and authorized exposure, does the proposed delivery approach produce evidence sufficient for our next acquisition-budget decision?” Write the metric, feasible design and action rules before launch.
Preserve the operating baseline
Record campaign and ad-set identifiers, delivery model, reporting view, conversion definitions, markets, creative, offer, customer exclusions, spend and material promotions. Keep the old configuration available as a reference. Retain historical exports under their original definitions.
A campaign that performed during one promotion is not automatically a clean control for a replacement launched after the promotion. If the business must change price, inventory or acquisition offers during the test, record those changes and assess how they affect interpretation. Necessary operations should remain visible.
Define an evaluation that both teams can reproduce
Choose a primary business outcome and a common reporting basis for diagnostics. Specify the counting unit and treatment of repeat purchases, cancellations, refunds and late outcomes. Agree when observations are sufficiently mature for the planned read.
A controlled comparison requires an appropriate assignment and analysis plan. Running two overlapping campaigns side by side is an operational arrangement; it does not by itself establish that differences are caused by the attribution model. If a defensible comparison is infeasible, label the work as a bounded operational pilot and narrow the claim.
Record changed constraints and acceptance conditions
Create an acceptance register with an owner and evidence for each requirement:
Configuration: the intended model and supported goal are actually selected in the new campaign.
Measurement: the event and value definitions remain consistent and receipt issues are understood.
Operations: authorized spend, inventory, offer and financial constraints can be maintained.
Interpretation: the analysis can distinguish the planned action from a reporting-definition change.
Passing the configuration check establishes that the intended setting exists. It does not establish improved acquisition. Passing measurement checks makes an outcome more interpretable; it does not guarantee sufficient precision for a budget decision.
Allow an inconclusive result
Predeclare what happens if the evidence cannot distinguish useful outcomes. Options include retaining the current approach, resolving a specific measurement gap, revising feasibility or declining further testing. An inconclusive read should not be converted into a model preference because one dashboard number looks more attractive.
Set operational stops for broken purchase collection, unauthorized expenditure or an inability to honor customer offers. Those are governance rules selected by the business. They are separate from statistical stopping rules and should be documented as such.
Is incremental attribution the same as Conversion Lift?
No. Meta’s incremental-attribution documentation describes a prediction model. A controlled lift experiment establishes a comparison between exposure conditions and measures outcome differences under a study design. As a general example, Google’s Conversion Lift documentation describes treatment and control groups. That source explains the experimental distinction; it is not evidence of Meta account eligibility or study requirements.
Selecting an attribution model is therefore insufficient evidence that your business ran a holdout experiment. If an agency proposes a lift study, ask for its assignment, exposure contrast, primary outcome, feasibility analysis, uncertainty reporting and contamination checks. Verify the applicable platform’s current access and setup separately.
An experiment can also answer a different question from a delivery comparison. Withholding a channel asks what the channel added under the tested conditions. Comparing two delivery approaches asks about their relative outcomes under the specified design. Be explicit about which intervention is being evaluated.
The incrementality and geo-holdout guide covers that broader design decision. Its feasibility requirements remain relevant even when an attractive modeled result motivates the investigation. A reporting feature does not make an otherwise infeasible experiment informative.
What an agency proposal should contain
Ask the proposed operating partner to supply a compact decision packet:
The intervention: alternate reporting only, a new delivery campaign, or a separate experiment.
The applicability evidence: dated account configuration and current official requirements.
The commercial outcome: an agreed purchase, customer or value definition connected to the budget question.
The comparison method: common reporting definitions, assignment where appropriate, known confounders and uncertainty.
The operating plan: authorized spend, changed controls, responsible owners, failure conditions and recovery actions.
The decision record: evidence needed to continue, stop, repair or call the result inconclusive.
This is a scope assessment, not a request for a guaranteed result. A partner can credibly identify that measurement repair or a smaller feasibility review comes first. A presentation that labels every discrepancy “overattribution” without testing definitions has not established the cause of the discrepancy.
The fee and deliverables should match the intervention. Exporting alternate columns, preparing a test, operating campaigns and designing an experiment are different responsibilities. Establish who owns data access, implementation, financial reconciliation and interpretation before the work starts.
When to retain the current approach or defer testing
Defer a delivery change when the conversion definition is unstable, the required configuration is unverified, an essential bid control would be lost without an acceptable alternative, or the evaluation cannot support the decision being promised. A lower modeled conversion count alone does not resolve any of those conditions.
Retain a suitable current approach while investigating the uncertainty. Keep the investigation bounded: identify the missing evidence, its owner and the decision it would change. There is little value in collecting more columns when no plausible result would affect allocation.
After a test, assess financial outcomes alongside platform reporting. The MER-versus-ROAS framework provides a separate business-level check. MER itself is not a causal experiment, and a favorable blended result does not isolate the attribution model’s contribution.
Bring the proposed change and its evidence to the conversation
For established e-commerce growth teams reviewing an agency recommendation or an internal model switch, Sharply Labs’ paid-acquisition and attribution services can be discussed within the e-commerce growth offering.
Bring redacted campaign settings, both reporting views, purchase and revenue definitions, relevant operating constraints and the budget decision being delayed. Start a scoped conversation to identify the first evidence gaps, accountable owners and a proposed validation agenda. Campaign implementation, technical investigation or experimental delivery would be agreed separately.
The conversation does not promise access to a platform feature, a completed study, causal certainty, lower CAC, higher ROAS or increased profit. Its purpose is to establish what the next decision requires before another attribution number becomes a spending instruction.