> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/perspective.md).
# Perspective
Set up the Perspective connector in Pandium using JWT token and campaign ID so tenants can authenticate securely and sync funnel data, lead information, and conversion metrics.
## **Connector Overview**
Perspective is a mobile-first funnel builder platform that helps businesses create interactive lead generation and sales funnels with high conversion rates, offering tools for building landing pages, collecting leads, and managing customer journeys.
## **Authentication Type**
Basic
## **Webhook Supported**
Yes
## **Secrets**
* PAN\_SEC\_PERSPECTIVE\_CAMPAIGN\_ID
* PAN\_SEC\_PERSPECTIVE\_JWT\_TOKEN
* PAN\_SEC\_PERSPECTIVE\_WEBHOOK\_EVENTS
## **API Client Supported**
No
## **Requirements for Provisioning**
In order to provision your connector, the following Perspective information must be gathered:
* Webhook Events
## **How to Connect Your Integration**
Upon successfully creating a tenant, you will use the following Perspective information to connect:
* JWT Token
* Campaign ID
## **API Resources**
For more information on how to utilize the Perspective API, feel free to reference the following documentation.
---
# 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.pandium.com/connectors/connectors-101/perspective.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.
