> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/webcomponents-overview/web-components-4.x./api/more-features/pushed-products.md).

# Pushed Products

Display pushed campaign products using a nested record list.

## Documentation

### Adding a Pushed Products campaign

Add products to a search result page by nesting a valid `ff-record-list` inside `ff-campaign-pushed-products`. Refer to `ff-record-list` for product visualization options.

```html
<ff-campaign-pushed-products>
    <span id="productCampaignCaption">Product Campaign</span>
    <ff-record-list subscribe="false">
        <!-- In this demo, a click on the product sets the recommendation product. -->
        <ff-record>
            <img data-image="{{record.ImageName}}">
            <!--<img data-image>-->
            <div>
                <a href="https://www.bergfreunde.de/{{record.Deeplink}}" data-action="redirect">
                    {{record.Title}}
                </a>
                <div>Price: <strong>{{record.Price}} €</strong></div>
            </div>
        </ff-record>
    </ff-record-list>
</ff-campaign-pushed-products>
```

## Demo

Try the [Pushed Products demo](https://search-web-components.fact-finder.de/demos/4.x/ff-campaign-pushed-products).

## API code

### Properties

<details>

<summary>Properties</summary>

| Name                                    | Description                                                                                                                                                                                                                 |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **name** (String) (default: empty)      | Binds the campaign to a campaign name defined in the FactFinder backend.                                                                                                                                                    |
| **is-product-campaign** (Boolean)       | If this attribute is present, regardless of its value, the `ff-campaign-pushed-products` is only considered for product campaigns retrieved by [ff-campaign-product](file:///api/4.x/ff-campaign-product)                   |
| **is-shopping-cart-campaign** (Boolean) | If this attribute is present, regardless of its value, the `ff-campaign-pushed-products` is only considered for shopping cart campaigns retrieved by [ff-campaign-shopping-cart](file:///api/4.x/ff-campaign-shopping-cart) |
| **is-landing-page-campaign** (Boolean)  | If this attribute is present, regardless of its value, the `ff-campaign-pushed-products` is only considered for landing page campaigns retrieved by [ff-campaign-landing-page](file:///api/4.x/ff-campaign-landing-page)    |

</details>

### Adding a (Product) Pushed Product campaign

Add `is-product-campaign` to make `ff-campaign-pushed-products` respond to product detail campaigns.

```html
<ff-campaign-pushed-products is-product-campaign>
    <span id="productCampaignCaption">Product Campaign</span>
    <ff-record-list subscribe="false">
        <!-- In this demo, a click on the product sets the recommendation product. -->
        <ff-record>
            <img data-image="{{record.ImageName}}">
            <!--<img data-image>-->
            <div>
                <a href="https://www.bergfreunde.de/{{record.Deeplink}}" data-action="redirect">
                    {{record.Title}}
                </a>
                <div>Price: <strong>{{record.Price}} €</strong></div>
            </div>
        </ff-record>
    </ff-record-list>
</ff-campaign-pushed-products>
```


---

# 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://docs.fact-finder.com/webcomponents-overview/web-components-4.x./api/more-features/pushed-products.md?ask=<question>&goal=<user_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.