RD Station Marketing to MySQL Integration

How Datrise loads RD Station Marketing into MySQL

Datrise syncs RD Station Marketing's leads, conversions, landing pages, emails, segmentations, and funnel stages into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

RD Station Marketing: Inbound marketing automation for Latin American teams.

MySQL: Widely used OSS relational engine (InnoDB).

How RD Station Marketing entities map to MySQL

RD Station Marketing entity	MySQL object	Notes
leads	`rd_station_marketing_leads`	id PK · custom fields → JSON columns
conversions	`rd_station_marketing_conversions`	id PK · linked to rd_station_marketing_leads
landing pages	`rd_station_marketing_landing_pages`	id PK · linked to rd_station_marketing_leads
emails	`rd_station_marketing_emails`	id PK · linked to rd_station_marketing_leads

FAQ

How does Datrise handle RD Station Marketing's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the RD Station Marketing to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect RD Station Marketing to MySQL 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.