Treat preparation as a separate phase
Week zero is the work done before launching a paid campaign. It is not a guarantee of approval, traffic, revenue, or a smooth account setup. Its purpose is narrower: to help a beginner understand the rules, organize decisions, and notice avoidable gaps before spending begins.
Think of an advertising account as a product and a working tool, not as a shortcut around platform requirements. Its use must fit the platform’s terms, verification processes, and advertising policies. If an account was purchased or transferred, check what was agreed with the seller, confirm that the transfer is permitted, and use only accurate identity and business information. Do not try to bypass a restriction, conceal links between accounts, or substitute borrowed or false details for required information.
Preparation does not need to become an elaborate project. The aim is to make a small set of useful materials: policy notes, a vocabulary list, a tracking method, a written budget plan, stop rules, and a campaign diary. These can be simple documents or notes, provided they are clear enough to use when decisions become less obvious.
Some tasks may already be complete. If you have recently reviewed the applicable policies, established a reliable tracker, or written usable stop rules, you can check that work rather than repeat it. The value lies in having current, relevant preparation—not in filling every task with activity.
Read the rules that apply to the account and campaign
Start with the official policy and help pages for the platform where you intend to advertise. Read the rules relevant to the account, the type of advertising, the destination page, and the product or service being promoted. Requirements can differ by platform and subject, so do not assume that approval or permission in one place means the same thing elsewhere.
Make notes in your own words. Separate what is clearly allowed, what is prohibited, and what is unclear or conditional. Pay attention to requirements concerning truthful claims, restricted products or services, landing-page content, account information, payment, and review or verification. If a policy refers you to another policy, follow that reference rather than relying on a short summary.
Avoid treating a seller’s description, a forum post, or an old checklist as a substitute for current platform guidance. When you cannot tell whether a planned ad or destination is permitted, pause and consult the platform’s official support or appeal channels as appropriate. Do not launch first and hope that an unclear issue will resolve itself.
Keep a record of the pages you consulted and the points that affect your plan. Platform policies and procedures may change; current requirements and values are published on the platform’s own help and policy pages. Revisit those pages when a relevant decision changes or when the platform indicates that its guidance has been updated.
Build a vocabulary that supports sound decisions
A beginner can lose time by using familiar words as if they all meant the same thing. Create a short glossary for terms that appear in the platform interface and in your own campaign notes. Use the platform’s definitions where available, and distinguish between a platform-defined term and your own shorthand.
Useful concepts to clarify include the advertising account, campaign, ad group or equivalent structure, creative, audience, placement, destination page, impression, click, conversion, attribution, review, rejection, and billing. Not every platform uses identical names or structures. Record the wording used by the platform you plan to work with instead of assuming that a term transfers exactly from another system.
Also define the business meaning of the action you hope someone will take. A click is not necessarily a meaningful outcome, and a platform’s reported conversion may depend on how tracking is configured. Write down what you count as a completed action and what evidence you will use to assess it. If the event is not yet measurable, mark that as an unresolved setup task rather than treating it as established.
Keep the glossary practical. A compact list that prevents confusion is more useful than collecting terminology without connecting it to a decision. When a term remains uncertain, note the question and seek clarification from the platform’s documentation before building a plan around it.
Choose a tracker before the first campaign
Decide how you will record campaign activity before launch. The tracker can be a spreadsheet, a document, or another method that you can maintain consistently. The important thing is that it captures enough context to understand what changed and when, without encouraging you to draw conclusions from incomplete information.
Plan fields for the campaign or test name, the intended audience or targeting approach, the creative or message, the destination, the goal, the status, and the observations you want to review. Add fields for spend and the platform-reported results if those are relevant to your setup. Record where each value comes from: platform reporting, your own analytics, or a manual observation. Different systems can define or attribute activity differently, so avoid treating unlike measurements as interchangeable.
Use clear labels and keep a note of meaningful edits. If several elements change together, it may be difficult to understand what influenced a later result. Where practical, make the purpose of each test explicit and avoid changing unrelated parts without recording them. This is not a promise that results will be conclusive; it is a way to make your own process more interpretable.
If tracking depends on a platform feature or an external measurement setup, verify that it is permitted and configured appropriately. Do not collect information you do not need, and follow applicable privacy requirements. If you have already selected and tested a tracker, check that it still fits the campaign and that you know how to read its outputs. You do not need to adopt a new tool simply to complete week zero.
Draft the budget split in words
Before entering any payment information or setting a campaign live, write down how you intend to divide the available budget. Use words rather than starting with a detailed numerical allocation. For example, describe the portions as a limited amount for initial checks, a portion reserved for a controlled test, and a portion left uncommitted until you have reviewed what the test shows. Adapt the categories to your situation; the point is to explain the purpose of each part.
State what each portion is meant to learn. A test might examine whether a message is understandable, whether a destination works as intended, or whether an audience definition is relevant. Avoid assigning money to a test unless you can say what decision its observations could inform. A test without a decision purpose can become spending without a learning plan.
Write down the conditions that must be met before any budget is released. These may include policy review, working access, a functioning destination, a clear campaign objective, and a tracking method you understand. If any prerequisite is missing, record that the campaign is not ready rather than treating the budget as a reason to proceed.
Your budget plan is a control, not a forecast. It cannot make an untested offer profitable or ensure that a platform will deliver a particular outcome. Keep enough flexibility to stop, reassess, or leave part of the budget unspent. If the platform sets current billing terms, thresholds, or other values, consult its own help pages; do not rely on an old note or an assumption.
Write stop rules before pressure enters the process
Stop rules are decisions made in advance about when to pause rather than continue automatically. Write them in plain language. Useful triggers can include a policy concern, a rejected ad that you do not understand, an unexpected charge, broken access, a malfunctioning destination, missing tracking, or spending that reaches the boundary you set for the test.
Include a rule for uncertainty: if you cannot explain why a material change is needed, pause and investigate before making it. Include a rule for account notices: read the notice, identify the issue, and use the platform’s official support or appeal route when appropriate. Do not respond to a review, restriction, or verification request by creating a workaround or disguising who controls the account.
Make each rule actionable. “Pause if tracking is unreliable” is more useful when paired with a next step, such as checking the setup and confirming what data is available. “Stop if the test has answered its question” can prevent a planned test from continuing without a reason. The exact triggers depend on the campaign and the platform; do not copy limits from someone else’s situation as if they were universal.
Review the rules before launch and keep them accessible while the campaign is active. If you revise one, note why. A rule should support deliberate decisions, not become an excuse to ignore platform requirements or keep spending after the original plan no longer makes sense.
Set up a campaign diary
A diary records context that raw dashboard figures may not show. Start with the reason for the campaign, the intended audience, the message, the destination, the measurement approach, the budget logic, and the conditions under which you will pause. Add a brief entry when you launch, make a meaningful edit, receive a platform notice, or stop.
Keep observations separate from interpretations. “The destination did not load during a check” is an observation; “the audience dislikes the offer” is an interpretation that may not be supported. Mark questions as questions and avoid presenting early signals as settled conclusions. This habit makes it easier to revisit a decision without confusing what happened with what you thought it meant at the time.
Record relevant account and access issues without putting sensitive credentials into the diary. For a transferred account, document the agreed handover and the steps you have taken to secure access in ways allowed by the platform. Never store passwords, verification codes, or unnecessary personal information in an ordinary campaign log. Follow the platform’s process for account security and required verification.
If you already maintain a useful campaign record, you can skip creating a second diary. Check whether the existing one captures decisions, changes, observations, and reasons for stopping. A diary is useful only if it stays accurate and manageable.
Check readiness, then proceed cautiously
Before moving from preparation to launch, review the materials together. Can you explain the applicable policies? Do you understand the terms used in the platform’s reporting? Is the tracker ready, and do you know where its measurements come from? Does the budget split have a learning purpose? Are stop rules clear, and is the diary ready to capture decisions?
Resolve gaps that could lead to an avoidable mistake. If an account, payment method, identity check, or campaign element is not ready, use the platform’s legitimate setup and support processes. If a requirement is unclear, wait for clarification rather than improvising around it. Keep account ownership and information accurate, and use the account only in ways the platform permits.
Week zero is complete when you have enough clarity to make a careful next decision—not when every possible task has been done. A beginner who has already completed a task responsibly may simply verify it and move on. Preparation reduces preventable confusion; it does not remove uncertainty, guarantee approval, or promise a financial result.