Browse abandonment email setup services

How a browse email project runs

1. 01

   Consent check

   Cookie consent, tracking script and privacy notice reviewed with you.

   Output: Consent notes

2. 02

   Trigger rules

   Minimum views, frequency cap, exclusions.

   Output: Rules

3. 03

   Content

   One helpful email per category or product type.

   Output: Approved copy

4. 04

   Build and test

   Including a test with consent refused.

   Output: Test record

5. 05

   Review

   Clicks, orders, unsubscribes, complaints.

   Output: Review

The consent check

Browse tracking typically uses cookies or similar technology to recognise subscribers. The service should list what tracking would be added, check how your cookie banner handles it, test that tracking does not run when a visitor refuses consent and suggest what your privacy notice may need to say. It should not decide the legal position for you; it should give you and your adviser the facts needed to decide.

Trigger rules agreed

Content that helps

The service should write one email per product category or service type, sharing something useful: a choosing guide, popular items, care information or common questions. It should avoid phrases that tell people they were tracked, avoid discounts and keep the email short. Product blocks should show accurate prices and availability at the time of sending.

Warning signs in a browse email service

• Consent not mentioned

  Tracking switched on without checking.

• 'We saw you looking'

  Wording that feels intrusive.

• No frequency cap

  An email after every visit.

• Built before basket reminders

  Lower-intent flow first.

Example: browse emails for an outdoor clothing shop

What you should receive

Reviewing results

After a month or two, the service should report clicks, orders, unsubscribes and complaints from browse emails compared with your other flows. If unsubscribes or complaints are noticeably higher, the trigger may be too loose or the wording too pointed, and the service should recommend tightening or pausing.

Briefing the service

Share your shop and email platforms, how your cookie banner is set up, your privacy notice, product categories and any guides you already have. Mention which other flows are already running.

Order of priority

A careful service would suggest getting welcome, basket and post-purchase flows working first, since they respond to stronger signals of interest. Browse emails then sit on top as a gentle extra. If a service proposes browse emails before the basics are in place, ask why.

Keeping product details accurate

Product blocks should show prices and availability as they are when the email is sent. The service should test what happens when a viewed product sells out or changes price, and make sure the email either leaves it out or suggests an alternative. Stock claims should only appear if the data is live.

Ownership and access

The flow should be built in your email platform account, and any tracking setting changed on your website should be documented so your developer knows what was done. Remove any temporary access once the work is finished.

Approving the wording

Because browse emails can feel personal, read every draft as a subscriber would. If a sentence makes you feel watched, ask for it to be changed. You have final say on tone.