1. What Is Frequently Viewed Products?

Frequently Viewed Products is a feature in Swym's Wishlist Plus app. It captures high-intent browse behaviour and sends it as events to your connected marketing platform. This includes Klaviyo, Omnisend, Attentive, and others.

Most tools react to a single product view. This feature tracks repeat views. It identifies shoppers who keep returning to the same product without buying.

A shopper who views a product detail page three or more times over two weeks is not casually browsing. They are considering. Frequently Viewed Products helps you reach them at exactly the right moment.

The Two Configurable Settings

The trigger runs on two settings you control.

View frequency. How many times a shopper must view a product to qualify. Examples: 3, 5, or 10 views. Views count across any timeframe. They do not need to happen in a single session.
Time delay. How long after the qualifying view before the event fires to your ESP. Examples: 30 minutes, 24 hours. If a shopper qualifies on multiple products within the same window, all can be included in one event. The delay starts from the final qualifying view.

Example. Configuration: 3 views, 30-minute delay

View 1. March 1 (any time)

View 2. March 8 (any time)

View 3. March 15, 2:00 PM. Shopper qualifies.

Event sent to Klaviyo. March 15, 2:30 PM. Flow triggers.

The goal is to give you more browse intent data. You can then retarget shoppers with the products they care about.

What Gets Sent to Your Connected Platform

Once a shopper qualifies, Swym sends a Swym-frequentlyViewed event to your connected platform. The event includes product name, image URL, product URL, and variant details for every product the shopper has qualified on.

One event can carry multiple products. Your email can show everything the shopper has repeatedly viewed in a single message. This keeps your outreach relevant without sending multiple emails per product.

Shopper Identity Requirement

Events only send for identified shoppers. A shopper must already be known to your connected platform. This happens when they log in, check out, save a wishlist, or opt in to marketing.

Anonymous browse activity is tracked by Swym. The event fires to your ESP once identity is resolved. If a shopper qualifies before their identity is known, the event sends as soon as it becomes available.

Shopper identity across integrations

Swym can identify shoppers who are not logged in through these connected integrations:

• Klaviyo

• Omnisend

• Ometria

For these platforms, Swym resolves identity using the email or profile data in your connected account. Anonymous browsers can be matched and retargeted once identified.

2. How It Works Alongside Browse Abandonment Flows

If you run a browse abandonment flow triggered by your ESP's Viewed Product metric, Frequently Viewed Products works as a complementary layer. The two tools serve different moments in the shopper journey.

ESP Viewed Product. Browse Abandonment	Swym Frequently Viewed Products
Fires on a single product view	Fires after multiple views. You set the threshold.
Session-level signal. What did they just look at?	Cumulative signal. What do they keep coming back to?
One product per event	Can include multiple products in one event
Best for immediate, session-based retargeting	Best for high-confidence re-engagement
Fires immediately at view time	Fires after a configurable delay post-qualifying view
Catches first-look interest	Catches sustained consideration

Together these tools give you full-funnel browse coverage.

Your ESP's Viewed Product catches the shopper right after they leave. Good for quick nudges while the product is fresh.
Swym Frequently Viewed fires later. It reaches shoppers who have shown repeat interest. This audience warrants a different message, such as a targeted offer or a personalised recommendation.

Run both flows in parallel with non-overlapping exit conditions. Add a condition so shoppers already in a Frequently Viewed flow are excluded from browse abandonment, and vice versa.

3. Platform Availability

Plan Requirement

Frequently Viewed Products is available on all paid Wishlist Plus plans. It is not available on the free plan. If you see a locked screen on the feature card, check your plan or contact Swym support to upgrade.

Trigger Availability

The self-serve setup UI is currently available for some integrations like Klaviyo, Omnisend, Swym’s inbuilt sender etc.. Other integrations like Ometria are available on request.

To enable Frequently Viewed Products for any platform, contact us.

• Email: [email protected]

• Book a call: meetings.hubspot.com/renuka-thakur

4. Setting It Up. Klaviyo

Setup runs in three stages. Enable the trigger in Swym. Send a test event so the metric appears in Klaviyo. Then build and activate your flow.

Step 1. Find the Feature in Wishlist Plus

In your Shopify Admin, go to Apps and open Wishlist Plus.
In the Wishlist Plus dashboard, click the Marketing tab.
Locate the Frequently Viewed Products card.
Click Set Up on the card to open the configuration panel.

Frequently Viewed Products is available on all paid Wishlist Plus plans. If you see a locked screen, check your current plan or contact Swym support.

Step 2. Configure View Frequency and Time Delay

View frequency. Set the number of views required for a shopper to qualify.
Time delay. Set how long after the qualifying view before the event fires to Klaviyo.
Click Turn On to enable the feature.

Recommended starting configuration

View frequency: 3 views | Time delay: 30 minutes

