Value measurementChoose the valueUse transaction revenue, contribution value or a documented lead-quality proxy. Protect the payloadSend value, currency and event identity consistently across browser, server and postback paths. Reconcile the resultCompare reported value with orders, refunds, approvals and finance records before optimizing.
Track conversion value, not only conversion count
Conversion value tracking attaches a defined monetary amount or estimated value to each recorded action. It helps you distinguish a small order from a more valuable customer before moving budget. We recommend choosing the value basis, retaining its currency and checking it against your business records. Use our FroggyAds campaign and source reporting alongside those records to find traffic worth testing for more accepted revenue, leads or subscriptions.
Which value should guide your campaign budget?
Quick answer: Use a confirmed amount or a clearly labelled estimate that matches the buying decision. Keep sales revenue separate from margin, preserve currency and event identity, and check refunds before treating a source's reported return as money available to scale.
| Value approach | When to use it |
|---|---|
| Fixed value | Assign the same documented expected amount when one accepted action has similar economics across the cohort. Recheck the assumption as close rates or contribution change. |
| Transaction-specific value | Send the individual order amount and explicit currency when baskets or commissions vary. Reconcile later cancellations against the original transaction. |
| Estimated lead contribution | Keep the accepted lead stage and historical close probability visible. Label the result as a modelled estimate, separate from collected revenue. |
For the distinction between fixed and transaction-specific values, see Google Ads: About conversion values. Its bidding features belong to Google Ads; use the separate tracking instructions and controls supported by your FroggyAds campaign.
Core controls
A campaign can trust value only when the business meaning is explicit
Connect the commercial formula, event payload and correction process before any value metric influences spend.
Business meaning
Name the exact commercial basis and keep estimated lead value separate from confirmed transaction amounts.
Technical contract
Specify the numeric format, currency, stable transaction reference, event time, accepted range and response to missing data. Reject malformed or impossible values.
Value ownership
Assign owners for pricing, margin, lead scoring, refunds and model changes. Record when a value rule changes so historical comparisons remain interpretable.
Review criteria
Choose between static and dynamic conversion values
A static value assigns the same amount to every occurrence of a conversion action. It can be useful when the action has a consistent expected value, such as a qualified appointment with a stable close rate. A dynamic value sends the amount associated with the individual transaction or outcome. It is usually more informative for ecommerce, subscriptions, bookings and orders with different basket sizes.
Dynamic value should reflect the field the business is prepared to optimize. Gross revenue is easy to understand but can reward low-margin products. Net revenue can account for discounts and taxes according to the company rule. Contribution value can better represent what remains after variable costs, although it requires reliable cost data. Document the choice in plain language and use the same definition in reporting.
For lead generation, value can be a governed proxy based on qualification stage, historical close rate and expected contribution. Avoid arbitrary numbers chosen only to make dashboards look attractive. Re-estimate the proxy when sales acceptance or economics change.
Review criteria
Illustrative lead economics: a hypothetical accepted lead with a 20% close probability and $100 contribution per completed sale has $20 expected contribution before advertising and lead-handling costs. Record the historical cohort behind both inputs and label the result as an estimate. A revised close rate changes the estimate; it does not add cash to a customer record or prove that the traffic caused the sale.
Decision workflow
Approve the value field before the campaign uses it
Begin with the business amount you can defend, agree how the receiving tracker stores it and test a corrected event before comparing paid sources.
FroggyAds campaign action: choose one accepted-value basis for the first source test. We recommend keeping order revenue and lead estimates in separate reports so you can explain which customer outcome supports the next traffic purchase.
Define what one value number means
Agree whether the campaign receives order revenue, contribution, qualified-lead value or another measure. The same number cannot safely serve several definitions.
Create My Free Account
Measurement note
Design the value payload as a data contract
Every value event should include a stable event or transaction ID, numeric value, ISO currency code, conversion action and event timestamp. Define whether the number includes tax, shipping, discounts or recurring revenue. Set allowed ranges and decimal precision. A value of zero may be valid for a low-priority action, but it should not silently replace a missing value.
Where both routes support the same event identifier, preserve it across browser and server notifications about one business outcome. If a postback or server event retries, the receiver should be able to recognize the original event rather than add value repeatedly. Keep raw request and response logs without exposing personal data.
Validate currency before conversion. If campaigns operate in several currencies, preserve the original amount and currency, then apply a documented exchange-rate source and timestamp for consolidated reporting. Do not mix dollar, euro and local-currency amounts in one numeric column without a currency dimension.
Measurement note
Operating rule
Handle refunds, cancellations and delayed quality
A purchase value can change after the first event because of refunds, chargebacks, cancellations or partial fulfillment. Decide whether the advertising platform receives an adjustment, whether finance reporting uses a net value later, or whether both views are preserved. The method should match platform capability and business risk.
Lead value often matures through stages. A submitted lead may later become qualified, approved, deposited or retained. Send stage-specific events or update the backend value model using stable lead IDs. Avoid counting each stage as an independent customer outcome unless the reporting clearly distinguishes progression from additional conversions.
Use a maturity window before evaluating value-based performance. Recent conversion value can be incomplete when high-value outcomes take longer to approve. Pair the value model with conversion lag analysis so new sources are not cut because their revenue or lead quality arrives later.
Operating rule
FroggyAds campaign action: give each source the same time to accumulate accepted orders and later corrections. Our campaign reports supply the media groups; your order or CRM records establish the amount that remains after rejection or refunds.
Test the value path before optimizing spend
Send representative events through the complete tracking route and reconcile currency, duplicates and later adjustments in the advertiser backend.
Create My Free Account
Quality control
Reconcile value before using it for automated decisions
Compare total tracked value with the backend for matched event IDs. Check count, gross value, average value, currency distribution and the number of missing or zero values. A matching conversion count can still hide a value problem if one field is truncated, rounded, duplicated or assigned to the wrong event.
Reconcile by cohort and conversion age. If a platform assigns value back to click date while finance reports payment date, calendar totals will differ even when the underlying orders match. Use order-level samples and interaction cohorts to explain the bridge.
Set alerts for impossible values, sudden average-value changes, currency shifts and a rise in events without value. Pause value-based optimization when the feed is materially wrong. A bidding system can react quickly to bad value signals, so the rollback rule should be prepared before launch.
Quality control
Review checkpoint
Use value metrics that match the decision
Total conversion value shows the amount attributed under the selected method. Value per conversion separates quality from volume. Conversion value per cost is an attributed return measure, often expressed as ROAS. Value per click or per thousand impressions can help compare sources when conversion rates differ.
Attributed value is not automatically incremental profit. It can include outcomes that would have happened without the ad, and it may use revenue rather than margin. Use incrementality testing for causal questions and break-even thresholds for economic limits. Keep the language precise when reporting to finance or leadership.
For source optimization, combine value with sample size and stability. One large order can make a small source look exceptional. Use minimum conversion counts, winsorized or segmented views where appropriate, and a holdout budget before scaling on a volatile average.
Review checkpoint
Readiness scorecard
Reconcile accepted amounts before moving media spend
Match event identifiers and currency first, compare count and total accepted amount second, then examine missing values and large orders. That sequence distinguishes a tracking defect from a real difference between traffic sources.
Meaning clear
Dynamic where needed
Currency valid
Event ID present
Refunds handled
Lead model governed
Totals reconcile
Change log kept
FroggyAds campaign action: bring the verified value definition into your campaign brief. We can help you plan the traffic test while your team confirms the receiving system, event fields and reconciliation process for the selected setup.
Use value to distinguish sources that counts cannot
Compare accepted value by FroggyAds campaign and source after maturity. We recommend scaling only when the value advantage survives a new cohort.
Create My Free Account
Worked scenarios
Choose a source action from the settled value pattern
A larger basket, a falling lead acceptance rate and an incorrect currency each require a different response. Diagnose the pattern before rewarding or stopping a source.
Same CPA, different order value
Two sources generate purchases at the same CPA, but one has twice the net value per order. Confirm that product mix, refunds and currency are comparable, then use value per cost and contribution limits to direct more test budget to the higher-value source.
Lead volume grows but sales quality falls
The campaign reports more lead conversions, yet approved opportunities decline. Add governed stage values or separate qualified events, preserve the original lead count for funnel analysis and optimize only after the quality signal is stable.
A currency bug inflates ROAS
A local-currency amount is reported as dollars without conversion. Stop value-based decisions, preserve raw events, repair the currency mapping and backfill only through a documented method. Do not hide the incident by editing aggregate reports.
Limits
Separate recorded value from incremental profit
Recorded conversion value describes a transaction or estimate; it does not establish that advertising caused the outcome. Attribution and incrementality remain separate questions.
Value models can encode business bias. Review lead weights, margin assumptions and exclusions with sales or finance owners, not only the media team.
Rollback rule
If the value feed breaks, retain source and order records, restore the last verified campaign settings and correct the affected event path. Reconcile the repaired amounts against their original identifiers before using the revised source comparison to buy more traffic.
Operating record
Create a value governance record before optimization depends on it
Every conversion value should have an owner, a formula and a version. Record whether the value represents gross revenue, net revenue, contribution margin, predicted lead value or another business measure. Include the currency, tax treatment, discounts, shipping, payment fees, expected refunds and the time horizon used for delayed value. Without that contract, two teams can send technically valid numbers that describe different economics.
Use stable identifiers to connect the initial conversion with later changes. An order can be refunded, partially returned or upgraded. A lead can be rejected, approved or converted to a sale. The update path should prevent a later status from becoming a second independent conversion. Keep the original transaction reference and record whether the reporting destination supports adjustments, restatements or only forward-looking value improvements.
| Governance field | Required definition | Control |
|---|---|---|
| Value basis | Revenue, margin, qualified lead score or predicted value | Finance and marketing approval |
| Currency | Currency code and conversion timing | Reject missing or unexpected codes |
| Adjustment policy | Refund, cancellation and delayed-quality treatment | Transaction-level reconciliation |
| Version | Formula version and effective date | Annotation in campaign and reporting records |
Monitor both volume and value distributions. A stable total value can hide a payload problem when a few extreme values compensate for many missing ones. Check count, sum, median, percentiles, zero-value rate, currency mix and the share of events outside an expected range. Investigate abrupt changes before an automated system shifts spend toward the affected segment.
When a value model changes, avoid comparing the new period directly with the old one without an annotation or bridge analysis. A higher reported ROAS can come from a formula change rather than stronger traffic. Preserve enough history to explain that difference to media buyers, finance and management.
Questions
Track conversion value, not only conversion count: FAQ
Practical answers for advertisers, analysts and media buyers.
What is conversion value tracking?
It attaches a monetary amount or an explicitly defined value to a conversion. That amount may be transaction revenue, contribution after relevant costs or an estimate for a qualified lead. State which one you use. For a FroggyAds campaign, this lets you compare sources that produce the same number of actions but different business value, rather than optimize only for the lowest cost per conversion.
Should I use a fixed value or a different value for each conversion?
A fixed value can suit actions with reasonably similar economics, provided the assumption is documented. Use transaction-specific values when order amounts or accepted commissions vary. Keep the value tied to the real event and the fields supported by the receiving system. Do not use one attractive default amount for every sale merely because it makes campaign returns look stronger.
How can two campaigns have the same CPA but different value?
Imagine two hypothetical campaigns each spend $100 and produce five orders. Both have a $20 cost per order. If their confirmed order revenue is $150 and $400 respectively, the revenue-to-media-spend ratios are 1.5 and 4. Those figures still exclude product and operating costs. Use our source-level reporting with your business records to investigate that difference instead of declaring the campaigns equal on CPA alone.
Which value should I use for a lead before a sale is confirmed?
Use an evidence-based expected value tied to accepted lead stages, or keep the lead unvalued until a dependable model exists. Document the assumptions and update them from closed outcomes rather than assigning an attractive arbitrary amount. A lead score or estimated future amount is not cash revenue and should remain labelled as an estimate in the campaign comparison.
Should conversion value mean sales revenue or profit?
Choose the measure that answers your decision and name it clearly. Revenue describes the sale amount; contribution accounts for the costs included in your business calculation. A revenue-to-ad-spend ratio is not automatically profit. When comparing FroggyAds sources, use consistent treatment of discounts, product costs and reversals so a higher order total does not hide a less valuable customer.
What needs to be configured for dynamic conversion values?
Pass the verified amount, currency, transaction identifier, status and relevant product detail supported by the receiving system at the confirmed event. Agree how discounts, tax, shipping, refunds, cancellations and repeated updates affect the record. Use the actual campaign and tracker instructions rather than assume that another platform's value field or update method is compatible with FroggyAds.
Which checks keep conversion-value reports reliable?
Reconcile totals and sample transactions with order or CRM records, monitor missing currency and extreme values, and track late adjustments. Report coverage so decision makers know how much accepted activity actually carries a value. Keep test events separate from customer results before using the report to increase a traffic-source budget.
Why can conversion counts look correct while reported value is wrong?
The count may be right while a default value, currency mismatch or unit error changes the total. For example, sending 4999 where the receiver expects 49.99 inflates the amount one hundredfold. Check individual transaction IDs, the decimal convention and the receiver's documented units. Also verify refunds and discounts before changing bids in response to an apparent improvement in return.
Does sending conversion value automatically enable value-based bidding?
No. Recording a value and using it as an automated bidding input are different capabilities. Verify the selected platform, campaign and optimization option before assuming the value feed controls bids. With FroggyAds, your validated customer values can still inform source and budget decisions. Do not treat a successful value notification as proof of a particular SmartCPC algorithm or a target-ROAS feature.
When can I rely on conversion value to increase campaign spend?
Increase confidence when the current feed reconciles with business records, corrections work and recent results have had enough time to settle. Review the additional spend separately after any expansion. Our source controls help you concentrate a FroggyAds campaign on the traffic that supports your economics, while the underlying value definition keeps the comparison honest as products, commissions or customer quality change.
Continue the workflow
Use the related tracking and break-even guides
Confirm the event route, prevent duplicate order value, allow for delayed outcomes and calculate the economic limit before choosing your next FroggyAds traffic test.
Run a measured campaign
Launch a source test with accepted-value reporting
Start a focused test with FroggyAds self-serve advertising, one offer and a budget limit you can support. Compare our campaign and source reports with your accepted customer values, then expand the source test when the evidence supports your next purchase.
Commercial value contract
Define the value that may move campaign budget
The useful number is the one your business can reconcile, explain and update when the customer outcome changes.
Name the value basis before sending an amount: gross order revenue, net revenue, contribution after declared variable costs, approved lead value or another governed measure. Add the currency, event ID, event time, acceptance status and formula version. If the number is an estimate, keep that label in every report so it is not presented to the media team as collected revenue.
Test a low, typical and high value through the complete route. Confirm decimal precision and currency at every handoff, then repeat an event to verify deduplication. Follow one order through a refund and one lead through rejection or approval. The value feed is not ready for a budget rule until later corrections reach the record used by the decision.
Read count, value and maturity together
Compare matched event count, total accepted value, value per accepted event and the distribution of values. One large order can make a small source look exceptional, while a matching total can hide missing currency or a default amount applied to many conversions. Use mature cohorts so delayed approvals and cancellations do not reward the newest source too early.
FroggyAds campaign and source reporting gives your team the media-side groups for the comparison. Your backend remains the commercial reference for accepted value. Move budget in a bounded step when the value advantage survives reconciliation and a new cohort; roll back when the payload or business definition changes materially.
Buyer rule
Never let an undefined or unreconciled value field control spend. Keep the prior campaign setting available until the corrected value path proves itself on new events.
Buyer decision tool
The conversion-value data contract
This page is for ecommerce, lead-generation and subscription teams that need budget decisions to distinguish high-value and low-value outcomes. Use it to send and reconcile conversion values that reflect the advertiser's real business event. The decision is which value is known at conversion time, which adjustments arrive later and which value belongs in campaign optimization. The accepted outcome is reconciled accepted value in a declared currency after cancellations, rejection or quality adjustments.
| Evidence field | What your team should record |
|---|---|
| Event identity | Name the exact purchase, qualified lead, activation or subscription event and define when it becomes accepted. |
| Value basis | State whether the value is revenue, margin, approved lead value or another business measure; never leave the unit implied. |
| Currency and precision | Send an explicit currency and consistent numeric precision, then test how every receiving system stores them. |
| Adjustment path | Record how refunds, cancellations, duplicate events and delayed quality decisions correct the original value. |
Equal purchase counts can hide different accepted value
Two campaign cells produce the same number of conversions, but one contains larger accepted orders and the other has more cancellations. A value contract keeps currency, event identity and later adjustments visible before spend moves.
Attach the value contract to your next FroggyAds campaign
- Validate a low, typical and high-value event end to end before using value in a budget rule.
- Reconcile event counts first, then reconcile total value and the distribution of value per accepted event.
- Keep provisional value separate from accepted value when downstream review can change the outcome.
- Use FroggyAds source and campaign evidence to allocate spend only after value records are commercially complete.
Make accepted value part of the campaign brief
Define the amount, currency, correction path and maturity window before the first traffic purchase. Then use FroggyAds campaign and source reporting to compare where accepted value is created, and expand only after the advantage repeats.