MailerLite to Qlik Integration

How Datrise loads MailerLite into Qlik

Datrise syncs MailerLite's subscribers, groups, campaigns, automations, email events, and forms into Qlik as tables loaded into Qlik's associative engine (often via QVD). Flexible or custom fields land in flattened columns for the data model, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental QVD loads merged on stable id, so re-runs update only what changed. QVD files per entity and load date. Qlik's associative model joins on identically named fields, so Datrise standardizes key names so associations link correctly.

Ideal for associative, in-memory exploration in Qlik Sense.

Endpoints

MailerLite: Email campaigns, automations, and landing pages.

Qlik: Associative analytics with Qlik Sense apps and governed data models.

How MailerLite entities map to Qlik

MailerLite entity	Qlik object	Notes
subscribers	`mailerlite_subscribers`	id PK · custom fields → flattened columns for the data model
groups	`mailerlite_groups`	id PK · linked to mailerlite_subscribers
campaigns	`mailerlite_campaigns`	id PK · linked to mailerlite_subscribers
automations	`mailerlite_automations`	id PK · linked to mailerlite_subscribers

FAQ

How does Datrise handle MailerLite's custom fields in Qlik?

Flexible values are stored as flattened columns for the data model, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Qlik types.

How does the MailerLite to Qlik sync stay up to date?

It runs incrementally — Datrise uses incremental QVD loads merged on stable id.

Related pipelines

Early access

Connect MailerLite to Qlik the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.