What each model asks you to measure
CPA means cost per acquisition or action, depending on the campaign's terminology. CPL means cost per lead. Neither abbreviation tells you enough to approve a campaign on its own. A CPA might be a paid subscription, an eligible application or another agreed event. A CPL might require a valid phone number, a particular location and a genuine request for information.
Begin with the event definition in plain language. Someone reading the campaign brief should be able to determine whether a particular action qualifies. Words such as valid and quality need an operational explanation: which fields are required, how duplicates are identified and what evidence supports a rejection.
Where CPL fits the customer journey
CPL can be useful when a sale needs a conversation, a quote or an offline assessment. The publisher introduces a prospect and the advertiser takes responsibility for the next stage. That arrangement puts weight on the advertiser's response process. A well-qualified inquiry can lose value if nobody follows up while the prospect is still interested.
Review lead acceptance and the later sales outcome separately. If you only count submitted forms, you may miss a source that produces fewer inquiries but more customers. Equally, a slow sales process should not automatically become a publisher-quality complaint. Agree which part of the journey each party can control and measure.
Compare customer costs, not just the price on the offer
Consider a hypothetical campaign that buys 100 accepted leads at 20 currency units each. The lead spend is 2,000. If ten leads become customers, media cost per customer is 200; if only four become customers, it is 500. Those examples exclude sales costs, refunds and other expenses, and they are not network performance figures.
A CPA campaign can make the payable event closer to the desired customer outcome, but the price may reflect that additional risk. Compare the economics over the same cohort and time window. A lead that converts several weeks later should not disappear from the evaluation simply because the first report was pulled too early.
Agree validation before traffic begins
Document the event, attribution window, duplicate rule, rejection reasons and reporting timetable. Where the campaign has several stages, use distinct event names so a registration is not confused with a purchase. Both parties should understand whether a status is provisional or final.
Everflow's postback documentation describes fields used to report conversion events. Your actual integration still needs its own approved configuration. The tracking guide explains the questions to settle before treating platform totals as comparable.
Make the choice, then review it with evidence
Use the model that your business can validate fairly and operate consistently. If your team cannot explain why a lead was rejected, changing the payout model will not solve the reporting problem. If you need a sale to justify acquisition spend, follow that sale through to the relevant revenue or retention outcome.
Record the assumptions behind the decision and revisit them when the product, market or source mix changes. Keep publisher economics in the conversation too: the EPC guide explains how earnings per click can help assess an offer from the traffic owner's side.
Put the principle into practice.
Discuss the campaign-specific requirements with MMN before committing traffic or budget.
Talk to Partnerships