Part II · Chapter 5

How an Ad Campaign Is Structured

Status: reviewed · Prerequisites: What AdTech Is and Why It Exists, AdTech Ecosystem Participants, Core Advertising Metrics, AdTech Economics and Business Models

How an Ad Campaign Is Structured

The Core Idea

An ad campaign1 is not a single banner or a line in a report. It is a control-plane configuration that translates the business intent of an advertiser2 into delivery rules: what the system must optimize for, which ad opportunities are allowed, where the ad may appear, how much and when it may spend, which content to show, where to bring the user, and which signals to use for measurement.

Most platforms have a similar object tree:

advertiser account
└── campaign
    └── ad group / ad set
        └── ad
            ├── creative
            └── destination

But this is not a single industry-wide schema. Vendors and campaign types place budget3, targeting4, optimization and schedule5 differently. A portable mental model is built not around the names of screens but around two questions: which object owns the setting and which child objects receive its effect.

Why a campaign needs a hierarchy: the account as the root of control

A single advertiser runs different products, countries, billing scopes, and teams at the same time. A flat list of ads6 would make it impossible to safely define who has access, which currency counts spend7, which time zone governs the schedule, and which data sources are available to objects. That is why a platform starts with an advertiser account8, or ad account — a tenant within which campaigns and their related settings exist.

An account usually forms several boundaries at once:

  • Ownership and access. It defines the owner of resources and the roles and permissions of operators.
  • Billing identity. A payer9, billing profile, or another contractual entity is associated with it. The exact set of fields depends on the product.
  • Currency and time zone. These values affect reporting, budget periods, and the schedule; in some products they are hard or impossible to change after creation.
  • Namespace. Campaign and ad resource IDs are unique at least within the platform/account context. Event identifiers (click ID, event ID) belong to other namespaces and do not follow this rule — see chapters 21–23.
  • Shared configuration. Data sources, conversion actions10, brand assets, URL settings, and defaults may be shared across several campaigns.

The advertiser’s legal entity and the ad account are not the same thing. One company may have separate accounts for regions, brands, currencies, or different payers. Conversely, one account may serve several initiatives of a single legal entity.

A manager account11 is an administrative layer that gives an agency12 or an internal team centralized access to several ad accounts. Access to an individual account can also be granted without it; in either case it is administrative access, not a delivery layer inside the campaign.

Subscription App Ltd.
├── internal growth team
├── agency manager access ─────────────┐
│                                     │
├── ad account EU (EUR, Europe/Berlin)│
│   ├── campaign: Spring subscriptions│
│   └── campaign: Returning users     │
└── ad account US (USD, America/NY) ◀─┘
    └── campaign: Summer acquisition
Object What it represents What you cannot conclude from it
Legal advertiser A company or other legal party That it has exactly one ad account
Ad account Product, access, and billing boundary That only one team or agency can manage it
Manager account Delegated access to several accounts That it participates in the delivery hierarchy of every campaign

Account-level settings are often inherited downward until a more specific object sets an override. But inheritance is a product-specific contract: the same field name does not guarantee the same precedence order. When reading a configuration, you need to record not only the value but also its source: account default, campaign value, or ad-level override.

For the running example, take an EU account of a subscription app. The agency has been granted access, but the owner and billing identity remain with the advertiser. The account uses EUR and the Europe/Berlin time zone; this zone will be the baseline for the campaign schedule. The business goal is to acquire new paid subscriptions, but the campaign itself still has to turn that goal into executable settings.

The execution tree: campaign, ad group/ad set, ad, and creative

A campaign is the top-level delivery container for a single business intent or a coherent flight — a delivery period with a start and an end date. It consolidates settings that must apply across several child groups and ads: the objective13, shared limits, the channel/type, and other product-specific controls. A campaign is not just a folder for reporting: pausing it, rescheduling it, or constraining it can stop or change the delivery of all its descendants.

An ad group14 or ad set is an intermediate scope boundary for a group of ads. Both entities answer the question “which ads share execution rules?”, but neither has a universally identical schema:

  • in the Google-like model, an ad group usually bundles closely related ads and triggering criteria, such as related keywords;
  • in the Meta-like model, an ad set usually holds the audience, placements15, optimization, bid16, budget, and schedule.

So statements like “targeting always lives in the ad group” or “budget is always set at the campaign” are wrong without naming the platform and campaign type.

