SendBeam

SendBeam is email marketing for people who run more than one website: one account, a workspace per site, and a plan that counts subscribers across all of them. Every signup this plugin collects joins a list in SendBeam, where campaigns and automations pick it up — the forms and pop-ups are the front door, not the whole house.

This plugin puts your SendBeam forms on a WordPress site without copying embed code around:

• SendBeam Form block — pick a form, set a height, done. Works in posts, pages, templates and the site editor.
• Shortcodes — [sendbeam_form id="…"], [sendbeam_contact id="…"] and [sendbeam_popup_button] for widgets, page builders and the classic editor.
• Pop-up — show a signup form in a modal after a delay or from a floating button, on every page, posts only, pages only or the home page; hidden for a day, a week or for good once a visitor closes it.
• Pop-up styles — four looks for the modal: split with image, editorial, bold colour and slide-in, each with its own image, eyebrow, button label and optional subscriber count, chosen per pop-up.
• A default form — set it once under SendBeam → Forms and every block and shortcode without an ID uses it.
• Form plugins — send the people who fill in forms built with Contact Form 7, Elementor Pro, WPForms, Gravity Forms or Fluent Forms to SendBeam, onto the list and with the tag you choose. Switched on form by form, and only for people who ticked your consent field or filled in a form you marked as a signup form.
• Site email — send everything WordPress sends with wp_mail() (WooCommerce order confirmations, password resets, form and comment notifications, plugin alerts) through your verified SendBeam domain. No SMTP host, port or password: one API key, one switch, a test button, and a searchable log of every message with what became of it and which plugin asked for it.
• E-commerce events (WooCommerce) — feed SendBeam’s native Cart Abandoned, Product Viewed and Order Placed automation triggers. Order placed fires once, when the order is paid, and keeps a running lifetime-value total on the contact. Each event has its own switch, off by default. Works with both the classic checkout and the block checkout WooCommerce installs.

It has its own menu in wp-admin, with a page per section — Overview, Forms, Pop-ups, Audience, Site email, E-commerce, Settings and Help — and walks a new site through connecting, verifying its sending domain, switching on site email and placing a form the first time it is activated. That guide can be skipped a step at a time or left entirely; every step is also on the Overview.

Connecting is one button: tick what this site may do, sign in or create your account in the window that opens, and the key arrives on its own. You choose the domain you send from — this site’s, or a brand domain you own — and the plugin shows you its DNS records, checks them again on its own for a day afterwards, and switches your site email on once they are live. If you did not give a permission, the step that needs it offers to reconnect; disconnecting revokes this site’s key and leaves everything in your workspace where it is.

Forms are shown exactly as configured in SendBeam (fields, double opt-in, the thank-you message, the list they join), so changing a form there changes it on your site straight away. Displaying a form makes no request from your server — the visitor’s browser fetches it. Site email, when you switch it on, is one HTTPS call per message to SendBeam’s API.

Your forms, your lists and the site’s email log are proper WordPress list tables: search, sort out how many rows you want per screen, and delete log entries in bulk, the same way the Posts screen works. SendBeam → Help carries the documentation links, the shortcodes, what each API key permission is for, and a system-status block that copies in one press for a support email; the same information is in Tools → Site Health, along with three checks — your key works, your sending domain is verified, and your site’s email is not being sent from a domain nothing has verified.

A site can listen for sendbeam:submitted on document to track a signup as an analytics goal or redirect to a thank-you page.

External service

This plugin talks to SendBeam (sendbeam.io) in six distinct ways. Nothing is sent anywhere else.

1. Showing a form or pop-up. The visitor’s browser loads the form from https://sendbeam.io/f/<form id> and, for the pop-up, the script https://sendbeam.io/f/<form id>/popup.js. The URL carries the appearance you chose (colours, corner radius, text size, typeface) so the form matches your theme, and for a pop-up its headline, line underneath, style, image address, eyebrow, button label and whether to show the subscriber count; these are your settings, not anything about the visitor. Your server makes no request to show a form.

