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

# The seller-history co-op

> What a buyer account shares and gets by joining the seller-history co-op, the data co-op of Section 6.3 of the Terms of Service, how the pooled figures are protected, and how leaving works.

A seller's record shows how often it kept the commitments it made on goals. On
your own buys, you always see your own record with a seller. The
**seller-history co-op** adds something you cannot get alone: other buyers'
results with that seller, pooled.

It is how a buyer account takes part in the **data co-op** in Section 6.3 of the
Terms of Service. Under the Terms, participants opt in at the account level and
contribute performance data to a shared pool, in exchange for enhanced matching,
pricing signals and optimization recommendations derived from that pool. The
Terms say the specific co-op features, participation mechanics and eligibility
are published on the Platform, and that the Terms govern participation. This
page is that publication. Joining is the account's choice, and it starts off.

For what a record cell holds and how a buy is judged, see
[The seller's record](https://docs.apostra.com/v2/concepts/goal-seeking-campaigns.md#the-sellers-record).

## In short

* Joining is how this account takes part in the data co-op of Section 6.3 of the Terms of Service. It shares the judged results of this account's completed buys, only as aggregates that never name a buyer, campaign or media buy, and never what a seller charged. In return the account gets other members' pooled seller history and automatic selection that ranks sellers with it. Not joining does not affect access to standard Platform features, and a non-member's data is not contributed. Pooled reading and ranking open only when the pilot read is enabled for the account.
* Leaving takes effect from the day you leave, as Section 6.3 of the Terms of Service says. The account stops reading pooled history, and buys that complete after it leaves are not shared. Results it shared while a member stay in the pool and are not removed. Leaving does not affect access to standard Platform features.

## What the Terms promise, and what is available today

| Section 6.3 of the Terms | Available today |
| - | - |
| Contributing performance data to a shared pool | The judged results of the account's completed buys, as aggregates. See [What a member shares](#what-a-member-shares). |
| Enhanced matching | Other members' pooled history of a seller, and automatic selection that ranks sellers with it. See [What a member gets](#what-a-member-gets). |
| Optimization recommendations | Not available yet. |
| Pricing signals | Not available yet. When offered, they are wholesale product avails: that a given product in a given country never delivers below a given price, so no client has to rediscover it. Seller history never pools what a seller charged a buyer. |

## Participation and eligibility

Participation is set per buyer account. The administrators of a buyer account
decide whether the account joins, and an account that never joined is not a
member. Any buyer account may join. Buys from an account with no confirmed
operator identity are not counted, because the co-op counts buys by operator, so
the web app asks for the identity before the account joins.

| To do this | Use |
| - | - |
| Join or leave | `save_buyer_operator` on `/mcp/v3` with `sellerHistoryCoop: true` or `false`, or `PATCH /api/v2/buyer/readiness/operator` with the same field |
| Read whether the account is a member | `identity.sellerHistoryCoop` from `GET /api/v2/buyer/readiness`, which every buyer account can read, or `operatorIdentity.sellerHistoryCoop` from `get_status`, which is present only once pooled reading is open for the account and absent for every other account |

In the web app, the setting is under **Settings → Seller-history co-op** once
pooled reading is open for the account. Administrators join or leave there, and
other members of the account see whether it is a member. Leaving asks you to
confirm first.

The setting sits with the account's operator identity because the operator
that owns the account decides. Changing it takes the same administrator
permission as the operator identity. The field is sent with the identity, so
to change only the co-op setting, send the saved identity again unchanged. On
`/mcp/v3`, a change goes through the preview and confirmation that identity
changes use: preview first, show the person what a member shares and gets, and
confirm with the token the preview returns.

### Being asked during setup

Once pooled reading is open for the account, an administrator is asked once
whether the account joins. the Apostra assistant asks during buyer setup, and any agent on
`/mcp/v3` sees the same question as the `seller_history_coop` next action in
`get_status`. Saying no saves `sellerHistoryCoop: false`. It needs no preview,
because a "no" shares nothing, and the account stays out of the co-op. Joining, leaving or saying no is the account's answer, and the
question is not asked again after any of them. An administrator can still join
or leave later.

## What a member shares

A member shares the judged results of its completed buys, and only as
aggregates. A pooled figure never names a buyer, a campaign or a media buy, and
never says how many buyers or operators stand behind it.

* **Which buys count.** Completed buys that carry a goal commitment and were
  judged, as described in
  [Judging delivery](https://docs.apostra.com/v2/concepts/goal-seeking-campaigns.md#judging-delivery).
  Sandbox buys do not count, and neither do buys last delivered more than 180
  days ago.
* **Kinds follow the seller's pricing.** A buy's commitment kind is `guaranteed`
  when the seller fixed a price on the outcome the buyer asked for, whatever the
  product's delivery type, and `best_effort` or `report_only` as described in
  [what a seller can promise](https://docs.apostra.com/v2/concepts/goal-seeking-campaigns.md#what-a-seller-can-promise).
  Buys booked under the earlier reading are restated in a one-time pass after
  this change ships, so until it has run an older buy can keep its earlier kind;
  afterwards an older event-goal answer that also carries seller optimisation
  goals still keeps its earlier label, because the stored answer does not show
  which event the price covered. A snapshot already published is never
  rewritten, so figures published before the restatement keep their old kinds
  until the next snapshot replaces them.
* **Price is never shared.** The co-op pools delivery, performance and quality.
  What a seller charged you stays with you.
* **The operator behind the account counts, not the account.** The co-op
  counts operators by the operator domain an account confirmed. A buy from an
  account with no confirmed operator identity is left out, so confirm your
  [operator identity](https://docs.apostra.com/v3/buyer-setup.md) first.

## What a member gets

A member reads other members' pooled history of a seller, as the seller's
record, in place of its own record. It is the same kind of figure: one per
goal objective and commitment kind for each seller.

* **A figure is shown only with enough behind it.** At least 3 distinct
  operators and 5 judged buys must stand behind it, and no single operator may
  supply more than half of the judged buys. A figure that fails either is not
  shown. Without these limits, a member could work out another member's
  results from a thin figure.
* **Nothing exact is shown, and smaller records show less.** A record built
  from fewer than 40 judged buys is small. It shows a size band
  (`size: "under_40_judged"`) and a hit rate and median distance from target
  rounded to the nearest 0.25, which is quarters. It shows no number of buys,
  no number judged and no split into beat, met and missed: with so few buys,
  one buy can move a rounded share by a whole step, so a split could be worked
  back into individual results. Several different results round to the same
  quarter, so the quarter cannot be worked back into one. A record built from 40
  or more judged buys (`size: "40_or_more_judged"`) shows the rounded split. The
  number of buys and the number judged are rounded to the nearest 5. The share
  of judged buys that beat, met or missed their target (`beatShare`,
  `metShare`, `missedShare`) is given in steps of 0.05, which is 5 percentage
  points, and the three always add up to exactly 1: each share takes the step
  at or below it, and any step left over goes to the shares closest to the next
  step up. The hit rate is rounded to the nearest 0.05, and the median distance from target is rounded
  to the nearest 0.05, which is 5 percent of the target. At 40 judged buys one
  buy moves a share by 2.5 points at most, which is less than half of that
  rounding step, so no single buy can be read out of a figure.
* **It is a snapshot, not a live figure.** Pooled history is published on a
  fixed schedule, monthly to start. A live figure leaks through subtraction: if
  you read a pooled hit rate before and after one other buyer's buy completes,
  you could recover that buy's result. A published value changes only when at
  least 5 judged buys from at least 3 distinct operators have been added since
  it was published. Otherwise the previous value stands.
* **Automatic selection uses it too.** For a member with pooled reading open,
  automatic product selection ranks sellers with the published snapshot. For
  anyone else it ranks with the account's own completed buys with each seller.

## Leaving

Opting out is effective from the day you leave, and what the account shared
before then is not removed, as Section 6.3 of the Terms of Service provides.
Leaving does not affect access to standard Platform features.

* **The account stops reading pooled history at once.**
* **Nothing new is shared.** A buy counts as shared while the account was a
  member when it was already completed on the day the account left. A buy that
  completes after the leave is not shared. If the account rejoins, its
  completed buys count again, including ones that completed while it was out.
* **What it shared stays.** Buys shared while a member keep counting toward
  published figures under the same rules as every other buy: the 180-day
  window, the minimum of 3 operators and 5 judged buys, and the one-operator
  limit. A published figure does not change because a member left.

Leaving does not delete your own record with a seller. You keep reading that.

## If you are not a member

A non-member's data is not contributed, and its access to standard Platform
features is the same. You read your own record with a seller: only your own
completed buys, judged the same way. They are your own buys, so the counts are exact and no minimum
applies. You do not read any other buyer's results, and no other buyer's
results change how automatic selection ranks sellers for you.

## What a seller sees

A seller reads its own record across all its buyers, as before. That record is
built from evidence the seller holds or was sent, so no buyer's consent is
involved. A seller never sees which buyers are members.

> [!NOTE]
>
> **Pilot.** Reading pooled history is in a pilot, and the pilot widens after
> sellers have been told what buyers see. Until pooled reading is open for your
> account, joining only means your own completed buys will count toward the
> pool once it opens. You do not read pooled history yet: automatic selection
> ranks with your own buys, and an account outside the pilot that asks for
> `include: ["commitmentRecord"]` is refused with `FEATURE_NOT_ENABLED`.

## Not part of the co-op

Section 6.2 of the Terms is separate from the co-op. It lets Apostra use
aggregated and anonymized signals from activity on Apostra to improve the
Platform for all participants, such as vertical and market benchmarks, and
no individual participant's data is identifiable in those uses. That use does
not depend on membership. The market benchmarks that product scoring uses for
cost per action, cost per click, click-through and conversion rates by
objective, country and channel are one such signal: a market-wide computation
that names no seller, buyer or buy.


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