Understanding SmartPush Metrics (for SHOPLINE Merchants)

SmartPush
SmartPush
  • Updated

 

SmartPush Metrics allows you to leverage synced data from your store to build audience segments and trigger automations. This article explains the core concepts, behavioral events (such as Add to Cart and Checkout),  and how to use these metrics to implement precision marketing strategies.

Note: This article is for SHOPLINE merchants only.

 


 

Concept Overview

Before you begin analyzing event data, it’s important to understand several key concepts used in the configuration of metric-based reports. This will help you better interpret how SmartPush tracks and analyzes user behavior.

 

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, 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
Filter Filter 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. The following events are now available for deeper analysis and automation: 

 1. Email Engagement (Channel Participation) 

  • Sent Email (Coming Soon): Recorded when an automation or campaign email is sent. 
  • Open Email (Coming Soon): Recorded when a recipient opens your email. 
  • Clicked Email (Coming Soon): Recorded when a recipient clicks a link within your email. 

 2. On-site Behavior (Website Events) 

  • View Item (Coming Soon): When a customer visits a product detail page. 
  • Search (Coming Soon): When a customer performs a search on your store. 
  • View Cart: When a customer visits the shopping cart page. 
  • Add to Cart: When a customer adds an item to their cart. 
  •  Continue Checkout: When a customer enters the checkout process (triggers abandoned checkout logic). 
  • Order Create: When an order is successfully placed. 

Metric Operators

SmartPush supports analyzing all events by their trigger count and time range, helping you determine how often an event occurred within a specified timeframe.

  • Trigger Count: If you simply need to check whether an event occurred, use ≥ 1.
  • Time Range Options:
    • Cumulative: Event occurred at any time in the selected period.
    • Time Range: Event occurred within a specific start and end date (up to 12 months).
    • Start Time: Event occurred after a specific date (up to 12 months).
    • End Time: Event occurred before a specific date (up to 12 months).
    • Past X Days: Events occurred within the past X days (1–180 days supported).
       

Commercial Rights & Data Notes  

  • Plan Requirements: Basic engagement events (Email Open/Click) remain available for all plans. However, new behavioral events (Add to Cart, View Item, Checkout, etc.) are Premium Features and require a paid subscription.  
  •  Data Sync Range: For historical On-site events, data is synced back to July 2024. Order Create data is synced for the entire history of the store.  
  •  Automation Logic: To prevent loops, emails sent/opened via an automated flow will not re-trigger the same flow.

Best Practices for Segmentation Filters

When creating audience segments, you may want to filter based on specific event or user attributes. Below is an example use case 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 using SmartPush segmentation:

  1. Create a new audience segment and set a condition for it:
    • Under Contacts > Choose SegmentsConsumer behavior > Purchased product > Select Product. 



  2. Exclude users who already subscribed:
    • Click Add Condition > Select 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 attribute: Subscribed Product = Selected Product Name.
  4. Generate the audience segment and rename it to reflect the use case, making it easier to select during campaign setup.
     

You can add multiple attributes under the same event to refine your filters. However, ensure your conditions don’t logically contradict each other.

For example:
If you set the filter "Next Subscription Cycle" between June 1–7, 2025, but also specify 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 called Placed an order but not a subscribed.
  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 then activate the automation task.

 

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

Scenario:  When customers add a product to their Wishlist but don’t purchase it within 15 days.

Setup Steps:

  1. Create a segment with Wishlist: Product added to wishlist event.
  2. Add filter Time range = Past 15 days.
  3. Exclude users with Order purchased  matching the Wishlist item.
  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: Customers submit product reviews with a 5-star rating, and then 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 received a gift card as a present from another member.

Setup Steps:

  1. Create a segment with Member Gift Card Updated event.
  2. Add event attribute filter Source = Gifted by others.
  3. Add Time Range = Past 1 day.
  4. Send an automation email encouraging them to use the gift card on featured products.

By combining event filters from multiple apps (Subscription, Wishlist, Product Reviews, 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