config/locales/en.yml in workarea-admin-3.5.21 vs config/locales/en.yml in workarea-admin-3.5.22
- old
+ new
@@ -301,10 +301,11 @@
young_label: This week,
past_three_months: Past 3 Months
views: views
edit:
client_id_note: Identifies the category for product import
+ default_sort_note: 'Since this category has featured products, this sort controls the products listed after the selected featured products.'
filters_note_html: 'Comma separated: just, like, this. If these fields are blank, the global values will be used from %{search_settings_link}.'
page_title: Attributes for %{category}
search_settings: search settings
show_navigation_false: Do not show Navigation
show_navigation_true: Show Navigation
@@ -4065,9 +4066,20 @@
orders: Orders
revenue: Revenue
aov: AOV
insights_for_this_customer: Insights for this Customer
percentile: percentile
+ customer_insights: Wondering about how Workarea customer insights work?
+ customer_insights_info_html: >
+ <strong>How are customer metrics tracked?</strong>
+ <p>Workarea's metrics engine saves reporting and insights data based on the customer's email address.
+ This allows for the best tracking of customers for generating helpful insights like
+ <a href="%{best_customers_path}">Best Customers</a>, <a href="%{customers_at_risk_path}">Customers at Risk</a>,
+ and <a href="%{repeat_purchase_rate_path}">Repeat Purchase Rate</a> as accurately as possible across both
+ guest and account checkouts.</p>
+ <strong>Wondering why some numbers don't line up?</strong>
+ <p>Because reporting is tracked by email address, changes in email address and/or having an account
+ can cause mismatch between the <a href="%{orders_path}">Orders</a> card and these insights.</p>
login:
never: Never logged in
time_ago: "%{period} ago"
name_types:
email: email