> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# From signup to your first booking

> One path for a publisher that runs an ad server such as Google Ad Manager and has no sales agent of its own: what you need, what you do, what Apostra does, and what holds a first booking back.

This page is for a publisher that runs its own ad server, usually Google Ad Manager (GAM), and has no
sales agent of its own. It follows one example from signup to a first booking: a Turkish news site on GAM
that a Dutch buyer has invited, because the buyer wants the site's inventory targeted to the Netherlands.
You can follow it yourself in the Apostra web app, or hand it to your own agent. Each step names the page
that has the detail.

The steps below show the agent calls. In the web app you can ask the in-app agent to do any of them for you
in plain words, for example "set my payout currency to EUR and my markets to the Netherlands and Turkey".
Where a step needs a form or a page, the step names it.

Steps 1 to 7 are yours. Step 8 is work Apostra does before buyers outside your organization can find you.
Apostra publishes no timings for it.

## If you have your own sales agent

The steps below follow a publisher on Google Ad Manager. If you already run an AdCP sales agent, you are a Listing,
and these steps differ:

| Step | With your own agent |
| - | - |
| 1 | Sign up as below and choose the Listing option. New signups start inside an organization. |
| 2 | Keep the account a Listing. Do not switch it to Storefront, which is the agent Apostra hosts. |
| 3 | The same: payout currency and markets. |
| 4 | The same: declare the publisher domains. Each domain's `adagents.json` names your agent's URL exactly as you connected it, not `https://apostra.com`. See [Publisher authorization](https://docs.apostra.com/v3/seller-publisher-adagents.md#if-you-sell-only-through-your-own-sales-agent). |
| 5 | Instead of connecting GAM, register your agent in your organization's Agents account and connect it to your seller account. See [Connect your own sales agent](https://docs.apostra.com/v3/seller-partner-connection-form.md#connect-your-own-sales-agent). An older account that is still standalone becomes an organization when it creates the Agents account. |
| After 5 | Pass certification. Apostra sends new buys only for the use cases your agent has passed. Turn on **Allow certification buys** and see [Certification](https://docs.apostra.com/v3/certification.md). |
| 6 | The same: verify your brand domain. The AAO registry must also be able to find your agent (see "What it costs"). |
| 7 | Step 7 drafts products from GAM. For your own agent, check what your agent declares: see the [sales agent checklist](https://docs.apostra.com/v3/seller-agent-checklist.md). |
| 8 to 10 | The same: marketplace review, billing and payout, and the go-live checklist. |

Before step 5, work down the [sales agent checklist](https://docs.apostra.com/v3/seller-agent-checklist.md).

## Signup link: how a publisher signs up and how a buyer invites a seller

**Publishers sign up here:** [app.apostra.com/signup?intent=storefront](https://app.apostra.com/signup?intent=storefront).
It opens straight on the publisher path. Then follow the steps below.

**Buyers inviting a publisher:** send the publisher that link with a line about why, and record a supply
request for its domain and channel so your interest is kept. The link and the request contact nobody for
you. See [Invite a seller that is not on Apostra](https://docs.apostra.com/v3/media-partner-availability.md#invite-a-seller-that-is-not-on-apostra).

## What it costs

There are two ways to be on Apostra, and they match the two account types in step 2.

* **Listing** is free on the Listing plan. You bring your own sales agent, or use a third party's, and Apostra lists
  your products. The Listing plan has no IU price, and it waives the brief-response and media-buy charges the Storefront
  agent plan carries.
* **Storefront** means Apostra hosts the agent for you. On the Storefront agent plan you pay per Intelligence
  Unit (IU) for the seller-side activities it meters: a brief response (1 IU for each completed brief
  response) and an Apostra media buy (1 IU for each qualifying buy per billing period). Plans have no monthly
  commitment. The price per IU in each currency is in
  [What you pay as a seller](https://docs.apostra.com/v3/plan-and-billing.md#what-you-pay-as-a-seller). That is the standard list;
  the Rate Card your organization accepts is the authority, and a negotiated offer replaces the list price.
* Neither needs a paid AgenticAdvertising.org (AAO) membership. On Storefront there is nothing to do. On
  Listing, the AAO registry must be able to find the sales agent you connect: declare it in your
  `brand.json` or `trust.json`, or add a community entry for it in the registry (see
  [Registering your agent with AAO](https://docs.apostra.com/v3/identity-documents.md#registering-your-agent-with-aao)).

What you are charged follows the plan your organization accepts. Only the Standard plan prices an activity by the
account type that incurred it, so on any other plan switching the account type does not change what you are billed
(see [How the account type affects what you pay](https://docs.apostra.com/v3/seller-account-type.md#how-the-account-type-affects-what-you-pay)). Apostra has a separate Enterprise route with no public price.

## What you need before you start

* A work email address on your company's domain. Signing up to sell needs one, and a personal address
  such as a free webmail account is not accepted for it.
* A GAM network, and someone with the rights in GAM to add a service account user and give it a role (see
  step 5).
* The currency you want to be paid in, chosen from the currencies Apostra can settle (see step 3).
  Turkish lira is not one of them. Your GAM network must also book in that currency, as its primary currency
  or a secondary one (see step 5).
* The domains your inventory runs on, such as your news site's domain (see step 4).
* A list of the countries and channels you want to sell to, including countries where your readers live
  but you do not (see step 3).

## Step 1: sign up with your work email

Choose the option to sell inventory and sign up with your work email. Apostra creates a Seller Account.

If your email domain already has an organization on Apostra, you need an invitation from that organization
to sign up. Ask the person who set it up to invite you.

## Step 2: check your account type

A Seller Account is a Listing or a Storefront. Read yours with `get({ "kind": "seller" })`, which returns
`sellingMode`. [Account type](https://docs.apostra.com/v3/seller-account-type.md) is the full rule. What matters for a publisher
with no sales agent of its own:

* **Listing** means you bring your own sales agent, or use a third party's. Apostra lists your products
  and does not host an agent for you.
* **Storefront** means Apostra hosts the agent that answers buyer briefs for you.

Setting up an ad server that Apostra manages for you is Storefront setup. When that setup has to create
your storefront, it records the Storefront type. It does not change the type of an account that already
has one. So if you are a publisher with an ad server and no agent of your own, read `sellingMode` and,
if it says `listing`, ask a direct administrator of the billing organization to switch it with
`save_seller({ "sellingMode": "storefront" })`. The Apostra-hosted agent is what a Storefront
is.

If you connect a managed ad server while the account is still on Listing, the Connect form shows a readiness
item explaining the available switch. The same item is in `get({ "kind": "seller", "include": ["readiness"] })`.
It is advisory and does not stop transactions. A direct administrator of the billing organization reviews the
applicable [account-type charges](https://docs.apostra.com/v3/seller-account-type.md#how-the-account-type-affects-what-you-pay) and confirms
any switch. The connection and the account type do not change automatically.

A Storefront needs a plan that covers it. If yours does not, the switch is refused with `CONFLICT` and the
reason says what to do next. Only the Standard plan prices an activity by account type, so on any other plan
the switch does not change what you are billed.

The signup screen's Listing option says it "includes your connected sales agent". Read that as an agent
you connect yourself. It does not mean Apostra provides one.

## Step 3: set your payout currency and your markets

Both of these decide who can buy from you, so set them before you build products.

**Payout currency.** Apostra settles in these currencies: USD, EUR, GBP, JPY, CHF, CAD, AUD, NZD, CNY,
HKD, SGD, SEK, NOK, DKK, PLN, KRW, INR, MXN, BRL and ZAR. Local currencies outside that list, such as
Turkish lira (TRY), are not accepted. Send `defaultCurrency` and `paymentCurrencies` to `save_seller`, and
include the default in `paymentCurrencies`.

A product shows to buyers only if it has a price Apostra can use. A product priced only in a currency that
is not one of your settlement currencies stays hidden. A product with no pricing option at all stays
hidden too. [Setup checklist and go-live](https://docs.apostra.com/v3/seller-readiness.md) has the full rule.

Your ad server's own currency matters as well: Apostra never converts an order from one currency to another.
When you connect GAM in step 5, your **default** payout currency must be one your GAM network books in, either
the network's primary currency or a secondary currency enabled in GAM. A second payout currency does not
count. If yours does not match, the connection is refused. Set this before step 5. See
[ad-server execution currency](https://docs.apostra.com/v3/seller-readiness.md#ad-server-execution-currency).

**Markets.** A buyer request that names countries or channels outside your markets never reaches you. In
the example, if you save only Turkey, the Dutch buyer's request for the Netherlands is never sent to your
sources. If your readers include people living abroad, add those countries, or accept every country with
`acceptsAllCountries: true`. If you set no countries, requests from every country reach you. Save channels
and countries together in one `save_seller` call. [Markets](https://docs.apostra.com/v3/seller-markets.md) has the rule and the
country groups.

## Step 4: declare the domains you sell

Before you build products, tell Apostra which publisher domains your inventory runs on, such as your news
site's domain. Send them with `save_coverage({ "add": ["example.com"] })`, or ask the in-app agent to add them.
Every product you create names the domains it covers, and the product form has nothing to offer until a
domain is declared.

Apostra then reads each domain's `adagents.json`. A domain that serves pages but has no `adagents.json` is
fine: authorization does not stop a booking. A domain Apostra cannot reach at all, because it does not exist or
does not answer, is not passed on to your ad-server source, and the product form then says "No publisher
property selectors were returned by this source". Check the spelling, and re-check a domain with
`save_coverage({ "refresh": ["example.com"] })`. [Re-checking a publisher in your coverage](https://docs.apostra.com/v3/seller-publisher-coverage.md)
has the detail.

## Step 5: connect Google Ad Manager

Call `save_inventory_source` with only `adServer`:

```json theme={null}
{ "adServer": { "type": "google_ad_manager" } }
```

The call creates nothing. It opens the **Connect ad server** form and returns `serviceAccountEmail`, the
email of a service account Apostra creates for your organization. Credentials are entered in the form and
never pass through chat.

1. In GAM, add `serviceAccountEmail` as a service account user: in your network's global settings, turn on
   **API access** and choose **Add a service account user**. Do not invite it as an ordinary user.
2. Give it a role that can read inventory, traffic orders and line items, and approve orders. Apostra
   recommends the **Administrator** role. A custom role with trafficking and order approval works, and so
   does adding the user as an approver in your order approval workflow. The built-in **Trafficker** role
   cannot approve orders.
3. Enter your network code in the form.

The person who does step 1 therefore needs rights in GAM to add users and assign roles. If the GAM user
cannot approve orders, a new listing on Apostra is refused until the permission is corrected.

If your default payout currency is not one your network books in (step 3), the connection is refused and the
form says so. Change your default
payout currency to one the network books in, or add your currency as a secondary currency in GAM, then connect
again.

**Set a default advertiser.** After connecting, the **Ad server source** card asks for a default GAM
advertiser for live buys. Choose **Set default advertiser** on the card. Buyers billed through Apostra book on
that advertiser, and until it is set their requests stop before reaching your network.
[Connecting an ad server](https://docs.apostra.com/v3/seller-connect-ad-server.md) covers the form, and
[Google Ad Manager access](https://docs.apostra.com/v3/seller-gam-access.md) lists every permission the role needs, the roles that
cannot approve orders, and how to fix a missing permission.

## Step 6: verify your brand domain

Buyers see your brand domain as who they are dealing with. An unverified brand domain blocks go-live. It
appears as the `operator_domain` check in your setup checklist.

If your brand domain is the domain you signed up with, you verify that domain once. Any one of these
works: an active member of the account with an email address on the domain, a DNS TXT record that Apostra
reads directly from DNS, or a manual review by Apostra for when neither of the first two is possible. If
your brand domain differs from your registered domain, you also publish evidence that links the two.
[Which domain is which](https://docs.apostra.com/v3/domains.md) has the record name and value and the steps.

## Step 7: create your products

A product is what a buyer sees and books. In the web app, open **Inventory components**, which lists the ad
units and placements synced from GAM. Choose **Select suggestions**, then **Draft product from** the components
you picked, and complete the form: formats, channel, delivery type, price and the publisher domain it covers.
An agent creates the same product with `save_wholesale_product`, passing the `sourceId` of your GAM source.

Save a product with `status: "active"` when it is ready, because a `draft` is hidden from buyers. Give each
product a price in one of your settlement currencies (step 3). [Product creation](https://docs.apostra.com/v3/seller-product-creation.md) has
the fields and the refusals.

## Step 8: what Apostra does before buyers can find you

**Marketplace review.** A new storefront starts as `PENDING_REVIEW`. Buyers in your own organization can use
it straight away. Buyers outside your organization do not find it in discovery until Apostra reviews it and
lists it (`LISTED`). Your checklist shows the review as open while it waits. If you are waiting on it, ask
your Apostra contact. Apostra does not promise a time.

**Listed without waiting, when a buyer asked for you.** If a buyer has asked Apostra for inventory one of your
active, priced products covers, Apostra lists you itself once your brand domain is verified, an inventory
source is connected and healthy, and at least one product is active with a price. Your checklist says which of
these you still need. [Listed without waiting](https://docs.apostra.com/v3/seller-readiness.md#listed-without-waiting-when-a-buyer-asked-for-you)
has the rule.

**No certification holds back booking today.** Apostra does not run a go-live certification on a GAM source
before buyers can book. If one is required for your ad server in future, your checklist shows it as
"Ad-server go-live certification" and says when booking opens.

## Step 9: billing and payout

Accepting the Terms, how you pay Apostra and where you are paid are set in
[Plan & Billing](https://docs.apostra.com/v3/plan-and-billing.md). A person does this in the Page: bank details are typed into the Page
and do not pass through the model. Saving payout details records a request, and they take effect only after a
direct administrator approves them on Apostra (see
[Change where a Seller is paid](https://docs.apostra.com/v3/billing-plan-and-invoices.md#change-where-a-seller-is-paid)).

## Step 10: check the go-live checklist

Call `get({ "kind": "seller", "include": ["readiness"] })`. `readiness.goLive.state` is `setup` until
every required step is complete, and `goLive.progress.nextStepId` names the next one. The
[setup checklist](https://docs.apostra.com/v3/seller-readiness.md) lists every check, what blocks going live, and the difference
between that state and whether buyers can use you right now. For the second question, call the status tool.

The checklist can read live before you have a product. A buyer finds nothing until you have at least one
active product with a price (step 7).

## Approve and map your buyers

Before a buyer's agent can book, it asks you for an account: one brand bought through one agency. Apostra
approves it for you when it asks for standard payment terms, and on a GAM source run by Apostra a buyer
billed through Apostra books on the default advertiser you set for that connection. A buyer waits for you
when you bill them directly, ask for longer terms, or need to choose which GAM advertiser they are. The
[Buyer Account Mapping Page](https://docs.apostra.com/v3/seller-buyer-account-mapping-page.md) shows who is waiting, and
[Why you approve and map buyers](https://docs.apostra.com/v3/seller-why-approve-and-map-buyers.md) explains the step.

## Your first booking

When your checklist reads live, you have an active product and Apostra has listed you, a buyer's agent can
send you a brief, see your products and book one.

A buyer outside your organization must switch you on for its advertisers before your products appear to it,
even when your markets, channels and currencies match its own. Apostra does not switch a new seller on for
buyers; it does that only for market makers. Your [setup checklist](https://docs.apostra.com/v3/seller-readiness.md#buyers-switch-you-on)
shows how many buyer accounts outside your organization, and how many of their advertisers, have switched you
on. Setting up the buyer's account with you then takes a few minutes. Discovery shows your price. For a newly connected GAM network it shows no availability
estimate yet, so a buyer plans a non-guaranteed buy from your price and targeting. For a managed ad server the booking becomes an order
in your GAM network. Depending on your media-buy approval setting, a buy can wait for you to approve it, and
if GAM needs the order approved by someone else, Apostra creates an action item and completes it once the
order is active in GAM. The [Media Buys Page](https://docs.apostra.com/v3/seller-media-buys-page.md) is where you see each buy and
whether anything is wrong with it, and its delivery view shows how the buy is delivering.

## Test your own storefront with a sandbox order

You can test your own storefront end to end before a buyer does. A sandbox order is a real order in your
ad server, booked from a sandbox advertiser, that you then cancel. Nothing is billed, and no one outside your
organization is involved.

The quickest way is to paste a request to the Apostra assistant, in the buyer account described below:

> Book a sandbox order for ROS Display using the sandbox advertiser, with no creatives and a flight that
> starts at least a week from now. Give me the order id, then cancel it.

The assistant follows the steps on this page. It asks you to confirm before it books the order and before it
cancels it.

### Who can place one

The supported way is a **buyer account inside your own organization**, with the order placed from that account.
Your own organization's buyers can use your storefront straight away, without waiting for marketplace review
(see step 8 above).

If your organization has no buyer account yet, an organization administrator creates one. Work in the
organization account: the assistant reviews the new account with you, then asks for it, and an organization
administrator approves it on the Apostra site (see [Child accounts](https://docs.apostra.com/v3/buyer-setup.md#child-accounts)).

The first buyer account you create adds the free buyer experience to your organization, if it has none. That
turns on the campaign and buying tools, and the assistant, for your buyer accounts. It does not include
[Prime](https://docs.apostra.com/v3/hosted-buyer-agents.md), the account's own agent, which is a separate beta switched on per
organization.

### The steps

1. **Confirm your company's identity, if asked.** Product discovery stops with `BUYER_SETUP_REQUIRED` until the
   buyer account has a confirmed operator domain. Confirm your organization's own domain, such as
   `yourcompany.com`, with `save_buyer_operator`. Use a real registrable domain, not a made-up test domain and not
   a subdomain. Apostra proves the domain for you when a member of your organization has an email address on it.
   Otherwise see [Which domain is which](https://docs.apostra.com/v3/domains.md). Sandbox work needs the current Terms accepted and a plan,
   but no payment route (see [Sandbox advertisers and live spend](https://docs.apostra.com/v3/account-access.md#sandbox-advertisers-and-live-spend)).
2. **Use a sandbox advertiser.** Reuse one you already have, or create one with `save_advertiser` and
   `sandbox: true`. A sandbox advertiser never spends money and cannot be turned into a live one.
3. **Wait for your storefront to set up the account.** After the identity is confirmed, your storefront opens an
   account for the sandbox advertiser. This can take a few minutes. Read your storefront with `get`, `kind:
   "seller"` and the sandbox `advertiserId`: the advertiser's `accountReadiness` is `pending` while it is being
   set up and `active` when you can search it. `needs_attention` names what is owed. See
   [Where the advertiser's account with a media partner stands](https://docs.apostra.com/v3/media-partner-availability.md#where-the-advertisers-account-with-a-media-partner-stands).
4. **Find your product.** Read your storefront's products with `get`, `kind: "seller"` and
   `include: ["products"]`. You can book one product or all of them.
5. **Book the order.** Create a draft campaign with `save_campaign`, stage the buy with `save_media_buy`, then
   preview the launch and launch the campaign with `save_campaign` and `confirmLaunch: true`. Choose a flight
   that starts at least a week from now. A creative is optional: a buy with no creative waits as
   `pending_creatives`, which is the expected state and not a failure. The media buy id (`mb_...`) is returned when the buy is staged. The
   storefront's own id for it is returned as `liveStatus.storefrontMediaBuyId` when you read the
   buy with `include: ["liveStatus"]`.
6. **Cancel it.** Cancel with `save_media_buy` and `isCanceled: true`. The result is `canceled`, `cancel_pending`
   or `cancel_failed`. Once the buy has canceled, archive it with `isArchived: true`, then archive the campaign and
   the sandbox advertiser if you created it for the test. An archived media buy cannot be undone today: `isArchived: false` is refused on a media buy. A buy that
   was never launched is a draft: archive it, because a draft cannot be canceled.

### What the order is in your ad server

On a managed Google Ad Manager source, a sandbox order is a real order with real line items. It sits under an
advertiser Apostra creates for sandbox orders, named `Sandbox (auto-created by salesagent - do not bill)`.
That is an advertiser in your ad server. It is not an advertiser in Apostra. Sandbox orders on your source
land under it, and Apostra does not map a sandbox account to an advertiser that bills.

To find the order, look under that advertiser, or search for the buyer's brand domain and the flight dates. Unless
you changed your [naming templates](https://docs.apostra.com/v3/seller-gam-access.md#naming-orders-and-line-items), the name is the brand
domain, a temporary id such as `gam_1a2b3c4d`, and the flight dates, followed by a unique tag in square
brackets. The temporary id is not the media buy id Apostra returns, so match on the brand and the dates.

Cancelling releases or archives the order's line items. The order itself may still be in your ad server, so
archive it there when you have finished with it. Apostra archives a draft order only when a booking fails after
the order was created.

### Held storefronts and draft products

Run the test while your storefront is open to buyers. A storefront on [intake hold](https://docs.apostra.com/v3/seller-intake-hold.md)
turns away every buyer, and that includes a buyer account in your own organization, so a sandbox order from one
is refused while the hold is on. Resume the hold for the test and put it back when you have finished. While it is
resumed, other buyers can book, so do not leave it open longer than you mean to.

Your own Seller Account has a separate way to test while the hold is on, described in
[Test your own products while the hold is on](https://docs.apostra.com/v3/seller-intake-hold.md#test-your-own-products-while-the-hold-is-on).
It is not the route on this page.

A product still has to be buyable. Buyers only see an **active** product with a price in one of your settlement
currencies, including buyers in your own organization. A `draft` product, or a product with no price or floor, is
hidden, so a sandbox order cannot book it. Price and activate the product first (step 7 above). A storefront
whose products are all hidden shows a buyer nothing, whether it is on hold or not.

## How you are paid

Normal Seller Accounts use consolidated billing today. Apostra bills the buyer on one consolidated media bill and
passes each payment to you by bank transfer, net of fees, once it arrives. This needs your payout details on
file (step 9). You carry the buyer's credit risk. Apostra publishes no payout schedule in these docs, so ask your
Apostra contact if your finance team needs one. The glossary entry
[Billing (`agent` vs `operator`)](https://docs.apostra.com/v2/concepts/glossary) has the rule.

## Related

* [Account type](https://docs.apostra.com/v3/seller-account-type.md)
* [Markets](https://docs.apostra.com/v3/seller-markets.md)
* [Connecting an ad server](https://docs.apostra.com/v3/seller-connect-ad-server.md)
* [Product creation](https://docs.apostra.com/v3/seller-product-creation.md)
* [Setup checklist and go-live](https://docs.apostra.com/v3/seller-readiness.md)
* [Why you approve and map buyers](https://docs.apostra.com/v3/seller-why-approve-and-map-buyers.md)
* [Plan & Billing](https://docs.apostra.com/v3/plan-and-billing.md)
* [How IU billing works](https://docs.apostra.com/v2/buyer/billing/how-iu-billing-works.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.