The WordPress connector is on the roadmap and is not built yet, so nothing on this page can be set up today. It describes what the integration will do when it ships. In the meantime you can connect WordPress through Zapier, viaSocket, or webhooks and the REST API. Note that polling-based automation can lag by up to fifteen minutes, which matters for time-critical flows such as cart recovery.
Capture on your site, send from real infrastructure
Embed Bluey forms and popups on any WordPress site, and route your site's transactional mail through authenticated SMTP instead of your host's mail function — the usual reason WordPress email lands in spam.
Typical setup: 10 minutes · No developer required · Connecting a store never raises your bill
The WordPress integration does two separate jobs. First, capture: embed Bluey forms, inline signup blocks and exit-intent popups anywhere on your site, with submissions landing directly in Bluey with their source page attached. Second, delivery: point WordPress's outbound mail at Bluey's authenticated SMTP so password resets, comment notifications and contact-form replies stop being sent by your host's PHP mail function, which is the single most common cause of WordPress email going to spam. Setup is about ten minutes and needs no code.
What actually syncs
The specifics, so you can tell before you connect anything whether the flows you want are possible.
| Data | Direction | Notes |
|---|---|---|
| Form submissions | Into Bluey | Every field, plus the page URL, referrer and UTM parameters, so you know which post or landing page produced the subscriber. |
| Page and post views | Into Bluey | For identified visitors, enabling content-based segmentation — someone who reads three pricing posts is a different prospect from someone reading one recipe. |
| Outbound site email | Out of Bluey | WordPress transactional mail routed through Bluey's SMTP with SPF and DKIM applied, and delivery logged rather than silently dropped. |
| User registrations | Into Bluey | New WordPress users sync as contacts with their role attached, so members and customers can be segmented apart from newsletter subscribers. |
What you can build once it is connected
Setting it up — about 10 minutes
- 1Install the Bluey plugin from your WordPress admin
- 2Connect it with your Bluey API key
- 3Enable SMTP routing so WordPress sends site email through Bluey
- 4Add SPF and DKIM records for your sending domain — this is what makes the SMTP switch worthwhile
- 5Place a form or popup with the block editor, or use the shortcode anywhere in your theme
- 6Send a test password reset and confirm it appears in Bluey's delivery log
What this integration does not do
Worth knowing before you build a plan around it.
- Content-view tracking only works for identified visitors — someone who has clicked an email or submitted a form. Anonymous readers are counted but not addressable.
- The plugin does not replace a full page builder; landing pages built in Bluey are hosted by Bluey, not injected into your theme.
- Multisite installations need the plugin configured per site rather than network-wide.
- SMTP routing covers mail sent through WordPress's standard mail function. Plugins that send directly via their own transport need pointing at Bluey separately.
WordPress integration FAQ
Why do my WordPress emails go to spam?
Almost always because they are sent by your host's PHP mail function from a shared server IP, with no SPF or DKIM alignment for your domain. To a receiving mail server that looks exactly like forged mail. Routing through authenticated SMTP with SPF and DKIM published for your domain fixes it in most cases, and it is the single highest-value thing this integration does.
Does this work with Elementor, Divi or Gutenberg?
Yes. Bluey forms embed as a Gutenberg block, a shortcode or raw HTML, so any builder that accepts a shortcode or HTML widget can render them. Popups and exit-intent forms are configured in Bluey and injected by the plugin, independent of the builder.
Can I keep using Contact Form 7 or Gravity Forms?
Yes. Point them at Bluey's API or let the plugin route their submissions across. You keep the form UI you have built and gain the list, the segmentation and the sending.
Will the plugin slow my site down?
The tracking script is small and loads asynchronously. Popups render client-side after content paint. If you run aggressive caching, exclude the form endpoints from the cache so submissions post correctly.
Does this work on WordPress.com?
On Business plans and above, where third-party plugins are allowed. On lower WordPress.com tiers you cannot install plugins, so embed a Bluey form with an HTML block instead — you keep capture, but not SMTP routing.
Keep exploring
Connect WordPress and ship your first flow this week.
Seven days of full access, no credit card. Connect the integration, turn on one flow, and watch what it recovers before you decide.