Understanding SmartPush Metrics (for SHOPLINE Merchants)

 

SmartPush Metrics allows you to leverage synced data from your store to build audience segments and trigger automations. This article explains the core concepts and how to use these metrics to implement precision marketing strategies.

Note: This article is for SHOPLINE merchants only.

 

In This Article

 


 

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.

Concept Description
Event An 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.
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.
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".

 


 

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).
       

 

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 : Target One-Time Buyers of Product A Who Haven’t Subscribed

A merchant offers Product A with options for one-time purchase or subscription. They want to target customers who have bought certain product  once but haven’t subscribed yet.

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.

Have more questions? Submit a request

Comments