> 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/integration/campaign-specific-integration/integrating-redirect-campaigns.md). # Integrating Redirect Campaigns Handle redirect campaigns by sending visitors to the right URL or showing alternative links. If the campaign is a redirection campaign, the type is set to `REDIRECT` and the redirection field is populated: **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 behavior is to redirect the current page automatically to the specified URL. Other responses are possible too. For example, you can use redirection campaigns to show selectable links instead. In that case, use the redirection name as the display text. The final display behavior is defined during the integration project. ### REST interface The REST API documentation is part of the search application and is available at \[your NG server]/fact-finder/swagger-ui.html. You can also access it here: Swagger Link: The relevant methods are documented under `records`. In addition to the parameter documentation, you can test requests and inspect the results directly. Because the documentation is built with Swagger, you can also use Swagger Codegen to generate a client. Please use the `campaign` method to retrieve campaigns. --- # 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/integration/campaign-specific-integration/integrating-redirect-campaigns.md?ask=&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.