← Back to modules

nexya mailya

Newsletters written on the WordPress site, with your posts in them — sent in the background, at the pace your server can hold.

  • Written the way it is seen Header, titles, texts, images, buttons, dividers and latest posts: sections are stacked and moved, and the preview redraws beside them, on a computer and on a phone.
  • Subscribers come from your forms Mailya’s own form, or those of Gravity Forms, Contact Form 7, WPForms, Elementor and Fluent Forms: one checkbox is enough, and each form picks its lists.
  • Sent without holding the site back Messages leave in small batches in the background, through the site’s sending method or the host’s scheduled task. No time limit to fear, even for thousands of addresses.
0:48

Pro

Live editor built from sections, templates, lists and contacts, sign-up forms with double opt-in, campaigns now, at a date or again and again, opens and clicks followed.

Get started

nexya mailya in three steps

  1. Switch on Mailya In the nexya hub, with the Pro licence (seven-day free trial).
  2. Connect your forms Mailya’s own form, or Gravity Forms, Contact Form 7, WPForms, Elementor, Fluent Forms.
  3. Write the first newsletter Stack the sections, drop in your latest posts, and send now or at a date.

nexya mailya is in the Pro version, with a seven-day free trial.

Start 7-day free trial

FAQ

Everything about nexya mailya

With Mailya, the newsletter is written in a section editor with the preview beside it, then goes to your lists now, at a date or on a schedule. Messages leave in small batches in the background.

Contacts stay on your site, not with a third-party service, and there is no subscription by number of subscribers. Messages go through the site’s sending method, the one set in nexya mail.

One checkbox is enough in Gravity Forms, Contact Form 7, WPForms, Elementor or Fluent Forms. Each form picks its lists, with double opt-in by e-mail.

Yes: messages leave in batches, at the pace your server and sending service accept, with no time limit to fear.

Yes: each campaign has its report, with sends, opens and clicks.

The suite

Other modules

nexya translate

The site in several languages: every content with its versions, an address per language, and the site’s texts translated in one place.

nexya popup

Popups composed section by section, opening at the right moment — and able to close the shop and the forms while they are live.

nexya custom fields

Fields of your own, kept in their own tables — and read in a single query per page.

nexya aris

Audience figures, measured by the site itself — no Google, no Matomo, no IP address kept.

nexya media

Folders to sort the media library, and thumbnail regeneration in the background, in batches, carrying on when you close the tab — and telling you when it is finished

nexya hub

The panel that gathers every nexya plugin. A module you switch on, a module you switch off — and nothing running on the WordPress site while it is off

nexya dashboard

The WordPress admin as the client sees it: menus cut down to what is useful, a tidy admin bar, and the dashboard in your own colours right through to the login page

nexya shortcuts

Duplicate, reorder, add — three gestures placed on the WordPress content lists, so you stop doing them by hand

nexya roles

WordPress capabilities filed under the plugin that creates them, readable at last. And the menu cut down to what the person in front of it actually has to do

nexya activities

Who changed what on the WordPress site, and when. Down to the ACF fields, with the value before and the value after — and the button to put it back

nexya cookie

Cookie consent, and the blocking that goes with it. Nothing runs before the visitor agrees — not the scripts, not the embedded videos, not the remote fonts

nexya seo

What the WordPress site says about itself to search engines — and what it shows when someone pastes its address somewhere. Written once, applied everywhere, checked before publishing

nexya mail

The WordPress site’s emails actually go out — and you know which ones did not, with the exact reason given by the SMTP server

nexya redirects

The 404 errors picked up as visits happen, and the 301 redirect suggested before anyone goes looking for it. With the number of hits, so you know which ones count

nexya security

The HTTP security headers set without breaking the site, the watch on vulnerabilities in the WordPress plugins installed, and the eye on what moves in the files

nexya maintenance

The operations you carry out on the WordPress site rather than in it: closing it for an intervention, slimming its database down, taking a copy

nexya cache

Each page kept as a file and handed to the next visitor before WordPress loads — then thrown away as soon as something changes it.