In a DSP17 and an ad server18, the same levels are often called insertion order and line item (chapters 11 and 16): the functions match, the names do not.

An ad is the executable delivery unit. It binds the parent group, advertiser identity, creative19, destination20, tracking, and status. The creative carries the message and the assets — text, image, video, audio, CTA (call to action), and metadata. A creative may be an inline part of the ad or a separate reusable object. Even if the UI shows them as one card, logically these are different responsibilities:

creative: what the user will see
ad:       where and under which parent rules this creative runs,
          where it leads, and what state it is in
Level Portable function Google-like example Meta-like example
Campaign Shared intent and delivery scope Campaign settings, channel/type, and budget link Objective and, when that model is selected, a campaign-level budget
Middle layer A group of ads with shared execution rules Ad group: related ads and keywords/criteria Ad set: audience, placements, optimization, bid, budget/schedule
Ad Delivery unit Ad inside an ad group Ad with a parent adset_id and creative reference
Creative Content and assets Assets/ad content A separate creative_id can be reused

Below is an illustrative tree, not the payload of a real API:

{
  "account_id": "acct_eu_1",
  "campaign": {
    "id": "cmp_subscriptions_42",
    "objective": "APP_PROMOTION",
    "groups": [
      {
        "id": "grp_us_1",
        "label": "US",
        "ads": [
          { "id": "ad_7", "creative_id": "cr_video_a", "status": "active" },
          { "id": "ad_8", "creative_id": "cr_video_b", "status": "active" }
        ]
      },
      {
        "id": "grp_de_1",
        "label": "DE",
        "ads": [
          { "id": "ad_9", "creative_id": "cr_video_a", "status": "active" }
        ]
      }
    ]
  }
}

The labels US and DE here are arbitrary names of execution scopes within one account: a label by itself does not set targeting and does not mean the region has to match the account boundary. The rules for building audiences belong to the next chapter. cr_video_a is used by two ads: the content is shared, but the ads have different parents, IDs, statuses, and may lead to different destinations.

The hierarchy also explains effective behavior. If ad_7 is set to active but the parent campaign is paused, impressions will not start. If the campaign defines a shared URL setting, the ad may inherit it or override it where the product allows. Reading the tree top-down shows the shared constraints; reading it bottom-up shows the full set of settings actually in effect for a specific ad.

From business intent to delivery selection rules

The tree tells you where settings live. The causal chain explains why they are needed:

business objective
  → optimization event / performance goal
  → eligible audience and placements
  → bid strategy
  → budget + schedule
  → delivery
  → tracking signals and the transition to the destination

For the subscription app, this chain may look like this:

growth in paid subscriptions                    # business outcome
  → App promotion or Sales                       # campaign objective
  → install, then paid subscription              # optimization event
  → geo/device/audience rules and exclusions     # targeting
  → feed, video, or in-app inventory             # placements
  → maximize conversions with a target/control   # bid strategy

The names App promotion and Sales and the available combinations are product-specific and change over time. What matters is not the label but the transition from the desired business outcome to an observable signal and to delivery rules.

Objective and optimization event

The campaign objective is the high-level business intent or setup guidance: awareness, traffic, leads, app promotion, sales. Based on it, the platform may suggest campaign types, features, and defaults. The objective does not have to be the event that the optimizer directly predicts.

The optimization event21, or performance goal, is the observable result, probability, or value that the delivery system tries to increase. It may be an impression22, a click23, a landing-page view, an install, a purchase, or conversion24 value. A specific conversion action defines which tracking event counts as the selected input for bidding and/or reporting; some products group several actions into a conversion goal and distinguish primary and secondary events.

A deep event such as a paid subscription is closer to business value but not automatically better for optimization. It may be rare, delayed, or unreliably transmitted from the event source. An install occurs earlier and more often but is only a proxy for the subscription. The choice requires sufficient signal volume and correct measurement25; the algorithmic trade-off is discussed in chapter 7.

Configuration layer Question Subscription-app example
Business outcome What should the business get? More new paid subscriptions
Campaign objective What overall intent is communicated to the platform? App promotion or Sales, depending on the product
Optimization event Which signal drives delivery decisions? install first, paid_subscription later
Tracked events Which events are observed at all? Install, trial, purchase, renewal
Bid strategy26 How does the policy translate the goal and constraints into bids? Maximize conversions with a given control
Billing/pricing basis27 Which qualifying event triggers a charge? For example CPM28 or CPC29; the basis is known from the contract and need not match the optimization

