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

# Landing Page Campaign

Trigger landing-page campaigns and render feedback or pushed products.

## Documentation

### Adding a Landing Page

Use `ff-campaign-landing-page` to display product campaigns independently of search requests. A common use case is a website's start page.

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

`ff-campaign-landing-page` triggers the FactFinder campaign that corresponds to the `page-id` attribute.

{% hint style="info" %}
The element itself **does not display anything**, nor does it take any child elements. It is merely a trigger that you place on pages where you want to display a landing page campaign.
{% endhint %}

The triggered campaign is visualized through the `ff-campaign-feedbacktext` and `ff-campaign-pushed-products` elements. To display landing page campaigns, they must be given the `is-landing-page-campaign` attribute.

```html
<ff-campaign-landing-page page-id="page-id-according-to-FF-config"></ff-campaign-landing-page>

<ff-campaign-feedbacktext is-landing-page-campaign label="your-label">
    {{{text}}}
</ff-campaign-feedbacktext>

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

For more information, see Campaign and Pushed Products.

## Demo

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

## API code

### Properties

<details>

<summary>Properties</summary>

| Name                                  | Description                                                                                                                  |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **page-id** (String) (default: empty) | Binds the campaign to a product campaign with the criterion **page-id** equals the defined pageID in the FactFinder backend. |

</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/landing-page-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.