About this plugin
Sitebix to EmailOctopus connects your site to EmailOctopus API v2:
- Connection — API key (encrypted in the database or via wp-config.php constant), list picker, default contact status ( subscribed vs pending for double opt-in), connection test.
- Sources — Multiple named profiles with field mapping (source keys → EmailOctopus field tags), static tags, and optional dynamic tags from one payload field.
- WordPress user sync — Role filters, comparison against list contacts (paginated API), batched upserts via Action Scheduler when available, otherwise WP-Cron.
- Elementor Pro — Native “Sitebix → EmailOctopus” form action after submit (mapping profile selector).
- Webhook — REST endpoint POST /wp-json/sitebix-weo/v1/webhook/{source_id} with shared secret (?secret= or X-Sitebix-WEO-Secret ). Optional IP allowlist. First-hit “hold until mapped” workflow with sample payload and replay.
- Activity log — Custom database table; filterable/paginated admin log (created, updated, skipped, webhook held, errors, bulk sync).
No Composer dependencies. Rate limits (429) are handled with retries/backoff.
Developer: K. com
Elementor Pro (native action)
- In Sitebix EO → Sources & mapping, add an Elementor profile and map form field IDs to EmailOctopus tags (include one row for your list’s contact email field — often emailAddress or email_address ).
- Edit your Elementor form → Actions After Submit → add Sitebix → EmailOctopus.
- Select the mapping profile and save.
Webhook (Elementor “Webhook” action or any HTTP client)
- Add a Webhook source; set a New webhook secret and save.
- Copy the Webhook URL from the source card. Append?secret=YOUR_SECRET or send header X-Sitebix-WEO-Secret: YOUR_SECRET.
- On first receive, while mapping is incomplete or the source is inactive, the plugin holds the payload, stores a redacted sample, and returns HTTP 202. Complete mapping, set state to Active, check Active, then save. Use Replay sample if needed.
IP allowlist: One IP per line in the source settings; empty list allows all. Behind reverse proxies, REMOTE_ADDR may need server configuration for accuracy.
User sync & background processing
Bulk sync enumerates existing list contacts (paginated), compares to WordPress users (optional role checkboxes on the Connection tab), then upserts missing contacts in batches. g. via WooCommerce), jobs run there; otherwise WP-Cron schedules follow-up ticks.
php enabled on budget hosts.
External services
com ) so site owners can sync WordPress users and form submissions to EmailOctopus lists.
What it is used for: creating and updating EmailOctopus contacts, listing lists and fields, testing the API connection, and (when configured) comparing WordPress users to list contacts during bulk sync.
What data is sent and when:
* The site owner’s EmailOctopus API key is sent as a Bearer token on every API request (after they save it in settings, or via the optional SITEBIX_WEO_API_KEY constant).
* Contact data mapped by the site owner (at minimum an email address; optionally names, custom fields, and tags) is sent when a WordPress user is created/updated and matches sync rules, when an Elementor form action or webhook source processes a submission, when a held webhook sample is replayed, or when a bulk user sync runs.
* Connection tests and list/field lookups send only authentication and list identifiers — not contact payloads — when an admin uses those controls.
No contact data is sent until the site owner configures an API key and active mapping sources. EmailOctopus is operated by Three Hearts Digital Ltd.
- Terms of Use: https://emailoctopus.com/legal/terms
- Privacy Policy: https://emailoctopus.com/legal/privacy
Credits
Developed by K. Young for Sitebix.