Merging Anonymous Activity in Customer.io

Overview

Merging anonymous activity in Customer.io is how you connect pre-purchase behavior (like product views, quiz results, and cart building) to a known shopper once they identify themselves (email capture, account creation, or checkout). For D2C retention teams, this is the difference between sending generic browse follow-ups and sending high-intent messages that reflect what someone actually looked at before they bought or abandoned.

Scenario: a shopper lands from TikTok, views three SKUs in your “Sensitive Skin” collection, adds one item to cart, then bounces. The next day they enter their email via a back-in-stock modal or start checkout. If you merge anonymous activity correctly, your abandoned cart and product discovery journeys can reference those earlier views and cart actions, improving first purchase conversion and reducing wasted sends.

If you want this wired cleanly across web events, identity capture, and lifecycle orchestration, Propel helps teams operationalize Customer.io quickly, you can book a strategy call.

How It Works

Merging anonymous activity in Customer.io works by tracking events against an anonymous identifier first, then linking that history to a known person profile when you later identify the shopper.

In practice, your site sends events like Product Viewed, Collection Viewed, Added to Cart, or Checkout Started before you know who the shopper is. Customer.io stores those events under an anonymous profile. When the shopper submits an email (newsletter popup, quiz result email gate, checkout email step, account creation), you call the identify step so Customer.io can associate the anonymous profile and its event history with the known customer profile. From that point forward, segmentation and Journeys can use the full behavioral context.

Most D2C issues here come down to identity timing. If you identify too late (after purchase), you lose the window where browse and cart recovery messages are most valuable. If you identify inconsistently (multiple IDs per device), you fragment the history and your triggers underperform. If you are running this through a CDP, make sure the same identity rules apply before events hit Customer.io.

Step-by-Step Setup

Merging anonymous activity in Customer.io becomes reliable when you standardize three things: anonymous ID creation, event tracking, and the moment you identify the shopper.

1. Define your identity moments. List every place you collect an email or customer ID (newsletter popup, quiz gate, SMS capture, checkout email step, account creation, post-purchase account invite).
2. Implement anonymous event tracking on key storefront actions. Track at minimum: product viewed, added to cart, checkout started, and order completed. Include useful properties like SKU, product name, variant, price, quantity, collection, and cart value.
3. Ensure your site generates a stable anonymous identifier. Use a first-party cookie or local storage approach that persists across pageviews and sessions (within your privacy policy and consent rules).
4. Send events against the anonymous profile until identification. Confirm in your event debugger or logs that pre-email events are arriving as anonymous, not dropped or misattributed.
5. Identify the shopper immediately when you capture email. At the exact moment email is submitted, call identify so the anonymous profile merges into the known person.
6. Validate the merge using a real journey. Run a test: browse product, add to cart, then submit email. Confirm the known profile shows the earlier events and triggers the right cart recovery flow.
7. Update your journey triggers to rely on merged context. For example, abandoned cart can trigger on Checkout Started and use cart contents from event properties, even if the email was captured after the cart was built.

When Should You Use This Feature

Merging anonymous activity in Customer.io is most valuable when your revenue depends on turning high-intent browsing into first purchases and shaping second purchases based on what shoppers explored.

• Abandoned cart recovery when email capture happens late. If shoppers often enter email at checkout or via a popup after browsing, merging ensures cart and browse events still power your recovery messages.
• Product discovery journeys. Use viewed collections, quiz outcomes, or PDP engagement to send tailored recommendations once the shopper identifies.
• Welcome offer personalization. Instead of a generic “10% off,” you can feature the last viewed category or the exact SKU they added to cart.
• Post-purchase upsell relevance. If a shopper viewed complementary products before buying, you can use that intent to shape cross-sell messaging after delivery.
• Reactivation based on historic intent. When lapsed customers return and browse anonymously, merging helps you treat them like a returning buyer, not a net-new lead.

Operational Considerations

Merging anonymous activity in Customer.io touches data flow, segmentation hygiene, and how your journeys behave under real storefront conditions.

• Consent and privacy. If you operate in regions with strict consent requirements, ensure anonymous tracking and identification only occur when permitted. Align cookie consent tooling with event collection.
• Identity hierarchy. Decide your source of truth (email, customer ID, Shopify customer ID). Keep it consistent across web, ESP, and any CDP to avoid duplicate profiles.
• Event property standards. Cart and product events should share a consistent schema so templates and segments do not break (for example, always include sku, variant_id, price, quantity).
• Journey entry timing. If a journey triggers on an anonymous event, confirm it can still send once the person becomes known. Many teams prefer triggering once identification happens, then referencing the recent anonymous activity.
• Deduplication rules. If your ecommerce platform also sends server-side order events, ensure you are not double-sending purchase events, which can cause premature journey exits and inaccurate attribution.

Implementation Checklist

Merging anonymous activity in Customer.io goes smoothly when you can check off the basics before you build campaigns on top of it.

• Anonymous ID persists across sessions and pageviews (within your consent policy)
• Key events tracked pre-identification (product viewed, added to cart, checkout started)
• Email capture points trigger identify immediately
• Known profiles show historical anonymous events after identify
• Cart and product event properties follow a consistent schema
• Abandoned cart and browse journeys are tested end-to-end with real storefront behavior
• Purchase events are deduped across client-side and server-side sources

Expert Implementation Tips

Merging anonymous activity in Customer.io is where strong D2C programs separate “we send flows” from “we send the right message at the right moment with the right context.”

• Identify earlier than checkout when possible. In retention programs we’ve implemented for D2C brands, moving identity capture to a high-intent moment (quiz results, back-in-stock, or a value-led email capture) improves both merge rates and abandoned cart revenue because you can message before the shopper cools off.
• Use a short “pre-merge buffer” in journeys. If you trigger on a cart event, add a brief delay (for example, 5 to 15 minutes) before sending the first message. This gives time for identification to occur so the message can personalize with full cart details.
• Store cart contents in the event. Do not rely on rebuilding the cart later from your storefront. Put line items into the Added to Cart or Checkout Started payload so templates stay accurate even if the cart changes.
• Segment by intent depth, not just “viewed product.” Create tiers like: viewed PDP twice, added to cart, started checkout. Then tailor incentives and urgency accordingly.

Common Mistakes to Avoid

Merging anonymous activity in Customer.io often fails quietly, then teams wonder why browse and cart flows feel generic or underperform.

• Identifying only after purchase. That turns anonymous browsing into unusable history for first purchase conversion and cart recovery.
• Creating multiple anonymous IDs per shopper. If your ID resets on each visit or across subdomains, you fragment intent and personalization breaks.
• Triggering journeys on anonymous events without a plan for identification. You end up with people entering flows who cannot be messaged yet, or messages that lack key context.
• Inconsistent event schemas. If one event uses product_id and another uses sku, your liquid logic becomes brittle and QA time balloons.
• Double-counting orders. Two purchase events can cause incorrect conversion metrics and premature exits from post-purchase journeys.

Summary

Merging anonymous activity matters when you want browse, cart, and checkout behavior to personalize messages the moment someone becomes reachable. Use it to lift first purchase conversion and make recovery flows more relevant inside Customer.io.

Implement with Propel

Propel can help you implement merging anonymous activity end-to-end in Customer.io, from event schema to identity capture and journey QA. If you want it set up to drive revenue quickly, book a strategy call.