What a configuration could hand over
The configurator does not need a domain of its own. It is embedded in an existing page, so the visitor never leaves your site and the page keeps the links and the history it has built. On a product page that is the difference between compounding and starting over.
Custom HTML block
The configurator can be embedded in a page with a Custom HTML block or a shortcode, so it stays on the same address, in the same menu and under the same analytics.
Custom post type
Enquiries could be stored in WordPress itself as a custom post type, such as Enquiries, with the dimensions, price and 3D preview link in custom fields.
REST API
Such an enquiry can be written through the WordPress REST API, provided the post type has show_in_rest turned on.
treede CRM
If you would rather not keep enquiries in WordPress, they can go straight to the treede CRM and the site stays a shop window with the configurator in it.
What we need to connect it
Embedding a script needs a user with the unfiltered_html capability: an administrator on a single site, only a super admin on Multisite.
If enquiries are to be stored in WordPress, you create an Application Password for us in the user profile, which can be revoked at any time.
The embed would be tested on a copy of the site first, to see whether a cache or security plugin alters the script.
We agree which pages the configurator runs on and where an enquiry goes once submitted.
Worth deciding up front
- Security and caching plugins can strip, combine or defer scripts in page content. If they do, the configurator needs an exception.
- WordPress has Application Passwords since version 5.6 and, by default, only on sites served over HTTPS, so an older or unencrypted site would need updating first.
- Analytics stay on your own domain. Configurator events, such as a submitted enquiry, can be added to it during implementation.
Questions about this connection
Will the configurator slow the site down?
The rest of the site is unchanged; the 3D loads only where the configurator is embedded. During implementation we can have it start only when it scrolls into view, and we measure the effect on your own page.
Do we need WooCommerce for this?
WooCommerce is not needed for this, as WordPress alone is enough for an enquiry. It only comes into it if you want to sell with payment in a cart.
Other integrations
Put WordPress to work in your sales.
Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.