---
updatedAt: 2025-12-31T08:38:43.000Z
agentTools:
projectIndex: https://docs.clevertap.com/llms.txt
---
# Swipe Pages
Customer Relationship Management
# Overview
[Swipe Pages](https://swipepages.com/) is a no-code landing page builder that helps create high-converting, mobile-optimized pages using a drag-and-drop interface. You can integrate Swipe Pages with CleverTap using Zapier to capture lead data from landing page forms and create or update user profiles in CleverTap.
With the CleverTap and Swipe Pages integration, you can:
* Automatically create or update user profiles in CleverTap from Swipe Pages form submissions.
* Trigger welcome emails or onboarding campaigns when a user signs up.
* Add users to specific journeys, such as event reminders or product interest flows.
* Segment users based on form inputs (for example, topic of interest) and send personalized follow-ups.
# Prerequisites for Integration
The following are the prerequisites for integrating Swipe Pages with CleverTap via Zapier:
* A Swipe Pages account with access to create landing pages and generate API keys.
* An active Zapier account.
* A CleverTap account with **Account ID** and **Passcode**.
# Integrate Swipe Pages with CleverTap
The integration process involves the following three major steps:
1. [Create Passcode on CleverTap Dashboard](https://docs.clevertap.com/docs/swipe-pages#create-passcode-on-clevertap-dashboard)
2. [Create Landing Page in Swipe Pages](https://docs.clevertap.com/docs/swipe-pages#create-landing-page-in-swipe-pages)
3. [Configure Zapier in Swipe Pages](https://docs.clevertap.com/docs/swipe-pages#configure-zapier-in-swipe-pages)
## Create Passcode on CleverTap Dashboard
CleverTap uses a header-based authentication model to authenticate requests to the API. Every CleverTap API request must include the Account ID and Passcode as the request headers. To create a passcode, refer to [Create Account Passcode](https://developer.clevertap.com/docs/authentication#create-account-passcode).
## Create Landing Page in Swipe Pages
To create a landing page in Swipe Pages where form submissions will be collected. To do so, perform the following steps:
1. Log in to your [Swipe Pages](https://app.swipepages.com/signup) dashboard.
2. Go to *Integrations* > *Landing Pages* from the left panel.
3. Click **Create New Page** to create your landing pages. Refer to [Creating a new landing page in Swipe Pages](https://docs.swipepages.com/en/articles/4761649-creating-a-new-landing-page).
## Configure Zapier in Swipe Pages
Zapier acts as the automation bridge between Swipe Pages and CleverTap. To enable this connection, you must configure Zapier within Swipe Pages. To do so, perform the following steps:
1. Go to *Integrations* from the left panel on the Swipe Page dashboard
2. Click on **Zapier** and click **Create a New Zap**.
3. To create the connection, you will be provided with a Swipe Pages API key here.
4. Copy it and keep it safe.
Now that Zapier is configured in Swipe Pages, proceed further to set up the Zapier workflow with [Swipe Pages as the trigger](https://docs.clevertap.com/docs/swipe-pages#set-up-swipe-pages-trigger) and [CleverTap as the action](https://docs.clevertap.com/docs/swipe-pages#set-up-clevertap-action).
### Set Up Swipe Pages Trigger
A trigger determines when your Zap will run. In this case, the trigger is a form submission on your Swipe Pages landing page. To set up swipe pages as a trigger, perform the following steps:
1. Set the **Trigger App** as *Swipe Pages*.
2. Select the *Trigger Event*. In this case, select *New Form Submission* from the dropdown. This ensures the Zap is triggered every time a user submits a form on your Swipe Pages.
3. Connect your Swipe Pages account using the previously generated **API Key** from *step 4* of [Configure Zapier in Swipe Pages](https://docs.clevertap.com/docs/swipe-pages#configure-zapier-in-swipe-pages).
4. Select the specific form whose submissions you want to capture.
#### Note
Submit a test form on Swipe Pages to fetch sample data during setup.
### Set Up CleverTap Action
Once the trigger is defined, you need to configure what happens in CleverTap. This is done by setting up an action in Zapier. To set up CleverTap as an action, perform the following steps:
1. From the *Action App*, select *CleverTap*.
2. Select one of the following **Action Events**:
* *Create/Update User Profile*
* *Upload Event*
3. Connect your CleverTap account by entering **Account ID**, **Passcode**, and **Region** of your CleverTap account. For detailed steps, refer to [Create a Passcode on the CleverTap Dashboard](https://docs.clevertap.com/docs/swipe-page#create-passcode-on-clevertap-dashboard).
4. Map Swipe Pages data to CleverTap fields:
| **CleverTap Field** | **Description** |
| -------------------- | ------------------------------------------------------------------- |
| Identity / Object ID | Unique identifier (email, phone, or internal user ID) |
| Creation Date | (Optional) Timestamp of form submission |
| Profile Properties | JSON object of additional attributes (for example, `name`, `email`) |
| Event Name | (If uploading event) for example, `submitted_landing_form` |
| Event Properties | JSON of contextual details (for example, `page`, `campaign`) |
#### Map Identity and Object ID
You can keep the Identity field blank if you provide an Object ID, and vice versa.
5. Click **Test & Review** to validate the setup.
6. Check your CleverTap dashboard for the test event.
7. Click **Publish** to activate the Zap.
# Verify Integration Results
After publishing the Zap:
* If you selected *Upload Event*, CleverTap logs a new event each time a form is submitted on your Swipe Pages site. Events appear in the *Events* section of the CleverTap dashboard.
* If you selected *Upload/Update User Profile*, CleverTap uses the `Identity` field to determine whether to create or update a user profile.
This automation enables you to seamlessly capture form data into CleverTap, allowing for personalized engagement without manual intervention on the CleverTap dashboard.
# FAQs
### What happens if I do not map the required fields?
Not mapping required fields may result in incomplete data being transferred or failure to update user profiles and events correctly.