A bid is the price you set for one counted advertising event. Your profit depends on what happens after that event. We built FroggyAds as a self-serve platform so you can set the bid, cap the spend, narrow the sources and read the result against accepted customer value, starting from a $50 minimum deposit. This guide shows how to work out a bid you can defend, test it with a limited budget and decide whether the next increase has earned its place.
Quick answer: an ad bid is the price you set for one counted event, such as a click or 1,000 impressions, under the selected campaign's rules. It is not your deposit, your campaign budget or your cost per customer. Work out the most one click or impression can be worth to you, set the bid below that figure, then judge it on accepted customers rather than on the price alone. FroggyAds gives you the format, targeting, bid, budget and source controls to run that test yourself.
| Section | What to check before buying |
|---|---|
| Bid | The price you set per counted event. Confirm the unit (per click or per 1,000 impressions) and the minimum for your format before you enter it. |
| Actual charge | What the campaign really spent per event. Read it from reporting after delivery instead of assuming it equals the bid. |
| Budget and deposit | The deposit funds the account (minimum $50). The campaign budget caps what one campaign may spend. Neither is a bid. |
| Accepted customer cost | Actual spend divided by the customers your business validates. This is the number that decides whether the bid stays. |
External pricing context: Google Ads: Cost-per-view definition describes Google's video-view pricing terminology. It does not define a FroggyAds buying model or a universal event price.
A bid belongs to a purchasing unit. On FroggyAds, our published starting prices are $0.003 per click for Push and Native campaigns and $0.10 per 1,000 impressions for Display. A price per click buys a counted interaction, while a price per thousand impressions buys counted exposure, so the two cannot be compared until you convert them to a shared unit. The next section shows how. These are starting prices, not recommendations. Confirm the unit and minimum for your chosen format and targeting in the campaign setup before you commit to a number.
Most bidding mistakes come from mixing four different amounts. Keep them in separate fields so each one answers one question.
| Number | Question it answers | Where to read it | Common mistake |
|---|---|---|---|
| Bid | What price did I set for one counted event? | Campaign settings | Comparing a CPC bid with a CPM bid as if both were the same unit. |
| Actual charge | What did the campaign spend per event? | Campaign reporting | Assuming a low bid means slow spend or a high bid means a higher charge. |
| Budget and deposit | How much may this campaign spend, and how much is funded? | Campaign budget and account balance | Treating the funded balance as the test budget. |
| Accepted customer cost | What did each validated customer cost? | Your order, lead or subscription records matched to spend | Treating clicks or platform conversions as final customers. |
Cost per accepted customer can rise even while the price per click falls. A cheaper set of clicks may contain fewer people who can use or pay for your offer. We recommend you judge every bid on both delivery and customer evidence, so the lowest visible number never becomes the buying objective.
Start with the event your business accepts, because that event sets the ceiling for everything else. The right definition depends on your model:
Affiliate offers: use the payout you keep after reversals or rejected leads. Some networks confirm outcomes days after the click, so note that delay before you call a recent result final.
Ecommerce: use contribution per accepted order after product, shipping, payment and return costs, not revenue.
Lead generation: count an enquiry your sales team accepts. Duplicates, wrong areas and unreachable contacts belong in the calculation.
SaaS and apps: decide whether you are buying registrations, activated trials or paid subscriptions. Those events arrive at different times and carry very different value, so a bid set from registrations alone can overpay for people who never activate.
Then write down the eligibility rules that change value, such as supported countries, devices or payment methods, and apply the matching geo and device targeting in FroggyAds. Reserve part of your test allocation for uncertainty. Your first campaign may not reveal a stable conversion rate, so treat any assumed rate as an assumption until your own data can challenge it.
The calculation below uses invented inputs to show the arithmetic. It is not a FroggyAds forecast or a suggested bid.
| Hypothetical model | Accepted outcome and value | Assumed click-to-outcome rate | Break-even per click |
|---|---|---|---|
| Affiliate sale | $12 payout after reversals | 0.5% | $12 × 0.005 = $0.06 |
| Local lead | $8 contribution per accepted enquiry | 2% | $8 × 0.02 = $0.16 |
| SaaS paid plan | $30 contribution per paid subscription | 0.2% | $30 × 0.002 = $0.06 |
If the affiliate buyer wants to keep 30% of the payout as margin, the bid ceiling falls to $0.06 × 0.70 = $0.042 per click. That ceiling is a limit, not a starting bid. It tells you the price at which a campaign stops being worth running, so you can begin lower and move up only while results justify it.
To compare formats, convert everything to one unit. An effective cost per click from a CPM purchase equals CPM ÷ (1,000 × click-through rate). A hypothetical $0.10 CPM at a 0.5% click-through rate buys 5 clicks per 1,000 impressions, or $0.02 per click. In the other direction, a $0.04 CPC bid at the same rate equals $0.04 × 0.005 × 1,000 = $0.20 per thousand impressions. Treat click-through rate as an assumption until your campaign supplies it, and remember that post-click quality still decides the customer cost.
Our $50 minimum deposit is what it takes to fund an account. It does not tell you how much evidence a bid test needs. Work backwards from the outcomes you want to see instead of starting from the balance.
| Step | Formula | Hypothetical figures |
|---|---|---|
| Set the review threshold | Accepted outcomes you want before judging the bid | 10 accepted outcomes |
| Estimate clicks needed | Outcomes ÷ assumed click-to-outcome rate | 10 ÷ 0.005 = 2,000 clicks |
| Estimate test spend | Clicks × planned average charge | 2,000 × $0.04 = $80 |
| Compare with funding | Test spend against deposit and loss limit | $80 exceeds a $50 minimum deposit, so fund more or revisit the plan |
The last row matters. If the estimate exceeds the funds you are willing to risk, change the plan before launch. You can lower the review threshold and read the result cautiously, test an offer with a higher accepted-outcome rate, or narrow targeting so spend concentrates on the most relevant audience. Ten outcomes is a working review point, not statistical proof, and no single test budget fits every payout, rate and risk limit. Set a daily cap and a total cap that match the loss you have agreed to accept, then keep that allocation separate from the bid.
Ask one question per test, for example whether a higher bid increases useful delivery inside an audience you already know. Hold the offer, destination and accepted-outcome rule steady while you do it. If you change creative, geography and bid together, the result can still be useful, but you cannot credit the bid. Log the combination as a new buying condition instead.
Keep a short change log with the campaign identifier, format, entered bid, targeting and source-list settings, destination version, review date and the reason for the change. This lets an agency or a second media buyer tie the number in the account to the result, and stops a copied campaign or revised landing page from being mistaken for the original comparison.
Separate new-offer tests from bid adjustments on an established campaign. A new offer carries uncertainty about audience response and page performance, and any price change on top of it is hard to read. An established campaign with a known baseline is the cleaner place to learn what a bid step actually does.
Each row resolves a different way a bid can mislead you. The useful output is a number with a unit, a spending limit you understand and a customer review you can repeat. Use the controls available in your FroggyAds campaign instead of importing a strategy or report field from another platform.
| Decision layer | Operating requirement | Evidence required |
|---|---|---|
| Buying unit | Confirm whether the number prices a click or 1,000 impressions. | Convert to one unit before comparing formats. |
| Break-even value | Calculate the ceiling from rate and contribution per accepted outcome. | Keep the inputs and label each one as assumed or measured. |
| Offer eligibility | List the countries, devices and conditions in which the offer can convert. | Apply matching targeting and source controls. |
| Tracking | Test that conversion tracking records the outcome you will pay for. | Complete a test conversion before heavy spend. |
| Spending limit | Set the daily and total cap for this comparison. | Keep it separate from the bid and from the account balance. |
| Delivery volume | Check whether the campaign delivered enough events to read. | Investigate narrow targeting and approval status before blaming the bid. |
| Review date | Choose a date that allows for delayed or reversed outcomes. | Mark pending records so they are not read as failures. |
| Next adjustment | Name the single condition the next change should test. | Compare the added spend and added customers before keeping it. |
Prepare the first buying instruction
Choose FroggyAds when you want a self-serve traffic purchase with hands-on control of format, targeting, bid, budget and sources. Bring your break-even figure, your destination and a capped test allocation. We give you the campaign settings to launch it and the reporting to compare spend with your own accepted outcomes, so your first review explains what the bid bought instead of only showing that traffic arrived.
Create My Free Account
Match the purchase to the message
We offer Push, Native, Display, Pop, Video and Interstitial within the verified FroggyAds format range, all bought through one self-serve account. Each format creates a different advertising experience and prices a different unit. Confirm the unit and asset requirements for the format you select, then judge it by its customer route. Comparing a Display impression with a Pop visit as if both were the same event can make a low price look more informative than it is.
Create My Free Account
The table separates what we can state from what you must check in the campaign setup. Starting prices show where our pricing begins for those formats. They do not predict the bid you will need for competitive delivery in your chosen geography.
| Format | Starting price reference | Confirm in the campaign setup | Bidding question to answer |
|---|---|---|---|
| Push | From $0.003 per click | Minimum for your geo and targeting | Does your click-to-outcome rate support the per-click price? |
| Native | From $0.003 per click | Asset requirements and minimum for your targeting | Does the ad's message pre-qualify clicks for your offer? |
| Display | From $0.10 per 1,000 impressions | Banner sizes and the click-through rate you can assume | What effective cost per click does the CPM imply? |
| Pop | Check the unit and minimum shown for your campaign | Destination behaviour and traffic-source controls | Do visits convert at a rate that supports the price? |
| Video | Check the unit and minimum shown for your campaign | Creative specifications and the event being priced | Which event does the price cover, and how does it connect to your outcome? |
| Interstitial | Check the unit and minimum shown for your campaign | Creative requirements and the pricing unit | Is the unit comparable with your other formats after conversion? |
Our platform connects to a global ecosystem of more than 750 SSP integrations, and our published scale figure is 20B+ impressions. Those numbers describe the inventory environment, not the volume any single bid will receive. Delivery depends on your targeting, your price, the creative and the campaign settings. That is why we suggest starting with one format and one market so the first result is easy to interpret.
Manual bidding gives you a price instruction you can inspect and change one step at a time. SmartCPC can assist an applicable FroggyAds bidding workflow, so confirm its availability and operating scope for your campaign before you plan around it. Neither option removes the need to validate customer outcomes, and you should not assume that a conversion-value strategy, shared-budget rule or auction-time algorithm from another platform exists here.
| Approach | Use it when | You still own |
|---|---|---|
| Manual bid | You have a break-even CPC and want to see the direct effect of each change. | The bid ladder, the review dates and the decision to raise or cut. |
| SmartCPC | The workflow applies to your campaign and you want to compare automation with your own settings. | The accepted-outcome rule, the budget cap, the source lists and the final keep-or-stop decision. |
Our recommendation is to compare the two as separate tests. Run a manual campaign and a SmartCPC campaign with the same offer, destination, sources and budget cap, then review both at the same date on cost per accepted customer. That way you adopt automation because your data shows it works for your offer, not because of its label.
The example below shows why an account average can hide the cost of a bid increase. An affiliate buyer has a hypothetical $12 payout and a 30% margin target, so the cost per accepted outcome must stay under $8.40. All figures are invented to illustrate the review, and they are not a FroggyAds result or recommended bid.
| Round | Bid entered | Average charge per click | Clicks | Spend | Accepted outcomes | Cost per accepted outcome |
|---|---|---|---|---|---|---|
| 1 | $0.030 | $0.03 | 2,000 | $60 | 10 | $6.00 |
| 2 | $0.045 | $0.04 | 3,000 | $120 | 13 | $9.23 |
| Added by the increase | n/a | n/a | +1,000 | +$60 | +3 | $20.00 |
Round 2 delivers more volume, and its average of $9.23 sits below the $12 payout, so the account total looks acceptable. The added purchase tells a different story: $60 of extra spend bought three extra outcomes, or $20 each, which is above the payout. The sensible decision is to return to the Round 1 bid and test a smaller step, such as $0.035. The example also separates bid from charge. How far the actual charge falls below the entered bid depends on the campaign's conditions, so read it from reporting rather than assuming it.
Work through the symptom, not the instinct to raise the price. A higher bid cannot repair an unapproved campaign, a broken tracking step or an offer that visitors cannot use.
| Symptom | Check first | Likely action |
|---|---|---|
| Little or no delivery | Campaign approval and status, budget caps, how narrow the geo, device and source targeting is, and the destination. | Fix any block, widen targeting if it is too tight, then raise the bid in small steps and record each effect. |
| Delivery but no outcomes | Conversion tracking, destination function and offer match to the ad. | Repair the measurement or page before changing the price. |
| Outcomes at too high a cost | Click-to-outcome rate and spend by source and time period. | Exclude or separate weak sources and lower the bid where the data supports it. |
| Spend arriving faster than planned | Daily budget cap, the latest bid change and the mix of sources. | Pause or tighten the cap, keep the records and restart with a stated reason. |
| Good cost at low volume | Eligible audience size and the marginal cost of added volume. | Raise the bid or widen targeting one step at a time and compare the added results. |
Two groups of traffic can carry the same price per click and produce very different customers. Use the source detail the campaign reports to find where the difference comes from, and apply whitelists and blacklists so you keep the sources that work and exclude those that waste spend. Where a dimension is not available, say so and keep the conclusion at the level your records support.
FroggyAds integrates with Adscore and applies internal quality controls to help screen invalid traffic. They support your decisions, but they do not replace a review of accepted outcomes. A click that passes a quality check can still fail your offer because of device, location, timing or message mismatch. Keep rejection reasons specific: a duplicate lead, an unsupported device, an unserviceable address and a confirmed invalid interaction each call for a different fix.
When a customer route breaks or spend changes without explanation, limit the affected delivery. Preserve the time and the settings, correct the cause and resume for a stated reason. A short pause protects the rest of your allocation and keeps the earlier evidence usable.
An exaggerated promise brings clicks that tell you little about what a bid is worth. State the offer accurately in the creative and make the next step obvious. If customers need to subscribe, book or deposit, prepare them for that commitment before the click. A lower price per event cannot compensate for a message that sets the wrong expectation.
Look at the first screen after the ad interaction. It should continue the same product, terms and next step. A buyer who adjusts bids while the destination redirects to a different offer is changing the price of an unstable purchase. Correct the route first and treat the corrected version as a new comparison.
Agree who can change the offer and who tells the media buyer when it changes. A stock shortage, a new trial rule or an expired promotion can alter acceptance without any bid change, so record the date beside the campaign result.
Specify the unit, the break-even ceiling and the reason for testing a particular bid. Confirm the eligible offer, the accepted outcome and the spending cap. This is a readiness sequence rather than a fixed calendar: move on when the information exists.
Save the initial settings and run a test conversion through tracking. Check that campaign identifiers can reach your own customer record. If attribution is incomplete, decide whether a campaign-level conclusion is still useful before you promise a source-level comparison.
Apply one bid change inside the authorized allocation and watch delivery, source mix and spend pace. Note any change in offer, targeting or measurement beside the adjustment so you can tell what actually moved the result.
Compare the added spend with the added accepted outcomes, including pending or reversed records. Keep the change, return to the earlier bid or run one narrower test, and write the reason and next review date down.
Make the next adjustment purposeful
Our self-serve workflow lets you turn a prepared bidding question into a live traffic test. Keep the eligible offer, the unit and the capped amount together, then use reporting and conversion tracking to see what the price actually bought. Choose FroggyAds for practical campaign buying when you want a setting you can operate and a customer outcome you can validate.
Create My Free Account
A bid that works at one spend level may attract a different mix of traffic when it rises. Review the next block of events separately from the earlier one, as the bid ladder above does, and ask whether the added volume is still eligible and profitable. Do not assume the earlier conversion rate will continue because the campaign name and landing page are unchanged.
Change one dimension at a time when you scale: the bid, the daily budget, a new geography or a new format. Then watch the cost of the additional results rather than the account average. If you widen several things at once, a rise in cost per customer has no clear cause.
Check that your business can fulfil the extra demand. A service team with a full calendar values another enquiry differently from an empty one, and a shop with limited stock may need to restrict the offer. The platform cannot see those limits, so bring them into the bidding decision before you spend. Keep the last bid and customer calculation you understood. If a new purchase becomes hard to explain, that record gives you a narrower step to return to, although a return does not guarantee the earlier result will recur.
We recommend FroggyAds for bidding tests because the controls match the questions this page raises. You choose the format and see its unit, so you do not compare mismatched prices. You set the bid, the budget and the targeting yourself, so a result traces back to a decision you made. Whitelists and blacklists let you act on what source data reveals, and Adscore integration with our internal quality controls helps screen invalid traffic. Because the account starts from a $50 minimum deposit, you can start with a small, capped test and increase spend only on campaigns that earn it. Your business supplies the accepted customer definition, which keeps our media workflow tied to the commercial reason you are buying.
The bid is the price you set for one counted event, such as a click or 1,000 impressions. The charge is what the campaign actually spends per event, which you read from reporting after delivery. The budget caps how much a campaign may spend, and your deposit funds the account. Keep these separate, and add a fourth number you calculate from your own records: cost per accepted customer.
The minimum deposit is $50, and it only funds your account. It does not set a bid or a campaign budget. Starting prices begin at $0.003 per click for Push and Native and $0.10 per 1,000 impressions for Display. Confirm the minimum and unit for your chosen format and targeting in the campaign setup, because a starting price is not a recommendation for competitive delivery.
Convert both to the same unit using your expected click-through rate. Effective cost per click equals CPM divided by (1,000 times CTR), so a hypothetical $0.10 CPM at a 0.5% CTR gives $0.02 per click. Going the other way, a CPC bid times CTR times 1,000 gives the equivalent CPM. Then compare cost per accepted customer, because CTR and post-click quality differ by format. Treat CTR as an assumption until your campaign shows it.
Multiply the share of clicks that become accepted customers by the contribution per customer, then subtract the margin you want to keep. As a hypothetical, a $12 payout at a 0.5% rate gives $0.06 break-even per click, and keeping 30% lowers the ceiling to $0.042. Use your own accepted-outcome rate and include reversals, refunds and non-media costs. These figures are examples, not suggested bids.
Work backwards from the evidence you need. As a hypothetical, 10 accepted outcomes at a 0.5% rate needs about 2,000 clicks, and at $0.04 per click that is roughly $80, which is more than the $50 minimum deposit. Cap the total at a loss you accept. Ten outcomes is a working review threshold, not statistical proof, and no single test budget fits every payout, rate and risk limit.
Use manual bidding when you have a break-even CPC and want to see the direct effect of each change. SmartCPC can assist an applicable FroggyAds bidding workflow, so confirm its availability and scope for your campaign. Compare it as a separate test against a manual campaign with the same offer, sources, budget and review date. In both cases your accepted-customer records decide which approach to keep.
Check status and approval first, then targeting breadth, budget limits and the destination before raising the bid. Narrow geo, device or source settings can limit eligible inventory, and a bid that is too low for your format and targeting may win little. If those settings are sound, raise the bid in small steps and record the delivery change after each one instead of making one large jump.
Compare the added spend with the added accepted outcomes, not with the account average. In a hypothetical example, raising a bid from $0.03 to $0.045 moved the average to $9.23 per outcome, yet the extra $60 bought only three more outcomes at $20 each. If the marginal cost exceeds the value of an outcome, return to the earlier bid and test a smaller step.
Use whitelists and blacklists to keep sources you trust and exclude those that waste spend, and review results by source where reporting provides it. FroggyAds integrates with Adscore and applies internal quality controls to help screen invalid traffic. These controls support, but do not replace, your own review of accepted outcomes before you raise a bid.
Set up conversion tracking for the outcome you will actually pay for, then test it with a conversion before spending heavily. Carry campaign identifiers into your own order or lead records where supported, and note pending or reversed outcomes. Without a reliable count of accepted customers, a bid change cannot be judged, so fix tracking before adjusting the price.
These existing Google and IAB references provide further context for event pricing, auctions and advertising operations. Google product descriptions apply to Google's own service; the retained IAB PDF is a dated study reference. Use current FroggyAds campaign settings for our feature availability and use your own customer records for the value of the purchase.
Keep the working numbers beside their assumptions so an account manager can hand the campaign to another buyer without losing context. Replace the illustrative inputs with your records and update the conclusion whenever a material buying condition changes.
Write the bid exactly as configured, including its unit. Add actual spend and counted events for the review period, and label any average event cost as observed rather than entered. Keep the customer denominator next to the cost, and state when acceptance is decided, because a submitted lead is not automatically a qualified enquiry.
Record who operates the campaign and who supplies the customer judgement. For an agency, agree how a client reports rejection reasons and offer changes. Distinguish an adjustment inside the agreed test from a request for more spend, so the account balance never becomes the default answer to how much a campaign should spend.
Identify the rate or acceptance figure that moves your break-even value most. In the hypothetical affiliate example, a fall in the accepted-outcome rate from 0.5% to 0.25% halves the $0.06 ceiling to $0.03. Choose the test that checks that assumption before you commit the whole allocation to a price experiment.
Confirm that spend and counted events cover the intended period and that the business record reflects acceptance, rejection and later value. Close with a concrete action and its reason: keep the bid, narrow eligibility, repair the destination or authorize another measured comparison, and attach the settings and customer totals so the next review has a clear reference.
Bring your offer, buying unit and initial allocation to FroggyAds. We provide the self-serve campaign controls to run the traffic test; your accepted customer records show whether the next bid should stay, fall or be investigated further.
Create My Free AccountA useful adjustment has a purpose beyond increasing activity. You may want to learn whether delivery can grow inside a source group you already trust, or whether the added customer cost stays acceptable. State that purpose before you change the number, and evaluate any new bidding tool such as SmartCPC as its own comparison.
Before entering a bid: confirm the unit, the break-even ceiling, the prepared destination and the amount authorized for the test. Save the starting configuration and the customer rule.
Before renewing the purchase: check actual spend, accepted customers and any material change in sources. Explain the gap, or choose the next limited comparison that can investigate it, and use outcomes from the agreed review date instead of treating every recent event as final.
| Checkpoint | Buying action | Evidence to keep |
|---|---|---|
| Price | Keep the entered bid and its purchasing unit together. | Record observed spend and counted events separately. |
| Value | Use your accepted customer rule and review date. | Include rejection and cancellation adjustments. |
| Action | State why the current bid should stay or change. | Authorize the next amount according to the remaining uncertainty. |
Hypothetical comparison: a $90 purchase produces six accepted orders, or $15 per order. A later $60 purchase produces three, or $20 per order. The combined $150 divided by nine is about $16.67, but that average hides the cost of the added purchase. These invented figures illustrate the review and do not describe a FroggyAds result or recommended bid.
Use FroggyAds when you want campaign settings you can operate and a traffic test you can review against your own accepted customer value. We help you make the next purchase purposeful, from the selected format to its reporting. Create your free FroggyAds account.
Set your bid from break-even value per click or per thousand impressions, not from the lowest price on the screen. Keep the deposit, budget and test allocation separate from the bid, change one variable at a time, and judge each step by the marginal cost of accepted customers. With FroggyAds, you can turn that prepared decision into a capped, practical traffic test.