The billing basis, as shown in the previous chapter, is set separately. So the label subscription campaign proves nothing about the billable event30.

Targeting and placement

Targeting defines the eligibility rules and inputs of the delivery model: which opportunities31, users, or contexts are allowed or preferred. At an overview level these may be geo, device, context, audience/keyword criteria, and exclusions. The sources of audience data, identity, and privacy are discussed in chapter 6.

Placement answers a different question: in which media environment and slot the ad may appear. Examples are feed, stories, search results, video pre-roll, an in-app banner, or a rewarded slot. The term is overloaded: on the publisher32 side a placement is a specific slot (chapters 1 and 10); on the buy side, in Google-like products it means the selected sites/apps (chapter 6), and in Meta-like products positions such as feed/stories; here it means the buy-side configuration field. Placement is tied to creative format eligibility, but the formats, assets, and compatibility themselves are covered in detail in chapter 8.

Axis Main question Example constraint
Targeting For which opportunities/users/contexts is delivery possible? Geo DE, mobile devices, keyword category, audience exclusion33
Placement Where exactly is delivery possible? Feed, search results, in-app rewarded slot

An API may store placements inside an object named targeting; that is the nesting of a specific product, not proof that audience and placement are one concept. An opportunity must pass the constraints of both axes.

Bid strategy

A bid strategy is the policy that translates the optimization goal and constraints into auction34 bids. The strategy may seek to maximize conversions, value, or another result, and it may take a target or a cap into account. Here it is important to separate four entities:

bid strategy  = the decision-making rule
strategy target/cap = a parameter or constraint of the policy
actual bid    = the decision for a specific auction opportunity
price/charge  = the outcome of the auction and the billing contract

A numeric target CPA35 is not an actual bid, and an actual bid does not by itself determine the billable amount. How bids are computed, how budget is distributed, and how pacing36 works is covered in chapter 7.

These three distinctions — objective ≠ optimization event, placement ≠ audience, strategy ≠ bid amount — let you read a campaign configuration without assuming that one UI label simultaneously describes the business goal, the delivery signal, and the money.

Resources and time: budget and schedule

Even a correctly chosen decision policy acts only within resource and time constraints. The budget caps the available spend on a given scope and time basis. It guarantees neither inventory37, nor conversions, nor an even rate of spend, nor an exact invoice amount.

Two temporal semantics are common:

  • A daily budget sets a daily basis. The specific product determines whether the value is a hard calendar cap, an average daily target, or another form of constraint.
  • A lifetime, campaign-total, or flight budget caps the spend over the whole interval.

Scope also varies. A budget may belong to a campaign, be shared between campaigns, or be set on an individual group (ad group/ad set). With campaign-level allocation the system distributes the shared resource among children; with group-level budgets each group has its own limit.

Setting Possible scope Unit/basis What it limits What it does not guarantee
Daily budget Campaign or group Currency per day Available spend on a daily basis The same spend every hour or day across all products
Lifetime budget Campaign or group Currency per flight Cumulative spend until the end condition Even distribution across days
Shared budget Several campaigns Currency on a shared pool The shared resource of the group A fixed share for each child
Bid target/cap Strategy scope Currency per predicted/result unit The decision policy or a bid constraint Total spend and the number of results

In the running example the campaign gets an illustrative lifetime budget of €700 for a seven-day flight and contains two groups (in a Meta-like setup, two ad sets). You cannot automatically write down €100/day: the available opportunities and allocation may change, and pacing may distribute spend unevenly. Nor can you conclude, without the product configuration, that each group will get €350.

The schedule, or flight, defines temporal eligibility:

  • start and end;
  • the account time zone in which the dates are interpreted;
  • where the product supports it — dayparting, that is, the allowed weekdays and hours.
configured status = enabled
start = 2026-09-07 00:00 Europe/Berlin
end   = 2026-09-14 00:00 Europe/Berlin

Before the start, the campaign may be enabled but have the effective status pending and not deliver ads. After the end it becomes ended/completed, even if part of the €700 was not spent. Dayparting can make the campaign temporarily ineligible inside an active flight. Budget, schedule, and status work together: the operator’s permission is necessary but not sufficient for showing ads.

Where the user lands and where the system gets its signals

A campaign ties together two different routes: the user must reach the destination, and the measurement systems must receive identifiers and events. These routes may intersect but need not coincide.

