> For the complete documentation index, see [llms.txt](https://docs.pubstack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pubstack.io/spark/spark-demand.md).

# Spark demand

Spark Demand is Pubstack's server-side demand solution.

It allows you to add Spark as an additional bidder to your existing monetization setup and expose selected inventory to demand managed through Pubstack's server-side infrastructure.

Spark Demand is available with both **Monetization Manager ONE** and **Monetization Manager NODE**.

It complements your existing bidder setup rather than replacing it.

***

### How Spark Demand works

Spark is configured as a prebid **server-side bidder** within Pubstack.

Once enabled, Spark participates in eligible auctions alongside the other bidders configured in your monetization stack.

The general setup consists of:

1. Making Spark available in your bidder seats.
2. Selecting the inventory that Spark is allowed to monetize.
3. Adding Spark to the relevant Bidder rules.
4. Deploying the updated configuration.
5. Monitoring Spark performance from the server-side analytics.

Spark configuration is managed directly from the Pubstack platform.

***

### Supported media types

Spark Demand can be used for supported server-side inventory including:

* **Banner**
* **Video**
* **Native**

The available media types are displayed directly on the Spark bidder seat.

***

### Where Spark Demand is configured

Spark Demand relies on several parts of Monetization Manager:

#### Integration catalog

Use the **Integration Catalog** to access Spark and add the Spark bidder seat when it is available for your account.

#### My bidder seats

Use **My bidder seats** to manage the Spark integration and define which inventory is enabled.

Spark appears under the **Server-side** tab.

#### Bidder rules

Spark must also be included in the relevant **Bidder rules** for it to participate in auctions.

#### Deployment

Configuration changes are not automatically deployed to your inventory.

After updating Spark mapping or Bidder rules, synchronize and deploy the affected media when required.

[\[Learn more about Spark Configuration\]](/spark/spark-demand/getting-started-with-spark-demand.md)

***

### Inventory activation

Spark inventory activation is managed from the Spark bidder seat.

For each media, you can define which ad units should be monetized through Spark.

An enabled value activates Spark for the corresponding inventory.

An empty value disables Spark for that inventory.

This lets you progressively control the inventory exposed to Spark instead of activating it globally.

***

### Ad Quality controls

Spark Demand can also benefit from Pubstack's **Ad Quality controls**.

These controls are available from:

**Settings → Spark ad quality**

They allow you to define blocking rules based on:

* **IAB advertising categories**
* **Advertiser domains**

The configured restrictions are transmitted to monetization partners as part of the bid request.

> Category blocking depends on each monetization partner's ability to interpret and enforce the information provided by Pubstack.

Ad Quality controls operate at Pubstack proxy level and may therefore also apply to other compatible server-side traffic.

[\[Learn more about Server Ad Quality\]](/settings/server-ad-quality.md)

***

### Performance monitoring

Spark Demand activity is available in Pubstack's **Server-side analytics**.

You can use these dashboards to monitor Spark alongside your other server-side demand partners and measure its contribution to your monetization.

[\[Learn more about Server-side analytics\]](/analytics/dashboards/server-side.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pubstack.io/spark/spark-demand.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.