Overview
When you add a form from your marketing automation platform (MAP), such as Marketo, to your Knak landing page, you can choose between two styling options:
Custom Style
Knak Style
Each option affects how your form looks and behaves. Some features vary by MAP.
Custom Style vs. Knak Style
Custom Style
Uses the original form styling from your MAP
Keeps any custom Cascading Style Sheets (CSS) applied in your MAP
May include outdated or rigid code
May not adjust well on mobile devices
Limits your ability to edit styles in Knak
Knak Style
Removes most default MAP styling
Lets you control styling in the Knak builder sidebar
Uses cleaner, modern code
Improves mobile responsiveness
Gives you more flexibility
Troubleshoot Knak Style Rendering Issues (Marketo Only)
Likely Cause
Custom CSS from Marketo is interfering with Knak styling.
Check for Custom CSS
Open your form in Marketo
Go to Form Settings
Click Edit Custom CSS
Fix the Issue
Clone the form in Marketo
Remove custom CSS from the cloned version
Reconnect the cleaned form in Knak
Optional: Automatically Remove Custom CSS
Enable Strip Custom CSS from Marketo
This removes custom CSS automatically when using Knak Style
If the issue continues, contact support.
How Do You Position Labels?
Behavior (Supported MAPs: Marketo, Eloqua, Pardot)
Knak Style lets you control label placement.
Available Options
Above input fields
Left of input fields
Benefits of Labels Above
Improves readability
Prevents label text from wrapping
Supports responsive design
Keeps layout consistent across devices
Change Label Alignment
Select the form in the builder
Open the settings sidebar
Choose Label Alignment
Select Above or Left
Why Are Label Styles Not Working?
Likely Cause
You are using placeholder text instead of labels.
What This Means
Labels are empty in your MAP form
Placeholder text appears inside fields
Label styling does not apply
Why This Matters
Reduces accessibility
Screen readers cannot identify fields properly
Recommended Fix
Add labels in your MAP form
Use placeholder text as an example input only
Why Does Your Form Look Different From Another Landing Page?
Common Cause
Custom CSS or JavaScript exists on another landing page
That code does not transfer into Knak
Marketo-Specific Note
Marketo landing pages may include global styles or scripts
These do not carry over into Knak automatically
What You Can Do
Share the example page with your team
Recreate the styling using Knak controls
Visibility Rules
Recommendation
Disable visibility rules for simplicity
If You Use Them
Match picklist or field values exactly
Test all conditions to confirm correct display
Marketo-Specific Note
Visibility rules depend on exact value matching
Mismatched values may prevent fields from appearing
Platform-Specific Considerations
Marketo
Custom CSS can interfere with Knak Style
Supports Strip Custom Marketo CSS preference
Supports multi-column forms
Other MAPs
May not support multi-column layouts
Feature availability may vary
Some styling controls depend on platform capabilities
Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com