Understanding SmartPush Metrics (for SHOPLINE Merchants)

SmartPush
SmartPush
  • Updated

SmartPush Metrics lets you use synced store data to build audience segments and trigger automations with precision. With support for a broader set of behavioral events — including email engagement (Send, Open, Click), on-site actions (View Item, Add to Cart, Remove from Cart, Checkout), and order activity — you have more signals than ever to reach the right customers at the right time. This article explains the core concepts, the full list of supported events, how to use Metrics as automation flow triggers, and how to apply these metrics to precision marketing strategies.

Note: This article applies to SHOPLINE (myshopline.com) merchants only.


Concept Overview

Before using event data for segmentation or automation, familiarize yourself with the key concepts below.

ConceptDescription
EventAn event represents a recorded user action. For example, a customer sees your ad on a media platform and clicks the link to visit your store (Page View). They become interested in a product category and view the product listing (Product List Viewed), then click on a specific product's detail page (Product Viewed), add the product to their cart (Product Added to Cart), and finally complete the purchase (Order Purchased). In this case, each step—page view, product list view, product detail view, add to cart, and purchase—is an event. Events are a digital record of user behavior. SmartPush now also tracks a wider range of actions including Email engagement (Sent, Opened, Clicked) and on-site behavior (View Product, Add to Cart, Remove from Cart, Search, etc.).
Attribute

Attributes provide key context for an event and are categorized into Event Attributes and User Attributes.

  • Event Attributes: Describe what happened during the event. For example, the time of a "Subscription Contract Created" event, the product subscribed to, subscription cycle, and frequency. These attributes can be used as metrics, group dimensions, or filter conditions.
  • User Attributes: Describe user characteristics, such as email, phone number, etc.
UTM ParametersUsed to identify the source and medium of your traffic and campaigns. SmartPush aggregates UTM data across events to help you analyze which marketing channels drive the most engagement.
FilterFilter conditions allow you to narrow data when configuring reports. For example, to analyze conversion rates in the U.S., you can add a condition such as "Country = United States".

Supported Native Events

SmartPush has unified historical data into a standard metadata structure, making a wider range of events available for segmentation, analysis, and automation. The following events are now fully available:

EventDescription
Email Engagement (Channel Participation)
Send EmailRecorded when an automation or campaign email is sent.
Open EmailRecorded when a recipient opens your email.
Clicked EmailRecorded when a recipient clicks a link within your email.
On-site Behavior (Website Events)
View ItemRecorded when a customer visits a product detail page.
SearchRecorded when a customer performs a search on your store.
View CartRecorded when a customer visits the shopping cart page.
Add to CartRecorded when a customer adds an item to their cart.
Remove from CartRecorded when a customer removes an item from their cart.
Continue CheckoutRecorded when a customer enters the checkout process. This event triggers abandoned checkout logic.
Order CreateRecorded when an order is successfully placed.

Metric Operator

For all events, SmartPush allows you to filter by trigger count and time range — helping you determine how often an event occurred within a specified timeframe.

  • Trigger Count: If you only need to confirm whether an event occurred at least once, set the count to ≥ 1.

Time Range Options:

Time Range OptionDescription
CumulativeBy default, the time range is set to the past 12 months. For order-related events, all orders within the entire time range are included by default.
Time RangeEvent occurred within a specific start and end date (up to 12 months).
Start TimeEvent occurred after a specific date (up to 12 months).
End TimeEvent occurred before a specific date (up to 12 months).
Past X DaysEvents occurred within the past X days (1–180 days supported).

Using Metrics as Automation Flow Triggers

How Flow Triggers Are Organized

When setting up an automation flow in SmartPush, you select a trigger event that starts the flow. Triggers are now organized into four categories to make selection easier:

  • Recommended: Commonly used triggers such as customer subscription, contact enters segment, date-based triggers, and website behavior events (page view, cart update, checkout, order created).
  • Metrics: Event-based triggers powered by the unified Metrics system. These include:
  • Channel Participation — Email Send, Email Delivered, Email Open, Email Click, Email Bounce, coupon-related events, popup events
  • Website Behavior — User Register, User Subscribe, Submit Search, View Item, View Cart, Add to Cart, Remove from Cart
  • App Integration: Triggers from connected apps such as Member System, Subscription Commerce, and Wishlist.
  • API: Custom events reported by your store via API. Displays events based on what your store has submitted.
Important: All Metrics-type flow triggers require a paid SmartPush subscription. Free plan merchants can use Recommended and App Integration triggers.

Loop Prevention for Email Triggers

