
Prerequisites
Before you start, make sure you have:- A LanderLab account with at least one published landing page
- A Klaviyo account
- A Klaviyo Public API Key (starts with
pk_)
Step 1: Get your Klaviyo API Key
- Log in to your Klaviyo account.
- Click your account name in the bottom-left corner, then go to Settings.
- Open the API Keys tab.
- Copy your Public API Key. It begins with
pk_.
Use the Public API Key, not the Private API Key. The field in LanderLab expects the
pk_ format.Step 2: Add Klaviyo to LanderLab
Step 3: Configure the integration
After saving your API key, a second configuration step opens.Step 4: Map your form fields
The field mapping step lets you control which data from your LanderLab form is sent to Klaviyo and which Klaviyo property it maps to. LanderLab shows all available fields on the left. For each field you want to send, use the dropdown on the right to select the matching Klaviyo field.You must map at least one field to continue. The Continue button stays disabled until at least one field mapping is set.
- LL Lander URL
- LL Visitor IP
- LL Visitor User Agent
- LL Submission Time UTC
- LL Variant ID
Step 5: Review and connect
The final step shows a summary of your integration configuration before anything goes live. Review the following:- List - The Klaviyo list leads will be added to
- Field Mapping - The fields being sent and how they map to Klaviyo properties
Troubleshooting
My Klaviyo lists are not loading
My Klaviyo lists are not loading
This usually means the API key was entered incorrectly. Make sure you are using the Public API Key (starts with
pk_), not the Private API Key. Go back to the integration settings, re-enter the key, and try again.Leads are not appearing in Klaviyo
Leads are not appearing in Klaviyo
Check that the integration is active on your landing page and that at least one field is mapped. Also confirm the correct Klaviyo list is selected and that it exists in your Klaviyo account.
The Continue button is disabled on the field mapping step
The Continue button is disabled on the field mapping step