This works well for most stores. Adjust once your first events are flowing.

Step 3. Send a Test Trigger

Send a test event before building your flow. Klaviyo only shows a metric as a flow trigger after it has received at least one event.
In Wishlist Plus, go to the Integrations tab.
Click on your connected integration, for example Klaviyo.
Find the Test Triggers section.
Locate Frequently Viewed Products and click Send Test.
In Klaviyo, go to Analytics. Metrics and search for Swym-frequentlyViewed to confirm the event arrived.

If you do not see the metric in Klaviyo, contact [email protected]. We will set it up for you.

Do not skip this step. Without a test event, the metric will not appear as a flow trigger in Klaviyo.

Step 4. Build the Klaviyo Flow

With the metric available, set up your flow to send email, SMS, and push notifications to qualifying shoppers.

In Klaviyo, go to Flows. Create Flow. Build Your Own.
Name your flow, for example Frequently Viewed. Swym, and click Create.
Set the trigger. Choose Metric. Your Metrics and select Swym-frequentlyViewed.
Add a time delay node before the first message if you want extra buffer.
Add your email, SMS, or push notification action.
Add an exit condition. Exit the flow if the person has placed an order containing triggered products.
Set the flow to Live.

Building emails for multiple products

The event can include more than one product. Use a table block in the Klaviyo email editor rather than a single image and text block. Reference event properties to pull product name, image, and URL for each product dynamically.

Adding SMS and push notifications

The Swym-frequentlyViewed trigger works for SMS and push notification actions in the same flow. Add the action as a branch or a step. Use event properties to personalise the message with product names and direct links.

For support, contact Swym at [email protected] or book a call: meetings.hubspot.com/renuka-thakur

5. Setting It Up. Omnisend

The Omnisend setup is enabled by the Swym team on request. Once enabled, the process has three stages. Connect Omnisend in Swym. Send a test event. Then build and activate your automation.

Do not see the Frequently Viewed Products card for Omnisend? Contact [email protected] or book a call at meetings.hubspot.com/renuka-thakur. We will enable it for you.

Step 1. Find the Feature in Wishlist Plus

In your Shopify Admin, go to Apps and open Wishlist Plus.
In the Wishlist Plus dashboard, click the Marketing tab.
Locate the Frequently Viewed Products card.
Click Set Up on the card to open the configuration panel.

Frequently Viewed Products is available on all paid Wishlist Plus plans. If you see a locked screen, check your current plan or contact Swym support.

Step 2. Configure View Frequency and Time Delay

View frequency. Set the number of views required for a shopper to qualify.
Time delay. Set how long after the qualifying view before the event fires to Omnisend.
Click Turn On to enable the feature.

Recommended starting configuration

View frequency: 3 views | Time delay: 30 minutes

This works well for most stores. Adjust once your first events are flowing.

Step 3. Connect Omnisend in Swym

In Wishlist Plus, go to the Integrations tab.
Find Omnisend and click Connect.
Authorise the connection and grant the required permissions.
Return to the Marketing tab. Confirm the card shows Omnisend as connected.

Step 4. Send a Test Trigger

Send a test event so swym_frequentlyViewed appears as a custom event in Omnisend. Omnisend requires at least one event before you can use it as an automation trigger.

In the configuration panel, find the Test Trigger option.
Enter your email address. You must be a contact in Omnisend to receive the test.
Click Send Test.
In Omnisend, go to Store. Custom Events and confirm swym_frequentlyViewed has arrived.

If you do not see the custom event in Omnisend, contact [email protected]. We will set it up for you. Do not skip this step. Without a test event, the trigger will not appear in the automation builder.

Step 5. Build the Omnisend Automation

In Omnisend, go to Automation. New Workflow. Custom Automation.
Name your workflow, for example Frequently Viewed. Swym, and click Create.
Set the trigger. Choose Custom Event and select swym_frequentlyViewed.
Add a time delay before the first message if needed.
Add your email, SMS, or push notification action.
Add an exit condition. Exit if the contact has placed an order.
Set the workflow to Live.

For multiple products, use a Product block or HTML block in the Omnisend editor. Reference the event properties to populate each product card with name, image, and URL.

For SMS and push, add these as additional steps in the same workflow. Use the event properties to personalise the message with product names and direct links to product pages.

For support, contact Swym at [email protected] or book a call: meetings.hubspot.com/renuka-thakur

6. Setting It Up. Attentive

The Attentive setup is enabled by the Swym team on request. Once enabled, the process has three stages. Connect Attentive in Swym. Send a test event. Then build and activate your journey.

Do not see the Frequently Viewed Products card for Attentive? Contact [email protected] or book a call at meetings.hubspot.com/renuka-thakur. We will enable it for you.

Step 1. Find the Feature in Wishlist Plus

