> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/campaign-creation-and-editing/strategy/autobidding-spa.md).
# Autobidding (SPA)
Auto bidding is designed to **pace your campaign budget while optimizing bids to maximize sales revenue**. It considers your budget (daily limit or total campaign limit) and distributes spend across your campaign period, either until the campaign end date or month to month for always-on campaigns.
The system dynamically adjusts bids based on your campaign’s performance history to prioritize sales revenue while staying within the spend limits and max bid you’ve set.
{% hint style="info" %}
This feature is currently in beta with expansions planned through H1 2026, detailed below.
{% endhint %}
***
## **Why use autobidding?**
* **Conversion Focused:** Adjusts bids in real-time to maximize conversion likelihood.
* **Smarter, Predictive Bidding:** Learns from historical auction data to forecast performance and adapt to changing conditions.
* **Balanced Approach:** Avoids overspending on low-value opportunities while prioritizing auctions most likely to drive results.
* **Budget Pacing:** Ensures spend is distributed intelligently across the campaign duration.
***
## **How to set up autobidding?**
1. **Select to Automate Bids**
* In the strategy stage, enable auto bidding in your campaign settings. Once live, the system will algorithmically adjust bids in real-time.
2. **Set a Spend Limit**
* Define daily or total campaign spend limits. This controls pacing and allows the system to manage spend evenly.
3. **Set Your Max Bid**
* Specify the maximum CPC (Cost Per Click) you’re comfortable with. The system will never bid above your set maximum.
Take a guided walk-through below:
{% embed url="" %}
***
## **Important Notes**
* Autobidding is currently available only on
* Product Ad campaigns.
* Single-catalog campaigns.
* Single-product campaigns.
* Planned to expand to multiple products in Q1 2026.
* Retailers that don't offer first-price auctions.
* First-price auction support is planned for 2026.
* You'll only see the option to set a total spend when your campaign has an end date.
* For keyword-targeted campaigns, manual keyword bids are replaced by automated best-bid decisions. There's no need to set keyword-level bids.
* Performance can vary due to a variety of unrelated factors, such as:
* Products going out of stock
* Wallet budgets being exhausted
* Campaign rejections
## **FAQs**
#### **Do we need an end date for the campaign?**
No, if your campaign has no end date, you can still select autobidding. If you want to pace your spend, set a daily limit.
***
#### **What is the autobidder’s learning time?**
The autobidder is continuously learning. For new campaigns, you can expect the autobidder to learn over the first days and weeks before you see some normalization in performance as it begins to find the right balance. How long this takes depends on a variety of factors such as competition, impression volume, and budget throughput.
For existing campaigns, this is slightly accelerated as the autobidder begins learning with the guidance of historical performance.
***
#### **What about first-price auctions?**
Support is planned in **2026**.
***
#### **What about daily caps and wallet spends?**
The campaign stops serving ads when any budget limit is reached (wallet or campaign level).\
Types of limits:
* Campaign average daily limits
* Campaign total spend
* Wallet budgets
* Wallet daily limits
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.citrusad.com/retail-media-interface/campaign-creation-and-editing/strategy/autobidding-spa.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
