How Do I Build a Klaviyo Audience of People Who Abandoned a Specific Product?

Why this audience is difficult to build

A product can appear in Klaviyo Analytics without giving you a usable audience of the people who abandoned it. The distinction is:

• Analytics is for aggregate reporting.
• Lists & Segments is where profile-level audiences are built.
• Product-filtered abandonment requires an event condition plus a no-purchase condition.
• Anonymous activity is unavailable until it is tied to an identified profile.

That last point is the growth ceiling: even a correctly configured segment cannot include a shopper Klaviyo cannot identify.

Key takeaways

• Build audiences from events, not product reports. Product analytics can reveal demand, but event properties connect demand to profiles.
• Define abandonment explicitly. Product interest alone is not abandonment; the shopper must perform a qualifying event and then fail to purchase within a meaningful window.
• Use both cart and checkout intent when useful. Added to Cart captures earlier intent; Started Checkout is smaller but usually stronger.
• Exclude purchasers at the right level. Decide whether to exclude any order or only an order containing the same product.
• Expand identification before optimizing audience logic. Attribuly helps turn more qualified high-intent sessions into profiles and retargeting audiences.

If the underlying automation is still being built, start with the Klaviyo abandoned cart flow guide, then add the product-level audience logic below.

What is a product-specific abandoned cart audience?

A product-specific abandoned cart audience is a group of identified shoppers who added or checked out with a particular product but did not complete the qualifying purchase within a defined period.

It is different from three adjacent audiences:

• a general abandoned cart audience, which can include any product
• a product-view audience, which does not require cart intent
• a customer audience, which includes people who already purchased

This distinction matters because each audience supports a different message. A shopper who viewed a product may need education. A shopper who began checkout may need reassurance, urgency, or a return path to the cart.

Why product-level audience building matters

A general abandoned cart campaign treats all intent as interchangeable. Product-level segmentation lets marketers align creative, social proof, objections, inventory messaging, and offer logic with the item the shopper considered.

For example, a high-AOV product may need a longer decision window and more education. A replenishable product may benefit from benefits-led messaging. A limited-inventory product may need careful availability logic so the brand does not advertise an item that is no longer purchasable.

The segment also creates a bridge between lifecycle and paid media. The same qualified audience can support:

• a Klaviyo abandonment flow
• a Meta custom audience
• suppression of recent purchasers
• a product-line lookalike seed
• an analysis of product-specific recovery rate

Which Klaviyo event should you use?

> For most stores, Added to Cart OR Started Checkout provides broader product-abandonment coverage, while a separate checkout-only audience can be used for the highest-intent messaging.

How to build the segment in Klaviyo

Event labels and property names can vary by integration version and account. Inspect a recent profile event before copying any rule.

Step 1: Confirm that the product property exists

Open a recent Added to Cart and Started Checkout event in Klaviyo. Look for a stable property such as:

• Product ID
• Variant ID
• SKU
• Items or line items
• Product name or title

Prefer IDs or SKUs over names when practical. A product-title change can silently break a name-based segment.

Step 2: Choose the qualifying intent event

For a broad product-abandonment audience, use logic similar to:

What someone has done
Added to Cart at least once in the last 14 days
where Product ID equals [target product ID]

For stronger checkout intent, use:

What someone has done
Started Checkout at least once in the last 14 days
where Items contains [target product or variant]

If both event types carry usable product data, combine them with OR logic.

Step 3: Exclude completed purchasers

Add a negative condition:

AND
Placed Order zero times since the qualifying event

If your goal is to recover only the target product, consider whether the exclusion should apply to:

• any placed order; or
• an order containing the same product.

The first prevents messaging someone who bought a different item. The second keeps the target-product opportunity open. Choose based on customer experience, not audience size alone.

Step 4: Define the abandonment window

An audience without time boundaries accumulates stale intent. Match the window to the buying cycle.

• Short-consideration products may use a few days.
• High-AOV or researched products may use several weeks.
• Repeat-purchase products may need exclusions for subscription or replenishment timing.

Step 5: Preview real profiles

Inspect at least ten profiles in the segment. Verify:

• the target product is present
• the qualifying event occurred inside the window
• no disqualifying purchase occurred
• consent and suppression status support the intended channel
• the profile is not a test or internal address

Step 6: Choose email flow or paid-audience activation

A segment can support campaign sends and audience synchronization. For repeated abandonment, however, a metric-triggered flow may be more appropriate because a segment-triggered flow can have re-entry limitations.