The landing page, destination, or final URL is the first target surface after the interaction: a web page, an App Store/Google Play listing, or a deep link into an app. It is part of the user experience and the product path, not a tracking record.

Tracking settings38 are the configuration of observability. They may include:

  • campaign, group, and ad IDs;
  • URL parameters, macros, tracking templates, and the final URL suffix;
  • a pixel, app SDK, server-to-server integration, or MMP39 as the event source;
  • the selected conversion actions;
  • the attribution40 configuration boundary, for example the platform rule/window in use.

Attribution mechanics, mobile privacy, postbacks, and discrepancy analysis are not covered here; what matters is seeing where the campaign connects to them.

user path:
  ad click → final URL / store listing / deep link

measurement path:
  click ID + campaign/group/ad IDs → platform and/or MMP
  install → trial → paid_subscription events → reporting/optimization

An illustrative URL may pass internal identifiers:

https://example.com/app?campaign_id=cmp_subscriptions_42&ad_id=ad_7

The parameter names are not an industry standard. Platform macros can substitute the actual IDs at click time; the destination or analytics then stores them for mapping. A tracking template governs the measurement path but is not a landing page.

Google Ads provides a product-specific example of separating the paths: with parallel tracking, the user is directed to the final URL while click measurement happens in the background. This is Google’s implementation, not a guarantee for every platform, browser, or MMP link.

For the subscription app, the ad with creative_id=cr_video_a promises premium features and leads a new user to the store listing. After the install, the SDK or MMP registers the install; the backend may later pass the trial and the paid subscription. For the platform to use the subscription for optimization, it is not enough to see this event in analytics: the right conversion action must be correctly mapped and selected in the campaign configuration.

Creative promise Destination Observable event Consistency check
“Try premium for 7 days” Store listing for new users Install, then trial The listing describes the same product and offer
“Continue setting up your subscription” Deep link for the installed app Subscription-start screen view The deep link opens the expected state
“Compare plans” Web pricing page Landing-page view, purchase The URL leads to the right locale/currency version

Landing-page optimization and CRO (conversion rate optimization) are separate topics.

An MMP also does not receive the campaign hierarchy magically. The platform, the tracking link, and the MMP must agree on the mapping of IDs and event names. Having an ad_id without parent mapping does not automatically restore account/campaign/group relationships. Conversely, a correct hierarchy in the platform does not prove that the downstream event source passes the required identifiers.

Lifecycle without false linearity

For a first acquaintance, it is convenient to memorize the lifecycle as:

draft → learning → active → paused → completed

But this is a mnemonic, not a universal linear state machine. It mixes the state of the configuration, the permission to deliver, the schedule, and the state of the optimizer. The real object is better described as a vector of states.

  • Draft: the configuration has not been published yet. In some systems the draft exists only in the UI or the client and is not yet a server-side campaign.
  • Learning41: the delivery/bidding model gathers performance data after launch or a material configuration change. Impressions and spend may already be happening during this time.
  • Active/enabled: the operator has permitted delivery. Actual impressions additionally depend on the parent, review (the platform’s policy and technical check of ads), schedule, budget, errors, and the availability of eligible opportunities.
  • Paused: the operator has stopped delivery. This is usually a reversible transition; resuming does not create a new campaign.
  • Completed/ended: the end condition has occurred, most often the schedule end. The object, reporting, and history are usually preserved; this is not a synonym for deleted.
draft → publish → pending/review → eligible delivery
                                  ↘ learning → stable delivery
active/learning ↔ paused
active or paused → end condition → completed/ended
material edit → learning again

The arrow learning → active is misleading: learning can be a sub-state of active delivery rather than a prohibition on impressions that precedes it.

Axis Who or what defines it Possible states Example of one moment
Configured status Operator/API Draft, enabled, paused, removed Campaign enabled
Effective delivery status Platform after all constraints Pending, eligible, not delivering, ended Ad set eligible
Review/issues Policy and technical checks Pending review, approved, limited, rejected/error Ad approved
Learning status Optimization subsystem Learning, stable, limited data Strategy/ad set learning

In the Google-specific view, a campaign may have the status Eligible while the bidding strategy is simultaneously Learning. In the Meta-specific view, an active ad set may be in the learning phase. The labels and exact rules differ, but the portable conclusion is the same: a single status column does not describe the whole operational state.

Changing the campaign and re-learning

Before the change, the running group is optimized on installs:

configured: active
schedule:   eligible
review:     approved
optimizer:  stable on install event

