> 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/api/more-features/pushed-products.md).

# Pushed Products

\`ff-campaign-pushed-products\` displays products returned by applicable campaigns. Nest an \`ff-record-list\` to control the product presentation.

## Documentation

Pushed products can be displayed by placing an `ff-record-list` inside an `ff-campaign-pushed-products` element.

The `ff-campaign-pushed-products` element scans **search results** for applicable campaigns and populates the nested `ff-record-list`.

For more information on how to customize the product visualization, refer to [ff-record-list](/webcomponents-overview/api/basic-elements/record-list.md).

```html
<ff-campaign-pushed-products>
    <!-- Optional additional HTML. -->
    <span class="productCampaignCaption">Product Campaign</span>

    <!-- Set `subscribe` to false as this record list will not be listening to search requests directly. -->
    <ff-record-list subscribe="false">
        <template data-role="record">
            <ff-record>
                <img data-image="{{variantValues.0.ImageName}}">
                <div>
                    <a href="https://www.your.shop/{{variantValues.0.Deeplink}}">
                        {{variantValues.0.Title}}
                    </a>
                    <div>Price: <strong>{{$ variantValues.0.Price}}</strong></div>
                </div>
            </ff-record>
        </template>
    </ff-record-list>
</ff-campaign-pushed-products>
```

## Display results from stand-alone campaign triggers

By default, `ff-campaign-pushed-products` only displays campaigns that are part of a **search result**.

However, you can trigger campaigns independently of searches. These are *landing page*, *product*, and *shopping cart* campaigns.

To display these campaigns, add the corresponding attribute. The element will then respond only to the specified trigger and no longer react to search results.

| Attribute                   | Triggered by element        |
| --------------------------- | --------------------------- |
| `is-landing-page-campaign`  | `ff-campaign-landing-page`  |
| `is-product-campaign`       | `ff-campaign-product`       |
| `is-shopping-cart-campaign` | `ff-campaign-shopping-cart` |

{% hint style="warning" %}
Only one attribute at a time is allowed.
{% endhint %}

```html
<ff-campaign-pushed-products is-landing-page-campaign>
    <ff-record-list subscribe="false">
        <template data-role="record">
            <ff-record>...</ff-record>
        </template>
    </ff-record-list>
</ff-campaign-pushed-products>

<ff-campaign-landing-page page-id="home"></ff-campaign-landing-page>
```

## API

### `ff-campaign-pushed-products`

#### Properties

| Name                                    | Description                                                                                                                               |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **name** (String) (default: empty)      | Binds the campaign to a campaign name defined in the FactFinder UI.                                                                       |
| **is-landing-page-campaign** (Boolean)  | Displays only landing-page campaigns from [Landing Page Campaign](/webcomponents-overview/api/more-features/landing-page-campaign.md).    |
| **is-product-campaign** (Boolean)       | Displays only product campaigns from [Product Campaign](/webcomponents-overview/api/more-features/product-campaign.md).                   |
| **is-shopping-cart-campaign** (Boolean) | Displays only shopping-cart campaigns from [Shopping Cart Campaign](/webcomponents-overview/api/more-features/shopping-cart-campaign.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 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/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.