In your Shopify Admin, go to Apps and open Wishlist Plus.
In the Wishlist Plus dashboard, click the Marketing tab.
Locate the Frequently Viewed Products card.
Click Set Up on the card to open the configuration panel.

Frequently Viewed Products is available on all paid Wishlist Plus plans. If you see a locked screen, check your current plan or contact Swym support.

Step 2. Configure View Frequency and Time Delay

View frequency. Set the number of views required for a shopper to qualify.
Time delay. Set how long after the qualifying view before the event fires to Attentive.
Click Turn On to enable the feature.

Recommended starting configuration

View frequency: 3 views | Time delay: 30 minutes

This works well for most stores. Adjust once your first events are flowing.

Step 3. Connect Attentive in Swym

Attentive requires an OAuth connection through Swym before events can flow.

In Wishlist Plus, go to Integrations. Find Attentive and click Connect and Install.
Log in to Attentive and authorise the OAuth permissions.
In Attentive, go to Sign-up Units. Copy the unit IDs for your Marketing and Transactional units.
Enter both IDs in the Swym Attentive settings form and click Save.

Swym creates two sign-up units in Attentive on connection.

• Transactional unit: Swym Wishlist Plus Action Unit

• Marketing unit: Swym Wishlist Plus Promotional Unit

A shopper must be subscribed to your marketing or transactional messages before Attentive journeys triggered by Swym events will send.

Step 4. Send a Test Trigger

In the configuration panel, find the Test Trigger option.
Enter your email address. You must be a subscriber in Attentive to receive the test.
Click Send Test.
In Attentive, go to Journeys. Custom Events. Confirm swym_frequentlyViewed appears.

If you do not see the custom event in Attentive, contact [email protected]. We will set it up for you. Do not skip this step. The event must be received once before it appears as a trigger in Attentive.

Step 5. Build the Attentive Journey

In Attentive, go to Journeys. Create Journey. Build Your Own.
Name your journey, for example Frequently Viewed. Swym, and click Create.
Set the trigger. Choose Custom Event and select swym_frequentlyViewed.
Add your SMS, email, or push notification action.
Use event properties to personalise the message with the product name and a direct link to the product page.
Add an exit condition. Exit if the subscriber has placed an order.
Set the journey to Live.

For SMS: keep to one primary product per message. For email: use a dynamic product layout block with event properties for name, image URL, and product URL. For push: personalise the notification title and body. Use deep links to the product page.

You can run an SMS-only journey using the swym_frequentlyViewed trigger. The shopper must be subscribed to SMS marketing from your brand. If not, Attentive will skip the send.

For support, contact Swym at [email protected] or book a call: meetings.hubspot.com/renuka-thakur

7. Setting It Up. SwymSender

SwymSender is Swym's built-in email sender. It supports the Frequently Viewed Products trigger. You can send product-personalised emails directly from within Swym. No external ESP is required.

SwymSender support for Frequently Viewed Products is enabled on request.

• Email: [email protected]

• Book a call: meetings.hubspot.com/renuka-thakur

How SwymSender Works with Frequently Viewed Products

Once enabled, SwymSender listens for the Swym-frequentlyViewed trigger and sends the email automatically. You configure the template inside Swym's email editor. No Klaviyo or third-party account is needed.

Shopper identity. Emails only send to identified shoppers. These are shoppers who have logged in, saved a wishlist, or provided their email address.
Multi-product emails. SwymSender can show multiple frequently viewed products in a single email using Swym's built-in dynamic product blocks.
Plan requirement. Available on all paid Wishlist Plus plans.

For support, contact Swym at [email protected] or book a call: meetings.hubspot.com/renuka-thakur

8. Using a Different Marketing Platform?

Frequently Viewed Products currently works with Klaviyo, Omnisend, Ometria, and SwymSender. If you use a different platform, including Braze, Iterable, or ActiveCampaign, contact us. We will confirm compatibility and enable the connection for you.

• Email: [email protected]

• Book a call: meetings.hubspot.com/renuka-thakur

We will confirm compatibility, enable the feature, and walk you through the setup.

9. Troubleshooting

Issue	What to check
Swym-frequentlyViewed not in Klaviyo Metrics	Send a test trigger from Swym. The metric appears only after one event is received.
Feature card locked or not visible	This feature requires a paid Wishlist Plus plan. Contact support to confirm or upgrade.
Flow or automation not triggering	Confirm the trigger is set to Swym-frequentlyViewed, exact match. Check the flow is Live, not Draft. Confirm the feature is Live in Swym.
Product data missing in email	Check that your email template references the event properties correctly. Use your ESP preview with a real event.
Shopper received email after purchase	Add an exit condition to your flow: exit if the person has placed an order.
Shoppers in both browse abandonment and frequently viewed flows	Add exit conditions to both flows. If a shopper converts through one, exclude them from the other.