The advertiser changes the optimization event to paid_subscription and updates the creative for the subscription offer. Historical installs and reactions to the old message no longer fully describe the new configuration. The platform may return the optimizer to learning while continuing active delivery:

configured: active
schedule:   eligible
review:     approved or pending for the new creative
optimizer:  learning on paid_subscription event

Meta, for example, counts changes to targeting, creative, optimization event, the composition of ads, the bid strategy, and a prolonged pause of the ad set among possible significant edits; the effect of a budget change depends on the product rules and magnitude. This list cannot be transferred to Google Ads, a DSP, or an ad network42, and the thresholds and duration must not be assumed constant. The general causal link is only this:

material configuration change
  → prior data describe the new decisions less well
  → the optimizer gathers data again

Pause does not have to precede completion: a campaign can end on the end date straight from active delivery, and a paused campaign can remain paused until a manual resume or transition to ended when the end condition occurs.

How to read any campaign

  1. Who owns the ad account, who has access, and which currency/time zone are in effect?
  2. At which object level does each setting live, and who inherits it?
  3. Which business objective is declared, and which optimization event is actually selected?
  4. Which targeting rules and placements define eligibility?
  5. Which bid strategy is selected, and which target/cap applies to it?
  6. Where are the budget and schedule set, and what are their scope and basis?
  7. Which IDs, URL settings, and event sources form the tracking path?
  8. Where does the user land after the interaction?
  9. What are the configured, effective, review, and learning states right now?

Common Confusions

  • An account is not the advertiser company. It is a product/access/billing boundary; a manager account grants access, it does not add a delivery level.
  • A campaign is not just a folder. Parent settings and limits change the behavior of children.
  • Objective, optimization event, tracked conversion, and billing basis need not coincide. They are different configuration and contract layers.
  • Enabled does not mean delivering right now, and learning does not mean inactive. Parent status, schedule, review, budget, errors, and eligibility can stop delivery; the optimizer can adapt during active delivery.
  • Pause does not mean completed. Pause is reversible, although on some platforms a prolonged pause itself counts as a significant edit; completion usually follows the end condition.
  • A tracking URL is not a landing page. The measurement path and the user path solve different problems.

What to Remember

  1. Campaign hierarchy is a model of scope and inheritance, not a single cross-platform schema; every setting has a source: account default, campaign value, or ad-level override.
  2. The ad account sets the administrative boundary; the campaign translates one intent/flight into shared delivery rules; an ad group/ad set groups ads with shared execution rules, and the exact placement of fields depends on the product.
  3. The ad is the delivery binding, the creative is the content; one creative can be used by several ads.
  4. The objective describes the overall intent, the optimization event the observable signal for decisions; bid strategy, strategy target, actual bid, and billable price are different objects.
  5. Targeting limits the allowed opportunities; placement limits the media environment and slot.
  6. Budget and schedule constrain resources and time but guarantee neither even spend nor results.
  7. The destination leads the user; tracking settings tie IDs and event sources to measurement/optimization.
  8. The operational lifecycle must be read as several axes: configured, effective, review, and learning status.

Check Yourself

  1. A campaign has the objective App promotion, is optimized on paid_subscription, tracks install, trial, and subscription, and its billing basis is CPM. Why do these values not contradict one another?
  2. An ad is set to active but receives no impressions. Which parent, schedule, review, budget, and eligibility states should you check?
  3. Why can changing the optimization event from install to subscription return the optimizer to learning without changing the configured status active?
  4. Which settings would you expect to share between two ads and which to keep separate, if they use one creative but lead to different regions and destinations?

Sources and Further Reading

  1. Google Ads Help — Account, campaign, and ad group performance and Google Ads API — Campaigns overview — the Google-specific hierarchy and campaign resources; the placement of fields depends on the campaign type and API version.
  2. Meta Marketing API — Basic Ad Creation — separate campaign, ad set, creative, and ad in the Meta Graph API; this is a vendor schema, not an industry standard.
  3. Google Ads Help — About campaign objectives and About conversion goals — the distinction between the high-level objective, conversion goals/actions, and their use in bidding.
  4. Meta Business Help Center — About performance goals — the product-specific link between objective, performance goal, and the required signals.
  5. Google Ads Help — About tracking in Google Ads — tracking-template inheritance, final URL settings, and parallel tracking as a Google-specific implementation.
  6. Google Ads Help — About campaign statuses and Google Ads API — Bidding Strategy Status — separate operational and learning statuses in Google Ads.
  7. Meta Business Help Center — About the learning phase, Significant edits and learning phase and Meta Marketing API — Budgets — Meta-specific learning, significant edits, daily/lifetime budgets, and scheduling behavior.

