Installing Plugin for WooCommerce Sites
The Yespo plugin allows you to manage your WooCommerce website’s marketing campaigns within one Customer Data Platform. The plugin allows you to:
- Transfer contacts from your site to Yespo.
- Synchronize order data (historical and new).
- Transfer website events, such as user activity, visited pages, cart and order contents as the plugin installs the tracking script on your WooCommerce site.
- Automatically register a domain, get and install the script and service worker, simplifying the entire Web Push configuration process.
After integration, you will be able to:
- Organize automatic onboarding workflow for new contacts.
- Enrich contact profiles with the data from your alternative platforms, such as mobile apps.
- Send bulk omnichannel campaigns.
- Set up transactional message chains.
- Analyze campaigns’ performance in real-time.
- Collect Web Push subscribers and message them in the corresponding channel.
When installed, the plugin allows sending the following events to Yespo as described in the table below.
Event | Description |
|---|---|
| This event is sent when a site visitor loads a particular website page. Default event, required for all other web tracking events to work. |
| The event is associated with actions on your product pages. It can be used for campaigns involving abandoned view, discount notifications for viewed items, or win-back campaigns. |
| It is triggered when a visitor views a product category page. After receiving this event in Yespo, you can send emails with recommendations of the most popular products in the viewed category. |
| This event relates to the site visitor’s data received when they register, log in, or complete a purchase. The event links your website visitors to accounts in your system, enabling personalized campaigns. |
| The event helps to track the status of your customers’ shopping carts. It can be used for running ecommerce workflows, such as abandoned cart, discount notifications for products in the abandoned cart, and notifications for discounts on products similar to those in the cart. |
| It informs about the purchased items and can be used for compiling lists of popular products for recommendations, upselling, and cross-selling. For example, if a customer purchased a phone, you can send them a message with recommendations featuring a phone case or a charger. |
| It is triggered when a visitor is currently on the main page. Necessary to display recommendations on the site. |
| This event tracks 404 page. Necessary to display recommendations on the site. |
| This event is used to show impressions for recommendation blocks in Reports. |
In case of deactivation, the plugin ceases to perform its functions.
Uninstalling the plugin removes all components configured during the setup of web tracking, including scripts and functions used for event tracking.
Note
- The plugin relies on data transfer via cron jobs. Ensure you have an active cron set up: either the default WordPress cron or a server-side cron on your hosting.
- If you're using any caching plugins, make sure to install updates through the WordPress repository and clear your cache afterward to ensure all changes are properly applied.
WordPress & WooCommerce Hooks
For the plugin to function properly, make sure of the following:
- Standard WordPress system hooks have not been removed or deactivated in the theme or by other plugins. These hooks are active by default, so if they are missing, it may be due to remove_action or remove_filter being used intentionally.
- Required WooCommerce hooks are present in the theme and functioning correctly. These hooks are essential for integrating with WooCommerce features and must be available in your setup.
If any standard WordPress hooks have been forcibly removed or if the required WooCommerce hooks are missing, the plugin may not work as expected.
Action WordPress Hooks
| Name | Description |
|---|---|
admin_notices | This hook displays messages in the admin notice area. It is part of the WordPress core and is not affected by front-end themes or their customizations. Used by WordPress itself and other plugins. |
profile_update | Triggered when a user profile is created or updated. It belongs to the WordPress core and is independent of front-end themes or customizations. Used by both WordPress and third-party plugins. |
delete_user | Triggered before a user is deleted. This core WordPress hook functions independently of theme customizations. Utilized by WordPress and external plugins. |
wp_privacy_personal_data_erased | Triggered after a personal data erasure request is completed (GDPR). Part of WordPress core and not influenced by front-end theme customizations. Used within the WordPress core. |
admin_enqueue_scripts | Used to enqueue JavaScript and CSS files that extend the admin panel's functionality. It is part of the core and not affected by front-end themes. Utilized by WordPress and plugins. |
wp_footer | Adds custom code before the closing </body> tag. Part of the WordPress core, and not impacted by front-end themes. Used by both WordPress and plugins. |
wp_login | Triggered after a successful user login. Core hook not affected by front-end customizations. Used by WordPress and other plugins. |
Filter WordPress Hooks
| Name | Description |
|---|---|
cron_schedules | Used to add custom interval cron tasks. Utilized by both WordPress and third-party plugins. |
Action WooCommerce Hooks
| Name | Description |
|---|---|
woocommerce_add_to_cart | riggered when a product is added to the cart. Part of the WooCommerce core, initialized in CartController.php in src/StoreApi/Utilities. |
woocommerce_after_cart_item_quantity_update | Triggered when the quantity of items in the cart is changed. Core WooCommerce hook, initialized in class-wc-cart.php in the includes directory, but not actively used by the plugin itself. Since includes files are rarely modified, the risk of this hook being broken is low. |
woocommerce_cart_item_removed | Triggered when an item is removed from the cart. A core WooCommerce hook, initialized in class-wc-cart.php under includes. Actively used by WooCommerce. Since includes files are rarely modified, there’s minimal risk of this hook being affected. |
woocommerce_thankyou | Triggered after an order is placed. Part of WooCommerce core, used in templates to show final order details. Initialized in thankyou.php under templates/checkout. Since template files are often customized, there's a higher risk of hook initialization being overwritten. |
Installing Plugin
- Log into your WordPress account.
- Go to the Plugins section.
- Find Yespo in the search field and click Install now.
Or,
- Go to the WordPress plugins page.
- Find Yespo in the search field and click Download.
- Upload plugin at the Plugins section of your WordPress account.
- Click Activate.
- Click the Settings button under the plugin on the Installed Plugins section or navigate to the separate Yespo page.
- Enter your full access API key from the Yespo account and click Synchronize to start data synchronization.
Note
- The access rights for the API key must be Full access to API. Read this article to learn about API keys in Yespo.
- Yespo plugin supports multisite configurations for WooCommerce stores in WordPress. For correct data handling, each WooCommerce store must be connected to a separate Yespo account.
After clicking the Synchronize button, the new contacts’ and orders’ data that appear in WooCommerce will be automatically transferred to Yespo. The on-site event tracking configuration and Web Push script installation will also be completed. To ensure proper operation, make sure to add the product feed to Yespo.
Please contact us if you have any questions or problems with integration.
Updated 12 days ago