Create Ad Campaign Online
By FroggyAds. Create an online ad campaign by connecting a business goal to an eligible audience and suitable format. Name a verifiable action and clear spending rule.
Build a measurable online campaign in seven decisions
An online campaign needs a defined offer, eligible audience, supported format, accepted action and cost boundary before delivery begins.
Start with one buying decision: which offer, audience, format, accepted action and cost boundary are you testing? FroggyAds gives you a self-serve way to work with the format and targeting controls currently available in your account. Name the action and limit before configuring delivery, so every setting serves the same business question.
Start with a narrow question rather than a menu of settings. For example, can the approved offer produce a qualified lead from one eligible market through a format your team can supply? If the first test changes the offer, market, format and destination together, even a strong result will not show which choice mattered. Hold the other decisions steady and keep follow-up tests separate.
Start with the offer and accepted action. Confirm which audience conditions apply. Choose an available format that fits your creative. Match the final destination to the ad's promise. Set an approved spend boundary. Define when accepted outcomes are mature enough to review. This order keeps the creative, settings and measurement attached to one campaign decision.
Google Ads’ own create-ads guidance recommends making the ad relevant to the customer and matching its promise to the destination. That describes Google's platform. For your FroggyAds test, open the final URL. Confirm that visitors can complete the action named in your campaign brief. See the Google Ads create-ads guidance.
Confirm ownership before campaign setup
Assign an accountable owner to the offer, budget, creative, destination and accepted event before campaign setup begins.
The offer owner confirms what is being advertised and where it is eligible. The budget owner confirms the amount authorized for a test. The creative owner supplies the approved message and destination version. The analyst or system owner confirms what action will count and where acceptance is recorded. One person may fill several roles, but the brief should name each responsibility.
For an affiliate offer, ask the merchant or affiliate manager to confirm allowed markets, approved claims and which submitted leads or sales qualify. For ecommerce, ask the product owner to confirm availability, shipping limits and how cancellations or refunds affect an accepted order. For SaaS, agree whether signup or a later activation event is the business result. Do not leave those decisions to the campaign operator.
An agency should obtain written client approval for the offer, message, destination and test amount before configuring traffic. An independent media buyer should retain the offer terms and budget authority beside the campaign brief. These are business-control steps, not FroggyAds account features. They prevent later disagreements about whether a campaign followed the approved plan.
Google Ads also starts its own campaign creation guide with an advertising objective and campaign type. That is Google's account workflow, not a FroggyAds feature. Use the Google Ads campaign creation guide only for its platform-specific instructions; define FroggyAds inputs from the current options in your account.
Check FroggyAds campaign options before configuration
Create your free FroggyAds account when the test question and its constraints are ready. In the account, check which campaign formats, targeting options and buying terms are currently available for your campaign. Platform workflows differ: TikTok Ads Manager documents its own campaign, ad-group and ad levels, objective choices and budget setup. Those are TikTok-specific controls, not FroggyAds instructions. Use the options shown in your FroggyAds account and keep your approved brief beside them. See TikTok’s campaign setup guide for that platform’s structure.
Create your free FroggyAds accountChoose a format your asset and destination can support
Choose a format from the options currently available to you, then ask what the visitor must understand before clicking and what the destination must do next. FroggyAds offers Push, Native, Display, Pop, Interstitial and Video campaign formats; the asset requirements and availability depend on the selected option and current account inventory. A text-led message needs a clear headline and action; an image-led unit needs one legible offer; a video test needs a usable video asset. Do not choose a format because you assume it wins.
Before launch, read the creative and landing page as one promise. Confirm that the offer, condition, currency or eligibility statement in the ad also appears clearly on the final page. Follow redirects and test the call to action. Make sure the destination offers a clear next step without making visitors search for it. Google documents these requirements for Google Ads, not FroggyAds; its Google Ads destination and format policies explain why a functional, relevant destination matters.
Match the format to the asset you can actually deliver and the action the page can complete. Keep the first comparison interpretable. Hold the offer, eligibility and destination steady while testing another available format. Wait for the same accepted event to mature before deciding what to test next. The purpose is to learn which presentation deserves another test, not to assume that a format alone will improve acquisition.
Use the exact asset and destination version approved for the test. Keep a source file, submitted file, final URL and approval date together in your own record. If the offer, price condition, call to action or destination changes, treat it as a new creative-to-page combination and review it before replacing the live version. Google’s ad and landing-page guidance is specific to Google Ads; its relevance check is a useful comparison, not a claim about FroggyAds policy.
Assign a measurement owner before campaign creation
Choose one person responsible for confirming the post-click event. Record the event name in plain language, the system that reports it, the person who accepts it and the expected delay. An affiliate lead can be submitted before a merchant approves it. An ecommerce order can be placed before it clears a return or cancellation rule. A SaaS account can be created before activation. The reporting plan should name the stage used for the buying decision.
Ask the measurement owner to test the path from the campaign destination through the action. Confirm that campaign identifiers remain available in the reporting system when your setup uses them. Check that the expected event appears once, and document how the owner will flag duplicates or late confirmations. Do not assume a pixel, postback or server-side event is active until the responsible person has checked it.
If an agency manages the campaign while a client controls the CRM or order system, agree how event data will be shared before launch. Specify the reporting period, time zone and which status means accepted. If the client cannot return person-level data, agree on a suitable aggregate confirmation. Avoid moving spend on numbers that different teams define differently.
Keep the measurement owner available for the first review. If delivery starts but the event is missing, pause the result judgment and inspect the tracking path. If a downstream event takes several days to mature, keep it pending until that period passes. This gives the buyer a clear escalation path without mislabeling delayed data as a campaign outcome.
Write the test decision before configuring settings
Write the brief around the campaign decision. Record its offer, audience, available format and final URL. Name the accepted event, confirmation rule, approved cap, pause condition, owner and review date. Mark each value as confirmed, assumed or open. For a SaaS offer, for example, a signup is not automatically the accepted outcome if the business needs an activated trial. Name the event that qualifies and who can confirm it before delivery.
Create your free FroggyAds accountDocument eligibility and settings for the buyer
The offer owner should supply the eligible GEOs and any audience restrictions before the buyer configures campaign targeting. Record why the offer cannot serve an excluded location, device or language. The buyer can then compare the brief with the targeting controls currently available for the chosen FroggyAds campaign. Do not rely on a list copied from another campaign without checking the present offer.
When device, operating system, browser, language, carrier, connection, schedule or source settings matter, name the owner who requested each one and the reason. For example, a market restriction may come from shipping coverage or offer terms. A device restriction may come from a landing page that cannot complete checkout on that device. Use only the controls shown as available to this campaign.
Ask the destination owner to test the page in the same broad conditions the offer owner approved. A campaign can be configured with the intended market and still create a poor experience if the page is unavailable or the language is wrong. Record the tested URL and date, then send any material difference back to the offer owner before launch.
If an agency or client has a required exclusion, put it in the approved brief rather than relying on a verbal note. The media buyer should compare each required restriction with the account setup and record any option that cannot be represented directly. Resolve that gap with the client before committing spend; do not silently assume a setting exists.
Track creative, destination and offer versions together
Store the approved offer, creative and landing-page version under one campaign reference. Record the visible promise, any material condition and the next step a visitor will take. This gives the operator a clear comparison when reviewing the creative in the format preview or checking the destination. It also makes approval specific to a version rather than to a vague campaign idea.
For affiliate media buying, attach the accepted merchant terms or approval note to the offer record. For an agency, attach the client’s signoff for the exact ad and destination. For an ecommerce store, note which product page and availability state the creative refers to. For SaaS, identify the signup or activation path that the approved message describes.
If the client changes a price, offer condition, asset or landing page after approval, mark the old version as superseded. Have the appropriate owner review the replacement before the buyer updates the campaign. Never assume an approved banner remains accurate after the destination changes. Keeping versions together helps prevent stale messages from continuing to describe a newer offer.
We recommend that you keep the creative version and final destination visible in your internal campaign record. FroggyAds lets you manage the available campaign format and delivery settings; your team owns the exact offer content and destination. Use that division of responsibility to keep the ad, landing page and business approval consistent.
Set a spending boundary for the campaign test
Set the campaign cap from the amount your business is willing to put at risk before the accepted outcome is confirmed. Keep three values distinct: the authorized total cap, the bid used for buying, and any minimum shown in the account. A minimum is an entry condition, not a recommended test budget. Check the current FroggyAds buying terms before selecting settings; we will not turn a platform minimum into a promise about acquisition cost.
Accepted CPA equals spend for the test period divided by outcomes that pass the agreed acceptance rule. Set its ceiling from your business economics, not from click volume. An affiliate buyer should apply the merchant’s qualification rules to the approved payout. An ecommerce advertiser should decide how refunds, cancellations and fulfilment costs affect an accepted order. A SaaS buyer should distinguish a registration from a paid or activated account when that is the business result. Record the calculation period and assumptions so the buyer knows which events can be compared.
Use this planning boundary: approved campaign cap divided by the maximum cost per accepted outcome. A hypothetical USD 180 cap at a USD 30 accepted-CPA ceiling leaves room for six outcomes at that limit; it predicts neither delivery nor sales. If you split the cap among several formats or markets, each comparison receives less room. Start with one clean test unless the approved budget can support distinct, interpretable comparisons.
Amazon Ads’ budget guide frames budget choice around business priorities rather than a universal formula. That guidance describes Amazon’s platform, not FroggyAds buying terms. See the Amazon Ads advertising budget guide. Before setup, record who authorized the cap and who may approve a change.
Preflight the build against the campaign question
Before activation, compare the setup with your test brief. Confirm that the format accepts your asset and the audience meets offer eligibility. Check that the destination carries the ad's promise. Verify that the accepted event appears once in the agreed reporting system. Confirm that the cap and buying terms match the authorized amount. Fix each mismatch or return it to its decision owner before launch. If one check fails, correct it or return the decision to its owner. A verified preflight helps you use FroggyAds’ self-serve campaign controls with a clear next step.
Create your free FroggyAds accountKeep campaign approval states visible to every owner
Give every campaign brief a visible approval state that the client, offer owner, analyst and buyer can understand. A practical internal sequence is requested, approved, configured, checked, live, reconciled and superseded. These are team record labels, not FroggyAds dashboard statuses. Keep the current state beside the campaign reference so nobody mistakes a draft for permission to spend.
For each state change, name who moved the brief, when it happened and what evidence they checked. “Approved” should identify the offer terms, eligible markets, creative version, destination, accepted event and authorized cap. “Checked” should mean the configured values and a test visit match that approved brief. If one input remains open, leave the state at requested or configured and keep launch authorization pending.
Return the brief to review when a change affects the offer promise, audience eligibility, asset or destination version, acceptance event or spend cap. The owner responsible for that decision must approve the new version before the buyer changes live settings. Mark the earlier version superseded, retain it for comparison, and make the effective date clear.
Name each version with a stable offer reference, market, format and creative number. Keep client identifiers and payout terms out of public labels. When a buyer takes over an active campaign, record its current state and last approved version. State who may change it and which evidence still needs reconciliation.
Move the brief through six launch gates
Use these gates in order. Each one converts an informal instruction into a decision another buyer can verify. Keep the gate outcome in the internal brief; the page does not imply that FroggyAds provides an approval workflow.
- Test question: write one sentence naming the offer, eligible audience, chosen format and accepted action. State what the first result will help you decide; leave secondary comparisons for a separate test.
- Eligibility: the offer owner confirms active terms, permitted markets and conditions the creative may state. Save the source or written approval.
- Versions: the creative owner and landing-page owner approve the exact asset number and final destination together. Mark replaced assets superseded.
- Measurement: the analyst identifies the accepted event, system of record, maturity window and duplicate rule, then confirms a test action appears as expected.
- Spend authority: the budget owner records the total cap, allowed cost boundary, pause condition and the person who may approve a change.
- Launch check: the buyer compares available FroggyAds settings with the approved brief; a second reviewer follows the destination and confirms the configured version before delivery.
If any required gate is unresolved, leave the brief in its current state and keep launch approval pending. The buyer can prepare settings or resolve a technical check, but should not infer an offer condition, client approval, spend authority or accepted event.
After the launch check, save the campaign reference, active version, gate owners and test result together. The client, affiliate manager or next media buyer should be able to see what is live, who authorized it and which decision comes next without rebuilding the history from chat or email.
Hand off the created campaign with a launch record
After campaign creation, send the reference and final settings summary to the offer, budget and measurement owners. Confirm that the destination and creative version match the approved packet. Do not send confidential account credentials in an email or shared campaign note. Use the approved account-access process for any user who needs to manage setup.
At the first delivery check, compare the active configuration with the signed brief. Confirm the chosen market, format, destination, cap and event are still correct. If the test visit reaches the wrong page or the event does not appear, document the issue and alert the relevant owner before evaluating business results. Keep delivery status separate from accepted conversions.
When an offer or destination changes after launch, create an updated version record and obtain the necessary approval. Record what changed, who requested it and when the buyer applied it. If the change alters the test question, treat the new configuration as a separate version in your notes. This protects the meaning of earlier observations.
Use FroggyAds campaign and source information to review delivery, then use the agreed business system to confirm accepted outcomes. Do not claim a campaign succeeded because it generated clicks, or failed because later conversions have not matured. The assigned owners should reconcile the same period and acceptance rule before they approve a next action.
Online campaign creation: handoff questions
Who should approve an online ad campaign before setup?
The offer owner confirms the terms and eligible audience. The budget owner approves the cap. The creative owner approves the asset and destination. The measurement owner defines the accepted event. One person can handle several roles. Record every responsibility before the buyer configures delivery.
Which FroggyAds format should I choose for a first campaign?
Choose from the formats currently available in your FroggyAds account based on the asset you can produce and the action your destination supports. Keep the offer, eligible audience and destination steady while you learn how one presentation performs against the accepted event. Do not assume one format will outperform another; use the first test to decide whether that format merits another controlled comparison.
How can I check whether the destination matches my ad?
Open the final URL, follow any redirects and confirm that the page repeats the ad’s offer condition and call to action. Check that a visitor can complete the stated action on the device or market you plan to include. Google’s landing-page recommendations apply to Google Ads; the practical campaign check is to make sure your own destination delivers what the creative promised.
When should I compare two campaign formats?
Compare formats only when the offer, eligible market, destination, accepted event and review window can stay consistent. Change the format as the test question, not several campaign inputs at once. Wait until the agreed event has matured before interpreting the comparison, then use that evidence to choose the next test.
How do I set a stop rule for a new online campaign?
Set the limit before launch from the amount approved and your maximum acceptable cost per accepted outcome. Keep the bid, account minimum and total cap distinct. Pause if the cap is reached before the event is confirmed, if the destination is wrong, or if measurement has failed; do not raise exposure just because clicks arrived.
What must be reapproved when an offer or landing page changes?
Pause the affected campaign version if a change alters the offer, eligibility, stated condition or destination. Mark the prior version superseded, ask the responsible offer and creative owners to approve the new asset and page together, and record the effective time before the buyer updates settings.
Who may authorize a change to a live campaign?
Only the person named by the budget owner may change the authorized cap. Changes to offer terms, eligible markets, creative or destination require the relevant offer or creative owner to approve the new version. Record the requester, approver, time and reason before changing the live setup.
How should an agency handle a client request to raise spend mid-test?
Do not treat a client message as budget authority unless the client has designated that person to approve spend. Ask the authorized budget owner to approve the new total cap and pause rule in the brief, then record the effective time. Review added spend as a separate test period so the prior result remains interpretable.
What should I do when campaign settings do not match the brief?
Do not activate the mismatched version. Record the exact field and intended value, then ask the owner of that decision to approve a correction. If FroggyAds does not present a required option, do not substitute a broader setting without approval; revise the test question or resolve the limitation first.
How do I diagnose clicks without accepted outcomes?
First confirm that the accepted event is defined and reported once. Wait for the agreed maturity window. Open the final URL and follow the promised action. Check that the offer is eligible for the selected audience. Then compare delivery with your cap and the available source information. If tracking or the destination fails, fix that before judging traffic quality. Clicks alone do not prove a sale or a campaign failure.
Continue campaign planning with FroggyAds
Create your next FroggyAds campaign with an approved brief
A reliable first test has a written objective, a verified event, a spending boundary and a scheduled review. Keep settings simple enough to learn from the result, then decide whether to continue, adjust one input or pause.
Assign each campaign decision to an owner
Use this matrix to prepare a campaign before you open the setup controls. It is an internal handoff guide, not a required FroggyAds dashboard form. Keep the evidence and approver with the offer brief.
| Owner | Decision or material | Evidence to confirm |
|---|---|---|
| Offer owner | Offer terms, eligible markets and approved claims. | Current offer record or written approval. |
| Creative owner | Submitted asset version and matching destination. | Approved file label, URL and page check. |
| Measurement owner | Accepted event, reporting system and maturity window. | One test action appears once in the agreed system. |
| Budget owner | Exposure limit, accepted-cost ceiling, event-maturity period and pause trigger. | Written authority states amount and dates; the bid and account minimum are recorded separately. |
| Media buyer | Available format, targeting settings and campaign name. | Configured values match the approved brief. |
For an affiliate offer, the offer owner can be the merchant contact or affiliate manager; the media buyer remains responsible for using the approved campaign inputs. For an agency, the client should confirm the offer, asset and spend authority before the agency operator creates the campaign. This distinction reduces confusion about who can approve a change.
For an ecommerce advertiser, the product or operations owner can confirm availability and the order status that counts. For a SaaS team, the analyst can confirm the activation event and its delay. Keep the event name, system owner and time zone in the same packet. If another party confirms sales, agree how that confirmation is returned before buying traffic.
Hypothetical example: the budget owner approves USD 180. The business accepts up to USD 30 per qualified event. The simple ratio is six events at that boundary. This planning arithmetic predicts neither delivery nor sales. Use approved business figures; it is not a FroggyAds price or result.
If Push is already the chosen format, our How To Create A Push Ad Campaign guide covers its narrower asset and launch requirements. When your approved handoff packet is ready, create your free FroggyAds account and use the approved inputs to configure the available campaign settings.
How do I create an ad campaign online?
Align the offer owner, budget approver, creative owner and measurement owner. Record approved terms, destination, eligible audience, accepted event, asset version and test cap. Then configure the options available in your FroggyAds account, verify the route and event, and have a second reviewer check the setup before launch. Create a free account when the brief is ready.