Footnotes

  1. Campaign — an organized set of an advertiser’s advertising activity with a goal, a budget, delivery rules, and creatives. Before delivery, its conditions are communicated to the buying systems; objects and events are linked by identifiers such as campaign_id. ↩

  2. Advertiser — a market participant that funds advertising for a business result: installs, subscription purchases, growth in awareness. It buys not a person but the opportunity to address an audience in a specific context; it creates demand and sets goals, budget, and creative. ↩

  3. Budget — a constraint on the available spend over a given scope (a campaign, an ad set, a shared pool of several campaigns) and time basis. Common are the daily budget (a hard calendar cap, an average daily target, or another form — the product defines this) and the lifetime/flight budget for the whole interval. A budget constrains spending but does not guarantee inventory, conversions, even pacing, or an exact invoice amount. ↩

  4. Targeting — the campaign’s rules about to whom and where an ad may be shown: hard controls (eligibility rules — geo, device, context, audience/keyword criteria, exclusions) that restrict the set of permitted opportunities, and signals/hints that in algorithmic products only steer delivery without narrowing the eligible set. Targeting answers the question “for which opportunities/users/contexts is showing possible,” as opposed to placement (“where exactly”) and optimization (“which of the permitted impressions to choose”); even if the API stores them in one object, these are different axes. ↩

  5. Schedule (flight) — the campaign’s temporal eligibility: the start and end, the account time zone in which the dates are interpreted, and, where the product supports it, dayparting (the permitted days of the week and hours). Before the start, the campaign can be enabled but have the effective status pending; after the end it finishes, even if part of the budget was not spent. ↩

  6. Ad — the executable delivery unit of a campaign: it links the parent group (ad group or ad set), the advertiser identity, the creative, the destination, tracking, and the status. An ad is not the same as a creative: one creative can run in several ads with different parent rules, destinations, and states. ↩

  7. Media spend — the money an advertiser allocates and spends on buying advertising. It passes through the media sellers and ultimately forms publisher revenue, shrinking along the way by fees; it is not a synonym for publisher revenue, nor for intermediary fees — these are different amounts in one chain. ↩

  8. Ad account (advertiser account) — a tenant on an advertising platform within which campaigns and related settings exist; it forms several boundaries at once: ownership and access (the operators’ roles and permissions), the billing identity, the currency and time zone, the namespace of identifiers, and the shared configuration (data sources, brand assets, defaults). The advertiser’s legal company and the ad account are not the same thing: one company may have several accounts across regions, brands, and currencies, and one account may serve several initiatives of the same legal entity. ↩

  9. Payee / payer — the two sides of one payment obligation: the payer pays for the billable event, the payee receives the payment. Risk allocation in a pricing model is described through them: under CPM the payee earns the right to charge early in the funnel and the post-impression risk sits with the payer; under CPA the payee takes on all the risk up to the conversion. One company can be the payee in one contract and the payer in another. ↩

  10. Conversion action — a platform-configured definition of an event that counts as a conversion for reporting and optimization: the source (pixel, SDK, S2S, import), the event name, counting rules (one or every per interaction), the value, and the window. A platform may have several conversion actions per account; which are primary (used for optimization) and which secondary (reporting only) is part of the campaign configuration. ↩

  11. Manager account — the platform’s administrative layer that gives an agency or an internal group centralized delegated access to several ad accounts. This is administrative access, not an additional delivery layer: a manager account does not participate in the delivery hierarchy of each campaign. ↩

  12. Agency — a contractor company that plans and executes marketing and media work on behalf of an advertiser: develops strategy, prepares creative, selects channels, launches a campaign, and reports on results. An advertiser can keep media buying in-house, hand it to an agency in full, or split the responsibility. An agency is an organization and a contractual role, as opposed to a media buyer — an operational function that can also work inside an advertiser. ↩

  13. Campaign objective — the high-level business intent or setup guidance communicated to the platform when the campaign is created: awareness, traffic, leads, app promotion, sales. The objective suggests campaign types, features, and defaults, but need not match the event that the optimizer directly predicts: the optimization event is chosen separately. ↩

  14. Ad group / ad set — the intermediate level of the campaign hierarchy between the campaign and the ad, grouping ads with shared execution rules. The names and the set of fields are vendor-specific, and there is no universal schema: in the Google-like model, the ad group groups closely related ads and triggering criteria (for example, related keywords); in the Meta-like model, the ad set holds the audience, placements, optimization, bid, budget, and schedule. ↩

  15. Placement (ad slot or selectable media scope) — an overloaded product term. On the publisher side, it is a predefined ad slot or rule for ad appearance that generates ad opportunities as the product is used. On the buy side, placement can mean an explicitly selected delivery environment — a site, app, channel, video, section, or individual slot. The entity level must be clarified from the product contract. ↩

  16. Bid — a buyer’s offer to pay a certain price for a specific ad opportunity, usually expressed as a CPM. A bid is a pre-event decision: it is neither the final price (clearing price) nor the billable amount; in programmatic, the DSP forms a bid for each bid request separately. ↩

  17. DSP (Demand-Side Platform) — a platform that automates the purchase of advertising opportunities for an advertiser: it aggregates access to several supply sources, evaluates each opportunity, and decides whether to bid and how much to pay. It belongs to the demand side not because it “creates demand” but because it acts in the buyer’s interest. ↩

  18. Ad server — a system that selects, delivers, and logs advertising under given rules. There are publisher-side ad servers (matching direct campaigns, networks, and programmatic demand, managing delivery) and advertiser-side ones (storing creatives, counting impressions and clicks); the term denotes a function, not a market side. ↩

  19. Creative — the advertising material that is delivered and shown to the user: a banner, a video, a native format, a playable. Along with targeting rules it is an object of delivery and must match the format and rules of the publisher’s environment; for a campaign, several creatives are usually prepared. ↩

  20. Destination (landing page, final URL) — the first target surface after an interaction with the ad: a web page, an App Store/Google Play listing, or a deep link into an app. It is part of the user path, not a tracking record: the tracking template and URL parameters control the measurement path, but not the landing page. ↩

  21. Optimization event — the observable event that the delivery system learns from and optimizes impressions toward: install, trial start, paid subscription, purchase. The advertiser selects it in the campaign settings (different platforms call it a conversion action, conversion goal, or performance goal). It is not the campaign objective (the business intent), not the billable event (what is paid for), and not a strategy parameter such as target CPA. A deeper event yields fewer signals and a longer learning phase. ↩

  22. Impression — a delivery or display event for the selected ad, recorded by a system under a specific rule; a counting unit, not a fact of human perception. Served, rendered, and viewable are different delivery states, so the counters of different participants in the same deal may not match. ↩

  23. Click — a qualifying user-initiated interaction with an ad, recorded under a specific system’s rule. Even a single action has several measurement points: initiated, measured (click tracker), received (destination), and resolved (landing page) clicks need not match due to dropped connections, redirect chains, and filters. ↩

  24. Conversion — a valuable action or outcome that the advertiser has defined as significant (install, trial, first payment, renewal, purchase) and that a system has counted under its measurement and attribution rules. Conversions cannot be summed without an explicit counting rule: one click can lead to several conversions. An observed conversion is a recorded event; an attributed conversion is an event to which an attribution rule assigned credit; neither proves causality. ↩

  25. Measurement — the function of recording and aggregating advertising events (impressions, clicks, outcomes) for reporting and optimization. Measurement providers give an independent point of observation; different participants have different timestamps and counting rules, so reports do not have to match perfectly. In mobile, the dedicated category is the MMP. ↩

  26. Bid strategy — a policy that translates the optimization goal and constraints (a target or a cap) into auction bids. The strategy, its target/cap, the actual bid for a specific opportunity, and the billable price are four different entities: a single numeric target CPA is not the actual bid, and the actual bid does not by itself determine the billable amount. ↩

  27. Pricing basis — the contractual rule for calculating a price: the object for which the buyer pays — an impression, click, action, install, lead, a share of proceeds, a period of access to software, or another agreed result. A metric’s name in an interface (CPM, CPC, CPA) does not by itself fix the basis: the same name can be a contractual price, a bid, or the actual average after the events, so only the basis named in the contract creates a monetary obligation. ↩

  28. CPM (Cost per Mille) — the cost of a thousand counted impressions for the buyer: CPM = advertiser cost or spend / counted impressions × 1,000. The term is ambiguous without a contract: it can mean a pricing basis, a rate, a bid, or a post-fact observed average CPM; the observed CPM answers the question “how much did the buyer spend per thousand counted impressions.” ↩

  29. CPC (Cost per Click) — the cost or spend per qualifying clicks under a disclosed rule: CPC = cost / qualifying clicks. A bid/target CPC is not the actual average CPC: the former is a bid or an optimization target, the latter is a post-fact average. ↩

  30. Billable event — a qualifying event defined by the contract, after which the payee is entitled to accrue the billable amount — the sum under the pricing basis after counts, rates, validation, and contractual adjustments; it is not necessarily invoiced, recognized as revenue, or paid. The event is set by contract policy, not automatically by the protocol: an auction win, a win notice, and a billing notice are different points, and a win does not guarantee delivery or a charge. ↩

  31. Ad opportunity — a specific opportunity to select and show an ad that arises when a user reaches a placement. A short-lived event: in a digital environment it can vanish faster than a person can make a decision, so systems process it in milliseconds, and in programmatic it is put up for bidding as a separate unit. ↩

  32. Publisher — the owner or operator of a media environment where advertising opportunities arise: a website, a mobile app, a video service, a game. It monetizes the environment with advertising, creates supply, and decides which placements, formats, and buyers to admit, balancing revenue against user experience. ↩

  33. Audience exclusion / suppression — a negative targeting rule designed to exclude entities with a named membership or status; the actual completeness of the exclusion is limited by identity match, freshness, propagation latency, and the semantics of the specific platform. ↩

  34. Auction — the mechanism for choosing a winner among several bids for one ad opportunity and for determining the price (clearing price) under the auction’s rules — first-price, second-price, and their variants. An auction win is the event of choosing a winner; it is not an impression and does not by itself make the impression billable. ↩

  35. CPA (Cost per Action) — the cost per advertiser-defined qualifying actions: CPA = cost / qualifying actions. The action is defined by the campaign contract — a trial, an order, a lead, or a subscription, not necessarily a new customer — so a CPA cannot be read without the name of the action or compared between campaigns directly. ↩

  36. Pacing — the policy of distributing spend over time within budget constraints: whether to spend evenly, accelerate on cheap or high-quality opportunities, or hold back the budget. Pacing allocates the resource but does not promise even spending: the available opportunities and the allocation change. ↩

  37. Advertising inventory — the set of available or forecast opportunities to show advertising, bounded by the environment, the slot, the format, the time, the publisher’s rules, and the permissible audience context. Inventory is not a list of users and not a warehouse of pre-produced impressions: an opportunity arises and disappears at the moment the product is used. ↩

  38. Tracking settings — the campaign’s observability configuration: the transmitted identifiers (campaign/group/ad IDs), URL parameters, macros, the tracking template and final URL suffix, the event sources (pixel, app SDK, server-to-server integration, MMP), the selected conversion actions, and the attribution configuration boundary. Tracking settings govern the measurement path and do not replace the destination; URL parameter names are not an industry standard. ↩

  39. MMP (Mobile Measurement Partner) — a specialized category of measurement providers for mobile: it measures installs and in-app events, performs attribution, and provides independent data to the parties in the deal. Not a synonym for just any measurement system. ↩

  40. Attribution — the rules by which the available advertising touchpoints (impression, click) are matched to outcomes (install, registration, purchase) and receive credit for the conversion. Attribution answers the question “which source was credited with the action under the chosen rules,” not “whether the ad was the true cause”: credit does not prove causality. Attribution providers are a separate cross-cutting category; in mobile, the MMP. ↩

  41. Learning phase (learning status) — the state of the optimizer in which the delivery/bidding model gathers evidence after launch or a material configuration change: earlier data describe the new decisions less accurately. Learning is one of the axes of the operational state alongside the configured, effective, and review statuses, not the opposite of active: impressions and spend continue, and vendor-specific significant edits (targeting, creative, optimization event, the set of ads, the bid strategy) can return the optimizer to learning without changing the configured status. ↩

  42. Ad network — an intermediary that aggregates advertising opportunities (inventory) from many publishers and sells them to advertisers as a single packaged product: the network takes over supply selection, pricing, and delivery, while the buyer gets one manageable offering instead of a dozen separate contracts. Prices inside the network are usually opaque to the buyer. Historically, many ad networks added auction mechanics and rebuilt themselves as ad exchanges, so both functions are often combined under one brand. ↩