> ## 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.

# Pass the go-live test

> Clear the Successful transaction readiness check with a sandbox campaign on your own advertiser.

Before buyers can transact with a storefront, its readiness checklist needs a
**Successful transaction**. For a storefront whose inventory is a modular
source, you can pass it yourself, with no test to request: run an ordinary
sandbox campaign with your own sandbox advertiser against your own storefront.

A sandbox campaign for a product from one of your modular sources is not sent
to the provider behind that source. If the source is connected to a provider's
campaign system, such as Epsilon Retail Media or FreeWheel automatic execution,
Apostra records the sandbox campaign instead of sending it. It cannot create a
real campaign or a charge there. That also means the campaign does not test the
provider connection; see
[Sources connected to a provider](#sources-connected-to-a-provider).

## What the check needs

The **Successful transaction** check (`publish_validation`) turns complete when
one media buy on your storefront has been accepted by its inventory source and
carries that source's media buy ID. A sandbox campaign you launch from your own
account produces that buy. A successful buy from a live buyer satisfies the same
check, but a live buyer cannot connect until your storefront is ready, so for a
new storefront the sandbox campaign is the route.

The check reads the whole storefront:

* **Modular sources.** The sandbox campaign is the evidence. For a source
  connected to a provider it is recorded in Apostra and not sent to the
  provider; for any other modular source it is booked against your booking
  ledger.
* **Managed ad-server sources.** A storefront whose active sources are all
  managed ad servers reports the check complete without a test. A mixed
  storefront still needs the campaign, and it covers the sources that are not
  managed ad servers.
* **External sales agents.** An external Agent source needs its own current
  proof of `create_media_buy`. A sandbox campaign does not stand in for it, and
  the check names the Agent that is still uncovered. Use that Agent's Test
  section.
* **Demo storefronts.** The check reports complete with no test while every
  connected source is part of the demo profile.

Run the sandbox campaign, where it applies, after the other blockers on the
checklist are clear.
Check your storefront status for what is still open: the checklist tells you
which blocker comes first.

## Run the sandbox campaign

Use your seller account's own MCP connection. You stay in the same
account for the whole campaign; do not switch accounts.

**1. Create a sandbox advertiser**

Call `save_advertiser` with `sandbox: true`. A sandbox advertiser belongs to
your own account and is test-only. Its sandbox setting is permanent: it cannot
be changed to live later. Every Media Company can create sandbox advertisers.

**2. Create a campaign for that advertiser**

Call `save_campaign` with the advertiser, a brief, a flight, and a budget.
Apostra pins the campaign to your own storefront; a product, proposal, or
media buy from any other storefront is refused.

**3. Choose a product from your own catalogue**

Open your catalogue with `get` for `kind: "seller"` and include the
products, then pass a qualified product to `save_media_buy` to stage a media
buy. You can also ask for proposals with `request_proposals`.

**4. Add a creative**

Call `save_creative` with the campaign to attach a creative to it. See
[Create and verify a campaign creative](https://docs.apostra.com/v3/tool-reference.md#create-and-verify-a-campaign-creative).

**5. Launch the sandbox campaign**

Launching is a two-call operation: preview, then confirm with the returned
revision. See
[Launch a campaign with explicit confirmation](https://docs.apostra.com/v3/tool-reference.md#launch-a-campaign-with-explicit-confirmation).
Because the same company operates both the campaign and the storefront, your
explicit launch is also the storefront's approval of the buy. The buy then
goes to your inventory source.

The full buyer workflow is in
[Buyer workflows](https://docs.apostra.com/v2/setup/v3/buyer-workflows.md), and the seller-side limits are
in [Seller limitations](https://docs.apostra.com/v3/limitations.md#seller-limitations).

## Confirm that the check passed

Call `get_status`, or open the readiness checklist, and look at **Successful
transaction**. Readiness refreshes shortly after the buy is recorded, so give it
a moment before you read it again.

* **Complete.** The buy was accepted by its source and recorded with that
  source's media buy ID.
* **Still missing, no buy recorded.** The campaign did not launch or the buy did
  not reach the source. Read the campaign and its media buy, resolve the error
  it reports, and launch again.
* **Still missing for an external Agent.** The check names the Agent. Its proof
  comes from that Agent's own Test section, not from a sandbox campaign.

## Sources connected to a provider

What happens to the buy after it leaves your storefront depends on the source:

* **A modular source with no execution module that reaches a provider** (an
  avails feed, for example) has no outside system to send the campaign to.
  Apostra reserves the capacity and records the buy against your booking ledger.
* **A modular source connected to a provider's campaign system** is not sent the
  sandbox campaign. Apostra saves the buy in your account, shows it as a sandbox
  campaign waiting to start, and creates no campaign, reservation or task at the
  provider and no charge. The saved buy counts as the transaction the check
  looks for. It has no delivery or reporting, and you change it by cancelling it
  and creating a new one. See
  [Sandbox advertiser buys are not sent to the provider](https://docs.apostra.com/v2/storefront/inventory-sources/modular-lifecycle.md#sandbox-advertiser-buys-are-not-sent-to-the-provider).

If your storefront requires approval for buys, a sandbox buy is judged when it
is queued, so approving it later still records it without sending it.

Passing the check this way does not prove that your provider credentials can
create a campaign. To test that, use the provider's own sandbox or test account.

## Linked partner products

A sandbox advertiser's buy of a product your storefront takes from a linked
partner storefront is not sent to the partner's provider. Your storefront works
out on the server that the buy is a sandbox buy and tells the partner:

* **The partner's source reaches a provider.** The partner records the buy as a
  sandbox campaign waiting to start and sends nothing to the provider. The
  partner's sellers see the recorded campaign in their storefront; the provider
  sees nothing.
* **The partner connects through an adapter.** The buy is refused with
  `sandbox_buy_refused_for_adapter` and nothing is created at the platform.
  Pausing or cancelling an order the platform already holds still works.
* **The sandbox status cannot be confirmed.** Your storefront sends nothing to
  the partner and the buyer retries.
* **The partner's source is an external sales agent.** Not covered, the same as
  on your own storefront.

A live advertiser's buy of a linked partner's product is unchanged.

## What a sandbox campaign does and does not do

* It uses only your own storefront and your own sandbox advertiser. It cannot
  reach another company's storefront or use an advertiser that belongs to another
  account. Apostra admits a storefront that has not passed the check only for
  your own sandbox advertiser.
* It does not make your storefront live or discoverable to buyers by itself.
  Buyers connect once every blocker on the checklist is clear.
* Sandbox campaigns are not live campaigns. Running live campaigns against your
  own inventory is limited to the companies enrolled for it.

Related: [Sandbox mode](https://docs.apostra.com/v2/features/sandbox.md),
[Storefront overview](https://docs.apostra.com/v2/storefront/overview.md), and
[Demo Storefront](https://docs.apostra.com/v3/seller-demo-storefront.md).


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