Use the segment as the reusable audience definition; use event-triggered automation when timing and repeat behavior matter.

Why the segment may be smaller than expected

Reason 1: Anonymous visitors cannot populate profile segments

Klaviyo can report aggregate product activity without exposing every anonymous shopper as a usable profile. If a browser has not been identified, the activity cannot become a person-level segment member.

Impact: The segment logic may be correct while the reachable audience remains incomplete.

Reason 2: Product data is missing from the chosen event

Some Added to Cart implementations send only the item just added, while Started Checkout may contain a fuller cart. Custom themes, headless storefronts, or outdated integrations can also change the payload.

Impact: A product filter returns fewer profiles or the wrong profiles.

Reason 3: The store is filtering on a mutable product name

Renaming a product breaks an exact text match.

Impact: New events stop qualifying even though the product is unchanged.

Reason 4: The purchase exclusion is too broad or too narrow

Excluding every purchaser can remove someone who bought another product. Excluding only the target item can leave a recent customer eligible for an awkward message.

Impact: Audience size looks plausible while customer experience suffers.

Native segment vs identified audience expansion

> Visitor identification does not replace segmentation. It increases the number of qualified shoppers the segmentation logic can evaluate.

Where Attribuly fits

Attribuly Capture detects high-intent activity such as product views, add-to-cart, and extended browsing. When a qualified session can be matched through its consent-based identity network, Capture enriches the profile with behavior and purchase-intent signals, then syncs it to an ESP, Meta, or Google audience.

For shoppers who already exist in Klaviyo but whose current behavior is no longer associated with their profile, Attribuly ReCapture reconnects eligible abandonment activity and can trigger the brand's existing flows.

The practical distinction is:

• Capture expands the reachable audience with newly identified high-intent visitors.
• ReCapture reconnects current behavior to shoppers already known by the ESP.

Neither product removes the need to define the target product, abandonment window, purchase exclusion, consent policy, and cross-flow frequency controls.

> Choose the path that matches the identity gap. Use Capture to identify new high-intent visitors, or use ReCapture to reconnect abandonment behavior to existing Klaviyo profiles.

How to activate the audience without creating a bad customer experience

Use channel-specific eligibility

An identifiable email address is not automatically permission for every marketing channel. Keep consent status, suppression status, and geographic rules in the activation logic.

Coordinate email and paid media

Do not run two disconnected messages forever. A practical sequence is:

1. Enter the email flow when the profile is eligible.
2. Add the shopper to the paid retargeting audience.
3. Remove or suppress the shopper after purchase.
4. Expire the audience after the intent window.
5. Measure incremental recovery by channel and combined exposure.

Match creative to the product and funnel stage

Use the product the shopper actually considered. Avoid generic "You left something behind" creative if the event payload supports a more relevant message.

Common mistakes

Mistake 1: Looking for profiles inside Analytics

Why it matters: Product reports answer performance questions, not person-level audience questions.

What to do instead: Build the audience in Lists & Segments from event properties.

Mistake 2: Calling every product viewer an abandoner

Why it matters: View intent and cart intent are not equivalent.

What to do instead: Create separate view, cart, and checkout audiences with different messages.

Mistake 3: Filtering by a product title that changes

Why it matters: Editorial updates can break the segment.

What to do instead: Prefer product ID, variant ID, or SKU where available.

Mistake 4: Forgetting purchaser suppression

Why it matters: Customers continue seeing an abandonment message after buying.

What to do instead: Exclude purchasers quickly in both Klaviyo and paid destinations.

Mistake 5: Optimizing a perfect segment on incomplete identity data

Why it matters: The best rules cannot include shoppers who remain anonymous.

What to do instead: Measure the share of product-intent events connected to usable profiles, then evaluate whether compliant visitor identification can expand coverage.

Next step

Build the native segment first and inspect real profiles. Then measure the missing layer: how many high-intent product sessions never become identified audience members? That number tells you whether the biggest opportunity is better segmentation or broader identity coverage.

> How much product demand is currently unreachable? Run the shopper identification audit to compare your store with relevant industry data and estimate the revenue opportunity from better identification before installing another tool.

> Ready to activate the audience? Start your Attribuly trial to test product-intent audiences across Klaviyo and paid channels.

Related reading

• How to update Klaviyo flows after implementing visitor ID
• Connect behavior data to your Klaviyo abandoned cart flow
• Shopify visitor identification guide
• Klaviyo abandoned cart flow guide