2. A visitor submitting a form. What they typed — their email address and any other fields on that form — is sent to SendBeam to create the subscriber or deliver the message.

3. The plugin’s settings screens. While a site administrator has the SendBeam settings page open, your server calls SendBeam with your API key to list your forms (/api/v1/forms), your lists (/api/v1/lists), the number of people on each list (/api/v1/lists/<id>/contacts) and your subscriber total (/api/v1/contacts). This is what lets the plugin offer your forms in a dropdown instead of asking you to paste an ID. The results are cached for five minutes. No visitor data is involved and nothing is sent on front-end page loads.

4. Subscribing someone who ticked the opt-in box (off by default). When a visitor registers an account, leaves a comment or checks out in WooCommerce (the classic or the block checkout) and ticks the subscribe box, their email address, first and last name and which of those three things they were doing are sent to /api/v1/contacts and added to the lists you chose. Nobody who has not ticked the box is ever sent, and the box is never pre-ticked.

5. Forms built with another form plugin (off by default, and off for every form until you switch it on for that form). When someone submits a Contact Form 7, Elementor Pro, WPForms, Gravity Forms or Fluent Forms form you have connected, and either ticked the consent field you named or filled in a form you marked as a signup form, their email address, first and last name and the name of the form plugin are sent from your server to /api/v1/contacts, added to the list you chose (/api/v1/lists/<id>/contacts) and, if you set one, given a tag (/api/v1/tags and /api/v1/contacts/<id>/tags). Nothing else from the form is sent.

6. Connecting this site to SendBeam (only when you press the Connect SendBeam button). A window opens on https://sendbeam.io/connect/wordpress carrying this site’s address, its title, your WordPress administrator email address — used only to fill in the signup or sign-in form, so you do not type it again — and the list of permissions this site is asking for. If you do not already have a SendBeam account you create one there, on sendbeam.io; account creation never happens on your site and your SendBeam password is never seen by WordPress. When you approve, your server makes one call to https://sendbeam.io/api/v1/connect/exchange and receives an API key for this site with exactly the permissions you ticked. The key is stored in this site’s options table, the same place a pasted key goes. Press nothing and nothing is sent.

What SendBeam does at that moment, in your workspace, is decided by the boxes you tick: if you leave the sending-domain box ticked it adds this site’s domain as a sending domain so its DNS records exist for you to copy, and if the workspace has no signup form yet it creates a list called Subscribers and a form called Newsletter signup on it. Afterwards, while a site administrator has the SendBeam settings page open, your server reads https://sendbeam.io/api/v1/connect/status with this site’s key to show the domain’s records and whether it is verified; the answer is cached for a minute. Pressing Check now posts to the same address to ask for the DNS to be looked up again. Pressing Disconnect posts to https://sendbeam.io/api/v1/connect/disconnect, which revokes this site’s key in SendBeam, and then the key is deleted from this site.

Site email (off by default) posts each email your site sends from your server to https://sendbeam.io/api/v1/transactional with your API key: the recipient addresses, subject, body and reply-to, so SendBeam can deliver it from your verified domain. Messages with attachments are left to the server’s own mailer.

E-commerce events (off by default, each of the three switched on separately, WooCommerce only) posts to https://sendbeam.io/api/v1/ecommerce/events with your API key: an email address, and depending on the event a name, an order total and its currency. Order placed sends once an order is paid — when it reaches processing or completed — never for a checkout that ends unpaid, and once per order. Product viewed sends only when the visitor is a known contact (logged in, or an email already given this visit) — never for an anonymous visitor. Cart abandoned is a best-effort heuristic: adding an item to the cart is timestamped locally on your server, and if no order has followed within a window you set (60 minutes by default) and an email became known at some point, one event is sent; nothing is sent for a cart nobody’s email was ever known for.

Full setup documentation: sendbeam.io/docs/wordpress. See also the SendBeam privacy policy and terms.

Requirements

A SendBeam account (the Free plan is enough) with at least one form. Form IDs are shown under Forms → your form → Embed.