內容簡介
WooRule 外掛是由 Rule 開發的，是 WooCommerce 與 Rule 行銷自動化平台的整合。
Rule 平台是一個直覺且易於使用的數位通訊服務，可為任何規模的公司和組織簡化外部通訊。Rule 讓您能夠透過電子郵件和簡訊向客戶發送超個人化和自動化的數位通訊。
在安裝這個整合後，您的 WooCommerce 資料將開始傳送至 Rule。藉由這些資料，您可以啟用許多電子商務通訊流程，例如：電子報、放棄購物車、訂單跟進、運送跟進、客戶保留、客戶回流、歡迎通訊等，還有更多其他功能！
使用方式
WooRule 具有自動事件觸發器，當客戶下訂單時會向 Rule 傳送資料。標籤會應用於 Rule 平台中的客戶，然後可以用來向訂閱者（您的客戶）發送自動化通訊。資料儲存為自訂欄位，包括有關訂閱者（例如名稱、地址、電子郵件、電話號碼）和訂單的信息（訂購的產品、訂單日期、價格、折扣、集合等，還有更多！）
以下事件用於在客戶訂單流程中應用以下標籤：
# 事件觸發器 標籤名稱 事件描述
1 購物車已更新 CartInProgress 購物車內容已更新
2 處理中 OrderProcessing 訂單已支付並等待處理
3 已完成 OrderCompleted 訂單已處理並完成
4 已出貨 OrderShipped 訂單已出貨*
*這是一個自訂事件觸發器，除非由商家添加，否則不會觸發。
有關 WooCommerce 訂單事件的更多信息可在此處閱讀。
WooRule 還包括一個可選的結帳註冊表單，顧客可以輕鬆選擇自動營銷通訊，例如電子報。
短碼
您可以在文章中或任何頁面上嵌入一個電子報註冊表單，只需使用簡單的短碼[woorule]
您還可以使用以下任何短碼屬性自定義註冊表單：
[woorule title="自訂標題" placeholder="自訂占位符文本" button="自訂按鈕文本" checkbox="核取方塊旁邊的自訂文本" success="自訂成功消息" tag="自訂標籤名稱" require_opt_in=false]
checkbox 屬性會在註冊表單下方添加核取方塊。如果此屬性存在，則在提交表單之前必須勾選核取方塊。這對於確保訂閱者同意加入郵件列表很有用。
tag 屬性將應用於提交表單時的訂閱者。如果未使用標籤欄位，則默認應用Newsletter標籤。
require_opt_in 屬性，如果設置為true，則需要訂閱者接受允許發送進一步營銷電子郵件的電子郵件。接受允許流程要求您在 Rule 帳戶中設置訂閱者表單，以便向訂閱者發送允許電子郵件。請注意，tag 屬性應該與表單標籤相同。
外掛標籤
開發者團隊
📦 歷史版本下載
原文外掛簡介
The WooRule plugin is developed by Rule as an integration between WooCommerce and the Rule marketing automation platform.
The Rule platform is an intuitive and user-friendly digital communication service that streamlines the external communication for companies and organization of any size. Rule enables you to send hyper-personalized and automated digital communications via email and SMS to your customers.
After installing this integration, your WooCommerce data will start sending to Rule. With this data you can enable many e-commerce communication flows such as: newsletters, abandoned cart, order followup, shipping followup, customer retention, customer winback, welcome communications, and much more!
Usage
WooRule has automatic event triggers that send data to Rule when a customer places an order. Tags will be applied to the customer within the Rule platform, which can then be used to send automated communications to subscribers (your customers). Data is saved as custom fields, and include information about the subscriber (e.g. name, address, email, phone number), and their order (products ordered, order date, price, discounts, collection, and much more!).
The following events are used to apply the following tags in the customer order flow:
# Event Trigger Tag Name Event Description
1 cart updated CartInProgress Cart contents are updated
2 processing OrderProcessing Order is paid and awaiting fulfillment
3 completed OrderCompleted Order fulfilled and complete
4 shipped OrderShipped Order was shipped*
*This is a custom event trigger that will not trigger unless added by the merchant.
More information regarding order events in WooCommerce can be read here.
WooRule also includes an optional checkout signup form where customers can easily opt-in to automated marketing communications, such as newsletters.
Shortcode
You can embed a Newsletter sign-up form in your posts, or on any page with a simple shortcode [woorule]
You can also customize the sign-up form with any of the following shortcode attributes:
[woorule title="Custom Title" placeholder="Custom Placeholder Text" button="Custom Button Text" checkbox="Custom Text Next To Checkbox" success="Custom Success Message" tag="Custom Tag" require_opt_in=false]
The checkbox attribute will add a checkbox below the signup form. If this attribute is present then checking the checkbox is required before the form can be submitted. This is useful for ensuring the subscriber agrees to your terms before being added to a mailing list.
The tag attribute will be applied to the subscriber when the form is submitted. If no tag field is used a Newsletter tag will be applied by default.
The require_opt_in attribute, if set to true, will require the subscriber to accept an opt-in email before further marketing emails can be sent. The opt-in flow requires you to have a subscriber form setup in your Rule account in order for the opt-in email to be sent to the subscriber. Note that the tag attribute should be the same as the form tag.
