Optisleek connects a WooCommerce store to the Optisleek platform, which uses AI tools to optimize the performance of an ecommerce business.<\/p>\n\n
Features:<\/p>\n\n
[optisleek_landing_page]<\/code> shortcode and an optional landing page on every product page.<\/li>\n<\/ul>\n\nAn Optisleek account is required. The plugin does nothing until you enter your Optisleek URL and pixel code in Optisleek \u2192 Settings.<\/p>\n\n
External services<\/h3>\n\n
This plugin connects to the Optisleek service (https:\/\/www.optisleek.com\/), operated by FDN Group. Every connection goes to the Optisleek URL that the site administrator enters in the plugin settings. Nothing is sent before that URL and the pixel code are set.<\/p>\n\n
Event tracking<\/strong> \u2013 used to measure the store's performance and to train the recommendations.\nWhen a visitor views a product or category, adds a product to the cart or completes an order, the visitor's browser sends to <Optisleek URL>\/api\/event\/push<\/code>: the pixel code, a random visitor ID (stored in the browser's localStorage), the event type, the product IDs, prices and quantities involved, the page URL, the referrer, the screen and window size, the browser's user agent, and the campaign IDs of Optisleek links. When an order is completed, the store's server also sends the order's products, quantities and totals. No names, email addresses, phone numbers or addresses are sent.<\/p>\n\nProduct sorting<\/strong> \u2013 used to fetch the AI product order for each category.\nTwice a day (WP-Cron), and when an administrator clicks \"Sync\", the store's server sends the API token and shop ID from the settings to <Optisleek URL>\/api\/products\/sort<\/code> and receives the product order.<\/p>\n\nProduct widgets and landing pages<\/strong> \u2013 used to show the recommendations.\nOn pages that display a widget or a landing page, the visitor's browser loads the Optisleek script <Optisleek URL>\/public\/widgets\/products.js<\/code>, which shows the widget in an iframe from the Optisleek service. The script receives the pixel code, the current product ID and, for landing pages, the landing page token.<\/p>\n\nCatalog sync<\/strong> \u2013 the plugin adds the endpoint \/optisleek\/api?sync=...<\/code> to the store. Optisleek reads the public catalog data from it: brands, categories, attributes, products, prices, stock and image URLs. No customer data is included. The latest full export and the list of disabled products are also saved as JSON files in the plugin's api\/files\/<\/code> folder.<\/p>\n\nService terms of use: https:\/\/www.optisleek.com\/footer\/legal\/terms-of-service\/\nService privacy policy: https:\/\/www.optisleek.com\/footer\/legal\/privacy-policy\/<\/p>\n\n\n
\n- Install and activate WooCommerce.<\/li>\n
- Upload the plugin to
\/wp-content\/plugins\/optisleek<\/code> and activate it.<\/li>\n- Go to Optisleek \u2192 Settings and enter your Optisleek URL and pixel code.<\/li>\n
- Enable the features you want from the Optisleek menu.<\/li>\n<\/ol>\n\n\n
\nDo I need an Optisleek account?<\/h3><\/dt>\nYes. The plugin connects your store to the Optisleek platform and needs the URL and pixel code of your account.<\/p><\/dd>\n
Does the plugin work without WooCommerce?<\/h3><\/dt>\nNo. WooCommerce is required.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.5<\/h4>\n\n\n- All front-end JavaScript is now loaded with wp_enqueue_script \/ wp_add_inline_script (tracking script moved to
assets\/js\/optisleek-tracking.js<\/code>).<\/li>\n- Admin notices are shown only on the plugin's own pages and the Plugins page.<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Catalog export also saved to
api\/files\/optisleek_data.json<\/code> and api\/files\/disabled_products.json<\/code>.<\/li>\n- Disabled products: unpublished, permanently deleted, and old out-of-stock products.<\/li>\n
- Code updates for the WordPress.org Plugin Check.<\/li>\n<\/ul>","raw_excerpt":"Connects your WooCommerce store to Optisleek: tracking, AI product sorting, product recommendation widgets and landing pages.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/391288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=391288"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/fdngroup"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=391288"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=391288"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=391288"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=391288"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=391288"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=391288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}