Connect Phonexa to your landing pages in LanderLab to send lead data directly to your Phonexa campaigns in real time. All you need is your Publisher API credentials from the Phonexa platform.
What is Phonexa?
Phonexa is an all-in-one performance marketing platform used by lead generators, publishers, and advertisers to manage lead distribution, call tracking, email marketing, and more. Its LMS Sync product handles lead posting, allowing publishers to send leads via HTTP POST to Phonexa campaigns in real time. When you connect Phonexa to your landing page in LanderLab, every lead collected is automatically posted to your Phonexa campaign using your Publisher API credentials. LanderLab handles the API connection for you, so you do not need to write custom code or build server-side integrations manually.Phonexa integrations are not saved globally. Each integration is configured per landing page, so you will need to set up a new Phonexa connection for each landing page where you want to send leads.
How to Add Phonexa
The Phonexa setup uses a 3-step wizard: configure the connection, map your fields, and review the final payload before connecting.Step 1: Configure the Connection
1
Go to your landing page
Navigate to Landing Pages and click the name of the landing page where you want to add the Phonexa integration.
2
Open the Integrations tab
Click Add Integration to open the integrations panel.
3
Select Phonexa integration
From the list of available integrations, find Phonexa integration (labeled as “Send leads to Phonexa in real time”) and click on it. The configuration wizard will open.
4
Fill in the connection details
Enter the following details:
5
Click Continue
Click Continue to move to the field mapping step.
Step 2: Map Your Fields
In this step, you choose which data fields to include in the request and how they should be named when sent to Phonexa.1
Select and configure fields
LanderLab automatically includes a set of default LanderLab fields. Each field has a checkbox to include or exclude it, and a Sent As column where you can rename the key to match what Phonexa expects.The default LanderLab fields are:
Use the checkboxes to enable or disable any field. Edit the Sent As value to match the field names in your Phonexa API specs.
2
Add custom fields (optional)
Under the Additional fields section, click + Add field to include extra key-value pairs in the request. This is useful for sending static values like sub IDs, traffic source identifiers, or any custom parameter your Phonexa campaign requires.
3
Click Continue
Click Continue to move to the review step.
Step 3: Review and Connect
1
Review your Phonexa integration
The final step shows a complete summary of what will be sent to Phonexa for every lead. You will see:
- The posting type and integration name
- The configuration section showing your API URL, API ID, and API Password
- The field mapping section listing all fields and their corresponding template variables (e.g.
{{LL Lander URL}},{{LL Visitor IP}})
2
Click Connect Phonexa
If everything looks correct, click the Connect Phonexa button to save and activate the integration.
Where to Find Your Phonexa API Credentials
If you are not sure where to find your API URL, API ID, and API Password, follow these steps:- Log in to your Phonexa account.
- Go to LMS Sync in the left sidebar.
- Click Publisher Products API.
- Select the product you want to connect to.
- In the Lead Specs section, you will find the posting URL (your API URL), API ID, and API Password.
Tips for Phonexa Integration
- Match field names exactly - Phonexa validates all incoming fields against your product’s API specs. Use the Sent As column in Step 2 to rename fields to match the field names in your Phonexa documentation exactly.
- Check required fields - Your Phonexa product’s API specs will clearly mark which fields are required. Leads that are missing required fields or contain values in the wrong format will be rejected.
- Use test mode during setup - Phonexa supports a test mode by adding
testMode=1to the payload. You can use the Additional fields section in Step 2 to add this as a static key-value pair while testing. Remove it before going live.