Forms sit at the very heart of any marketing automation strategy.
Yet in many platforms, they remain a constant compromise between functional limitations, custom scripts, and CSS workarounds that quickly become hard to maintain.
With Paminga, I rediscovered something that has become quite rare:
👉 forms that are both very easy to use and genuinely powerful, without relying on custom code or fragile technical setups.
In this second Paminga Tip, I will walk you through Paminga forms from a very practical, hands-on perspective.
Clear access to forms… and even clearer access to submissions
Forms are available in the Marketing Center, where you immediately find:
- the list of all existing forms
- the full history of form submissions
Each submission displays:
- the submission date
- the completion status
- direct access to the contact record
On each contact profile, a dedicated tab shows all forms filled over time, which is extremely valuable to understand the real conversion journey.
Another key point worth highlighting:
👉 UTM parameters are captured natively, with no specific configuration required, and are associated with:
- the form submission
- the website visit
You also get access to page and session duration, providing a much deeper level of insight into engagement.
Native multi-page forms, without code
One of the first features that stands out:
👉 multi-page forms are native in Paminga.
You can:
- create as many pages as needed
- start from a template or from scratch
- add rows and define the number of columns per row
Each column can then host the desired fields.
This approach makes it easy to design longer, more structured forms while keeping a smooth user experience.
Partial submissions can also be recorded, which is especially useful for complex forms.
Native multilingual forms, done right
Another major strength: multilingual support is fully native.
A single form can handle multiple languages.
Paminga allows you to translate:
- texts
- labels
- fields
- placeholders
- error messages
- steps (steppers)
When embedding the form on your website, you can:
- let Paminga automatically adapt to the browser language
- or force a specific language via a simple embed variable
Result:
👉 one form, multiple languages, no duplication, no maintenance overhead.
One consistent editor across the entire platform
The form builder relies on a very clear hierarchy:
- container
- sections
- rows
- elements (fields, text, buttons…)
This structure is exactly the same for:
- forms
- landing pages
- emails
Once you understand the editor, you can design everything consistently across the platform.
Each element can be:
- moved via drag & drop
- edited precisely
- cloned
- saved into a template library for reuse
Brand Kits and fine-grained design control
Brand Kits allow you to apply a complete visual identity:
- colors
- styles
- light and dark variations
You can then deviate from the Brand Kit if needed.
You can also choose to let the website handle the CSS, or fully control styling directly within Paminga.
At every level (container, section, row, element), you have access to:
- width
- margins
- padding
- backgrounds
- borders
- border radius
Display conditions at every level
This is where Paminga clearly differentiates itself.
Display conditions can be applied to:
- fields
- rows
- entire sections
Conditions can be based on:
- form field values
- database fields (when the contact is recognized)
- UTM parameters
- device
- overall context
For example:
- show a “State” field only if the country is “United States”
- display a GDPR-related section only if the preference center has not been completed
This enables true dynamic form experiences, far beyond simple field-level show/hide logic.
Native progressive profiling and prefill
Paminga provides:
- progressive profiling
- cookie-based prefill
These features work natively on your website, not only on hosted landing pages.
A few important notes:
- progressive profiling applies to single-page forms
- you simply define how many empty fields are displayed on each visit
No external scripts are required.
A very comprehensive set of field types
Paminga forms cover all modern needs:
- standard fields (text, email, phone…)
- checkboxes
- date / datetime
- confirmation fields
- multi-select
- yes / no
- ratings
- subscription management blocks
- native captcha
- native file upload with drag & drop
Picklists can be defined directly in the database and are automatically available when adding a field, with multilingual support if needed.
Extremely rich post-submission logic and actions
After form submission, Paminga offers very granular control over the experience.
Possible outcomes
- fully customizable thank-you message
- redirection to a URL
- conditional outcomes based on context (e.g. subscription status)
Available actions
- send an autoresponder email
- add or remove from lists
- manage subscription lists
- update field values
- update scoring
- set lead stage
- send internal notifications (Slack, for example)
- sync with Salesforce
- create an opportunity
- trigger a webhook or Zap
- push events to the data layer (Google Tag Manager)
- sunset or unsunset contacts
- register and check in contacts for events
Actions can be:
- unconditional
- or conditional
👉 And most importantly, they are directly attached to the form, without necessarily relying on external workflows.
My field perspective
After designing and maintaining many forms across different platforms and contexts, my conclusion is straightforward:
Paminga forms are among the most complete I have worked with in a long time, while remaining readable, consistent, and fast to deploy.
You can clearly feel:
- a product designed by people who understand real-life marketing constraints
- a platform that evolves quickly
- a strong focus on aligning marketing, data, and user experience
I already have a few ideas for future improvements…
and given the pace at which Paminga is evolving, I am confident we will see them soon.
👉 See you very soon for the next Paminga Tip.
Discover our other Paminga Tips
