0.2 How to Use This Wiki¶
What this page teaches: This page explains reading order, notation, examples, and where to find definitions.
Why this matters in real accounts: This topic affects money, visibility, campaign control, reporting clarity, or team execution. Understanding the business reason first makes the console steps much easier to learn.
Practical workflow: - Read the definition and linked glossary terms. - Identify what decision this topic affects. - Find the report, console screen, or input data required. - Make a small reversible change first when working in a live account. - Write down what changed and why.
Worked mini-example: Open the relevant report, check the key metric, make one small change, and note what you did and why.
Common beginner mistakes: - Skipping the context and copying tactics blindly. - Changing a live account without checking eligibility, budget, or data window. - Forgetting to log the reason behind the change.
Definition of done: - The learner can explain the topic without jargon. - The learner can name the report, console area, or data input used for this topic. - The learner can describe one safe action, one risky action, and one escalation trigger.
Merged from Complete Data-Filled Guide¶
Merged beginner guide content¶
This wiki teaches Amazon PPC from the ground up. Start with [[1. Foundations & Fundamentals]], then move through [[2. Account & Campaign Architecture]], [[3. Campaign Types]], and [[4. Targeting & Match Types]]. If you want a quick win, go to [[9. Negative Keywords & Negation Strategy]] — cutting wasted spend is often the fastest improvement you can make.
Role-based start paths¶
| Role | Best first path | Goal |
|---|---|---|
| Fresh graduate | Sections 1 to 4, then Glossary | Understand the language and ad system |
| VA | Sections 1 to 9, then Team Ops | Execute daily PPC tasks safely |
| Junior strategist | Sections 1 to 11, then lifecycle strategy | Optimize campaigns and explain performance |
| Brand owner | Foundations, metrics, reporting, launch strategy | Understand what your PPC team is doing |
| Agency owner | Team Ops, communication, reporting, tooling | Build repeatable service delivery |
Wiki conventions¶
- Bold terms should exist in [[28. Glossary & Acronyms]].
MONOSPACED TERMSrefer to console buttons, menu names, fields, reports, or file columns.- ACOS, TACOS, ROAS, CTR, CVR, CPC, SP, SB, SD, DSP, AMC, and SQP should always be capitalized.
- Every operational page should include a beginner explanation, workflow, worked example, common mistake, and definition of done.
Maintenance rules¶
Use this review path for content changes: Draft -> Peer Review -> Senior Strategist Review -> Publish. If Amazon changes a feature that affects live operations, mark the page as [Stale?] or [Deprecated], add the replacement page link, and update last_verified_against_live_console.
Operator checklist¶
- Explain the topic in plain English.
- Identify the report, console area, or input data needed.
- Make the smallest safe change first.
- Log the action, reason, and expected review date.
- Escalate if the issue touches policy, inventory, account health, or large budget changes.