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] 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 Settings → SendBeam 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 log of recent results.
• E-commerce events (WooCommerce) — feed SendBeam’s native Cart Abandoned, Product Viewed and Order Placed automation triggers. Order placed also keeps a running lifetime-value total on the contact. Each event has its own switch, off by default.

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.

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 five 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 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.

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 when an order is completed. 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.