> 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/product-campaign.md).

# Product Campaign

Trigger product-detail campaigns and render feedback or pushed products.

## Documentation

### Adding a Product Campaign

Use `ff-campaign-product` to display product campaigns on a product detail page. Add the element and set `product-id` to the FactFinder field configured with the **Product number (campaign)** role.

Check **Field summary** in FactFinder backend when you are unsure which field applies. Usually, set this attribute dynamically with JavaScript whenever the viewed product changes.

```html
<ff-campaign-product record-id="12345"></ff-campaign-product>
```

The element triggers a campaign but does not render content. Depending on the configured campaign, add `ff-campaign-feedbacktext` with `is-product-campaign` for feedback text or `ff-campaign-pushed-products` with `is-product-campaign` for pushed products.

See [Campaign](/webcomponents-overview/web-components-4.x./api/more-features/campaign.md) and [Pushed Products](/webcomponents-overview/web-components-4.x./api/more-features/pushed-products.md) for the associated components.

```html
<ff-campaign-feedbacktext is-product-campaign label="your-label">
    {{{text}}}
</ff-campaign-feedbacktext>

<ff-campaign-pushed-products is-product-campaign>
    <ff-record-list subscribe="false">
        <ff-record>...</ff-record>
    </ff-record-list>
</ff-campaign-pushed-products>
```

## Demo

Try the [Product Campaign demo](https://search-web-components.fact-finder.de/demos/4.x/ff-campaign-product).

## API code

### Properties

<details>

<summary>Properties</summary>

| Name                                                                               | Description                                                                                                                               |
| ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **record-id** (Number) (default: empty)                                            | When the **record-id** attribute is set, an AJAX request is made to retrieve all product campaigns for the given product ID.              |
| **id-type** (String) **Options**: "id", "productNumber" (default: "productNumber") | This attribute is only relevant when you are integrating against FactFinder NG API `v4` and later. It determines the type of `record-id`. |

</details>


---

# 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/product-campaign.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.