Marketing automation is a mature market. So are the promises.

What makes the difference today is not an additional AI feature, but the ability to execute quickly, cleanly, and measure your actions with confidence.

In this first demo, I'll give you a guided tour of Paminga, a recent marketing automation solution built on modern architecture and designed to be both powerful and easy to use.

Webinar outline

• 00:00 Introduction

• 01:24 CRM synchronization

• 09:21 Database management

• 13:00 Web tracking

• 16:06 Pop-up on web page

• 23:16 Sending to a Drip Series

• 26:40 Paminga forms

• 32:33 Paminga landing page

• 35:51 Paminga email

• 38:40 Email sending workflow

• 40:00 Scoring & Lead Life Cycle

• 45:25 Conclusion

Why I'm interested in Paminga (after 14 years with Marketo)

My name is Sylvain Davril, founder of Merlin/Leonard.
I was a Marketo partner for 14 years and have been a Paminga partner for several months now.

Why did I make this choice?
Because some customers are now looking for a modern alternative, and because I wanted to test the solution for myself: I am currently migrating our internal use of Marketo to Paminga.

This webinar is the first in a monthly series.
The goal is to start with the basics and then gradually move on to more advanced campaigns.

What this first demo covers

We start with the fundamentals, which determine everything else:

• CRM synchronization (with a focus on Salesforce, and a similar logic for Microsoft Dynamics)

• Database management (fields, value lists, custom objects)

• Tracking (page views with time spent, UTM, downloads, videos)

Next, we build an initial "Always On" campaign:

• A pop-up (call-to-action) on a website page

• a form

• a landing page

• a nurturing workflow

• and, if time allows: scoring and the lead lifecycle

1. CRM synchronization: an approach that is finally clear and manageable

Salesforce synchronization in Paminga is based on an interesting approach:
Paminga retrieves the Salesforce data model and allows you to decide, field by field:

• which fields should be synchronized

• in which direction (read-only or write-enabled)

• which actions should be triggered when a lead or contact arrives

Creating fields on the fly

One very useful feature in the demo: if a field exists in Salesforce but not yet in Paminga, it can be created directly from the interface, without any complex manipulation.

When it comes to a list value field, Paminga automatically detects it and prompts you to configure a clean mapping, thus avoiding data inconsistencies.

Explicit error handling

Another key point in the project: synchronization errors are clearly explained.
The demo shows a concrete example: a Lead Status value in French in Salesforce does not match the English value configured in Paminga. The error is immediately identifiable and correctable.

CRM actions from workflows

From a Paminga workflow, it is possible to:

• create or update leads and contacts

• create tasks

• add people to Salesforce campaigns with the correct statuses

• and, depending on the case, create opportunities

CRM synchronization is therefore designed as a central foundation, not as a simple peripheral integration.

2. Database: maintaining a clean and scalable model

Paminga offers all the fundamentals expected for database management:

• creation and management of fields (types, dropdowns, multi-select, etc.)

• structured management of value lists

• ability to rename and even delete fields that are no longer needed

This ability to clean up is far from insignificant when you want to maintain a database that remains readable over time.

Custom Objects

Paminga also allows you to create Custom Objects, with relationship management, including many-to-many relationships.

The goal is to be able to integrate business objects (contracts, projects, assets, subscriptions, etc.) into Paminga, whether they come from CRM or a data warehouse, and then use them in segmentations and workflows.

3. Tracking: an often underestimated foundation

Tracking is often the weak point of many platforms.

With Paminga, installing a tracker on the site allows you to natively collect:

• page views with time spent

• UTMs, automatically captured and associated with each visit

• PDF downloads, considered as actionable events

• native video tracking (YouTube, Vimeo, Wistia, Vidyard, etc.), with playback milestones at 25%, 50%, 75%, and 100%

These signals can then be used to segment, score, and trigger marketing actions without any heavy integration.

CRM visibility

Engagement data can also be displayed in Salesforce, giving sales teams a clear view of marketing interactions.

4. An "Always On" campaign: from pop-ups to nurturing

The demo continues with the implementation of a very concrete "Always On" campaign.

Objective: trigger a pop-up on a content page, collect an email address, then enroll the person in a nurturing program.

CTA and unified editor

CTAs (pop-ups, inline, scroll, etc.) are created in an editor that is common to all assets: forms, emails, and landing pages use the same editing logic.
This significantly reduces the learning curve and improves campaign consistency.

Native conditional content
A key feature is the ability to make any element conditional (section, line, component) without scripting.

For users accustomed to older solutions, this eliminates the need for specific languages and greatly simplifies customization.

Forms and nurturing

Paminga forms allow you to:

• Progressive profiling

• Multi-page forms

• Define post-submission actions (workflow, Slack, webhook, GTM, etc.)

• multilingual management

The nurturing presented is based on a simple and clear logic, with emails spaced out over time and the possibility of defining success objectives.

5. Scoring and lead lifecycle: a solid foundation, still evolving

Paminga offers several scores (profile, activity, engagement).
The configuration is deliberately simple, even if some mechanics are still being improved, particularly the dynamic management of point loss when attributes change.

For the lead lifecycle, the approach shown consists of rebuilding a complete logic using workflows, offering flexibility similar to that found on Marketo.

Key takeaways

At the end of this first demo:

• Paminga's foundations are solid

• Some components are still in transition, inherited from Net-Results

• Each component rebuilt from scratch is particularly well designed

• The product trajectory inspires confidence in the short term

What now?

This demo kicks off a series of monthly webinars, each dedicated to a specific use case or building block.

If you would like a personalized demo focused on your challenges (CRM, tracking, forms, lifecycle, ABM, etc.), I would be happy to organize one.