# Integrating Redirect Campaigns

If the campaign is a redirection campaign, the type is set to `REDIRECT` and the redirection field of the campaign is filled:

**JSON**: “`flavour`” and “`target`” within a `campaignsList` element.

A redirection consists of an optional name and a target URL. The URL is passed exactly as the user entered it (FactFinder does not perform any conversion on the URL).

When a redirection campaign triggers, the default reaction is that the current page automatically redirects to the specified URL. Other responses are also conceivable. For example, you could use redirection campaigns to provide shop visitors with links they can select. The name of the redirection can be used as the display text. The final decision on how to display the information is left to the shop operator in the integration project.

### REST-Interface

The technical documentation of the REST-API is contained in the search application itself and can be accessed via \[your NG server]/fact-finder/swagger-ui.html . It can be also accessed via the following URL:

Swagger Link: <https://ng-demo.fact-finder.de/fact-finder/swagger-ui.html>

Methods are documented under records. In addition to viewing the parameter documentation, you can also test a query and view the results. The documentation was created with Swagger, so you can use Swagger Codegen to generate a client to use in your code.

Please use the `campaign` method to retrieve campaigns.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fact-finder.com/integration/campaign-specific-integration/integrating-redirect-campaigns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