To prevent automation loops, SmartPush applies the following rules when an email-related event is used as a flow trigger:

  • Email Send / Email Delivered / Email Bounce: If the triggering email was sent by an automation flow (not a manual campaign), it will not re-trigger any flow that uses Email Send or Email Delivered as its trigger. This prevents a chain reaction where one flow's outgoing email continuously activates another.
  • Email Open / Email Click: These triggers use a more targeted check. If the email that was opened or clicked was sent by the current flow itself, that flow will not be re-triggered. However, if the email was sent by a different flow, opening or clicking it can still trigger a separate flow that uses Email Open or Email Click as its trigger.
Note: These loop-prevention rules apply specifically to email events used as flow triggers. They do not affect how these events are used as segmentation conditions in Segments.

Commercial Rights & Data Notes

Plan Requirements

Access to SmartPush Metrics depends on your subscription plan:

  • Segment conditions — Channel participation events (Email Send, Email Open, Email Click) and on-site behavior events (Page View, View Item) remain available to all plans, including free.
  • New behavioral events for Segments — Add to Cart, Remove from Cart, Continue Checkout, and View Item are Premium features and require a paid subscription.
  • All Metrics-type Flow triggers — Paid subscription required, regardless of event type.

Data Sync Range

Historical data availability varies by event type:

  • Order Create events: Full historical data is synced for the entire lifetime of your store.
  • On-site behavior events (PV-level): Data is available from January 1, 2025 onwards. When filtering on-site events, the earliest selectable start date is January 1, 2025.

Automation Logic

To prevent loops, emails sent or triggered by an automated flow will not re-trigger the same flow. See Using Metrics as Automation Flow Triggers above for the full loop-prevention rules.


Best Practices for Segmentation Filters

When creating audience segments, you may want to filter based on specific event or user attributes. Below are example use cases to illustrate how to apply filters effectively.

Use Case 1: Target One-Time Buyers of Product A Who Haven't Subscribed

A merchant allows customers to purchase "Product A" either as a one-time purchase or as a subscription. The merchant wants to target users who have purchased Product A but have not yet subscribed. By using SmartPush's segmentation filters, the merchant can create a segment for remarketing or set up an automation flow.

Steps to create an audience segment:

  1. Create a new audience segment. Under Contacts > Segments > Consumer Behavior > Purchased Product, select Product A.



  2. Exclude users who have already subscribed. Click Add Condition > App Integration > Subscription. Choose the event Subscription Contract Created. Set the trigger count and time range according to your business goals.
  3. Add an event attribute to further narrow the segment. Under the Subscription Contract Created event, add the attribute Subscribed Product = Product A.
  4. Generate the audience segment and rename it to reflect the use case, making it easier to select during campaign setup.
Note: You can add multiple attributes under the same event to refine your filters. However, make sure your conditions are not logically contradictory. For example, if you set "Next Subscription Cycle" between June 1–7, 2025, but also set the Start Date as after June 8, 2025, no users will meet both conditions and the segment will return empty results.

Steps to create an automation task:

  1. Create a segment named "Placed an order but not a subscription order."
  2. Create an automation task. Select the Contact Enters Segment trigger and choose the segment you just created.
  3. Drag in an email block, edit the email content, and activate the automation task.

Use Case 2: Re-Engage Customers Who Added Items to Wishlist but Didn't Buy

Scenario: A customer adds a product to their Wishlist but does not purchase it within 15 days.

Setup steps:

  1. Create a segment using the event Wishlist: Product Added to Wishlist.
  2. Add filter: Time Range = Past 15 Days.
  3. Exclude users who have placed an order for the same product.
  4. Trigger an automation flow that sends a reminder email with the specific product included via a product block.

Use Case 3: Reward Customers Who Leave Positive Product Reviews

Scenario: A customer submits a product review with a 5-star rating, and you want to reward them with a discount code.

Setup steps:

  1. Create a segment using the event Product Review Submitted.
  2. Add event attribute filter: Rating = 5 Stars.
  3. Use this segment in an automation that sends a "Thank You" email with a discount coupon.

Use Case 4: Target Members Who Recently Received a Gift Card

Scenario: A store uses the Member System app and wants to target customers who recently received a gift card from another member.

Setup steps:

  1. Create a segment using the event Member Gift Card Updated.
  2. Add event attribute filter: Source = Gifted by Others.
  3. Add filter: Time Range = Past 1 Day.
  4. Send an automation email recommending featured products the customer can purchase with their gift card.

By combining event filters from multiple apps — Subscription, Wishlist, Product Reviews, and Member System — you can design highly personalized and effective segmentation strategies that align with your business goals.

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request