| 开发者 | bytephase |
|---|---|
| 更新时间 | 2026年9月1日 20:27 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[bytephase_lead_form] and [bytephase_self_checkin]) — zero configuration. Change the heading and button with attributes, e.g. [bytephase_lead_form title="Get a Free Repair Quote" button="Send Request"] (use title="" to hide the heading).do_action( 'bytephase_submit_form', [ 'form_id' => '...', 'data' => [ ... ] ] )[bytephase_lead_form]) and map its fields once in BytePhase.In BytePhase, open Settings → Integrations → Website Forms and choose WordPress. BytePhase creates the API key and shows it once — copy it together with your Store ID, then paste both into BytePhase → Connection in WordPress. See the setup guide for a walkthrough.
No. It forwards submissions to BytePhase and keeps only an operational log (status, time, request id) so you can confirm delivery. Customer details live only in BytePhase.
Temporary failures are queued and retried automatically. You can also retry them manually from BytePhase → Health.
The plugin transmits form submissions to BytePhase and stores no customer details in WordPress. It adds suggested wording to Settings → Privacy (Policy Guide) that you can copy into your site's privacy policy. Data sent to BytePhase is covered by the BytePhase privacy policy.
Give every Elementor form a unique Form Name and avoid renaming it later. The form name identifies the form to BytePhase — two forms with the same name are treated as one, and renaming a form means re-mapping it in BytePhase.
Yes. The built-in forms are designed to keep working on cached pages, and submissions themselves are never cached.
No. On normal pages the plugin loads nothing. On a page using a built-in form it loads one small stylesheet. Form submissions are forwarded server-side.