Tracking and lifecycle email that turn attention into revenue.

Meta pixel and Conversions API tracking, sent server-side so Meta and Google see who really bought, and lifecycle email wired to real attribution. Welcome, nurture, cart recovery and reactivation flows, so you know which channel pays.

What is lifecycle email marketing?

Lifecycle email marketing is a set of automated flows triggered by customer behaviour rather than by a calendar. Welcome, abandoned cart, post-purchase, win-back and reactivation sequences run continuously in the background, recovering revenue from people who already showed intent but did not complete a purchase.

Best for

  • Ecommerce brands losing revenue to abandoned carts and one-time buyers
  • Businesses spending on ads without knowing which spend converts
  • Companies with an email list they have never properly used
  • Teams whose analytics and ad platform numbers never agree with each other

What we set up

Lifecycle email flows

Welcome, abandoned cart, browse abandonment, post-purchase, win-back and reactivation sequences built in Klaviyo or Brevo, segmented by behaviour and language.

Meta pixel and Conversions API

The Meta pixel and the Conversions API (CAPI), GA4 and Google Tag Manager configured server-side, so conversions still register when browsers block client-side pixels.

Attribution you can trust

Channel attribution wired end to end, so email, paid and organic each get credit for what they actually drove instead of every platform claiming the same sale.

Ads, as a Monthly Growth add-on

Meta and Google campaigns as an add-on to monthly growth, only for clients whose tracking and follow-up we have set up, so the ads optimise on real revenue rather than platform-reported ROAS. Never on their own. Ad spend is paid by you, on top.

Landing pages and funnels

Dedicated pages matched to the ad or email that sent the visitor, so message and page stay consistent through to conversion.

Segmentation and list health

Suppression rules, engagement segments and deliverability hygiene, so your sending reputation holds up as volume grows.

How we deliver it

  1. Audit what exists We review your current tracking, flows and ad spend, then quantify exactly what is leaking. Almost every account we open has recoverable revenue sitting in a half-finished flow somebody started and never switched on.
  2. Fix measurement first Tracking and attribution get fixed before we touch a single campaign. Optimising against broken data does not just waste budget, it actively makes your decisions worse, because you start confidently scaling the wrong thing.
  3. Build the flows We build the highest-value sequences first, usually cart recovery and welcome, because those capture demand that already exists and pay back fastest. Nurture, post-purchase and win-back follow once the money-makers are live.
  4. Test and scale We iterate on subject lines, send timing, segments and creative, then scale what wins. Reporting is monthly and tied to revenue, so you always know which channel earned its budget and which one only looked busy.

What an email marketing agency builds, and why tracking comes first.

What does an email marketing agency do?

An email marketing agency builds and runs the email a business sends automatically and on a schedule: welcome, abandoned cart, post-purchase, win-back and reactivation flows, plus campaigns, segmentation, deliverability and the reporting that shows what each email earned. For stores that means Klaviyo. For service businesses it means Brevo.

Flows do most of the work. Klaviyo's 2026 abandoned cart benchmarks put the average abandoned cart email flow at $6.77 in revenue per recipient. Flows and campaigns are measured against the same purchase data the ad platforms see, which is why the Meta pixel, the Conversions API and the analytics setup belong to the same agency as the email.

Proof of Pixel is a marketing and consulting agency for businesses that live on enquiries and orders, building the website, the tracking and the follow-up as one system, with offices in Dubai, New York, London, Antwerp and Kuala Lumpur.

Which lifecycle email flows recover the most revenue?

Abandoned cart and welcome flows recover the most revenue, because they reach people who already showed intent. Post-purchase flows raise repeat orders, win-back flows bring back lapsed buyers, and browse abandonment catches people who looked without adding to cart. Build in that order and the first two flows pay for the rest of the programme.

Baymard Institute's 2025 average across 50 studies puts cart abandonment at 70.22%, so seven in ten carts leave without paying. The results on the work page come from this kind of build: DC Greater Goods saw "+37% in repeat orders with new email and SMS flows", and the Decrypting dashboard project saw "+52% email revenue after a full-flow overhaul".

The flows, in build order:

  • Welcome: the first three emails after signup, with the offer, the story and the top products
  • Abandoned cart: one to three emails over 48 hours, with the cart contents and the delivery answer
  • Browse abandonment: one email for products viewed twice without a cart
  • Post-purchase: delivery expectations, how to use the product, a review request, a cross-sell
  • Win-back: for customers past their usual reorder window
  • Reactivation and sunset: re-engage quiet subscribers, then suppress them to protect deliverability

What is the Meta Conversions API?

The Meta Conversions API, or CAPI, sends conversion events from your server to Meta, alongside the Meta pixel in the browser. The pixel misses events when ad blockers, iOS privacy settings or consent choices stop it. CAPI sends the same purchase, lead or signup from the server, so Meta sees what happened and can optimise and report on it.

Three parts make it work. Deduplication: the pixel and the server send the same event with a shared event ID, so one sale counts once. Event match quality: hashed email, phone and name on the server event, so Meta can match it to a person. Parameter consistency: the same value, currency and content IDs on both sides.

What is server-side tracking, and do you need it?

Server-side tracking runs your tags from a server you control. A Google Tag Manager server container on Stape receives each event once and forwards it to Meta, Google Ads and GA4. You need it when ads are a real budget line and the platform numbers, the analytics and the orders in your store disagree.

The benefits are data quality and control: fewer lost events, first-party cookies that last longer, one place where every conversion is defined, and consent handled once before anything is sent. In the accounts we open, the same fault shows up: the pixel and a server event both firing for the same purchase with no shared event ID, so the ad platform reports more sales than the store took.

How is lifecycle email set up, step by step?

Lifecycle email is set up in six steps: audit the account, fix the tracking, connect the data, build the highest-value flows first, test, then scale. The order matters, because a flow built on wrong purchase data optimises toward the wrong customers and reports revenue it did not earn, and nobody finds out until the ad budget has followed it.

The results on the work page come from this order of work. Hertebos, which takes bookings through its website, saw "2× more booking enquiries through follow-up emails". A Belgian Shopify store saw "Conversion rate up 39%, 45.21% returning buyers" once the flows and the tracking ran on the same data.

  1. Audit the current flows, list, segments, sending domain and the half-built automations nobody switched on.
  2. Fix measurement: Meta pixel plus Conversions API with deduplication, and GA4 and Google Ads conversions through a server container.
  3. Connect Klaviyo or Brevo to the store or CRM, with consent and language captured at signup.
  4. Build abandoned cart and welcome first, then post-purchase, win-back and reactivation.
  5. Write and design each email in the brand's voice, with one call to action per email.
  6. Test subject lines, timing and segments, then scale what the revenue report shows is working.

Platforms we work in

Klaviyo, Brevo, Meta Ads, Google Ads, TikTok Ads, Google Tag Manager, Google Analytics 4, Meta CAPI, Shopify, NinjaPipe

Proof

All work

Frequently asked questions

Which is better, Klaviyo or Brevo?

Klaviyo is stronger for ecommerce, with deeper Shopify integration and better product-level segmentation. Brevo is more cost-effective at volume and fits service businesses well. We pick based on your model, with no preferred vendor.

Why do my ad platform and analytics numbers never match?

Ad platforms and analytics measure differently: ad platforms use view-through and platform-side attribution windows, analytics uses last-click sessions. Both are partly wrong on their own. Server-side tracking plus a single agreed source of truth is what closes the gap.

How long before lifecycle flows pay for themselves?

Cart recovery and welcome flows usually produce measurable revenue within the first month. Nurture and reactivation take longer, since they depend on list size and buying cycle.

Do I need a big email list for this to work?

No, you do not need a big email list: flows are triggered by behaviour, so they work proportionally at any list size. A small engaged list with proper cart recovery usually outperforms a large neglected list receiving occasional broadcasts.

Can you fix an existing Klaviyo or Brevo account instead of starting over?

Yes, and that is the usual starting point. The audit lists which flows run, which were started and never switched on, and which segments and sending settings hurt deliverability. We keep what works, rebuild what does not, and connect the whole account to verified purchase data.

Every answer about Proof of Pixel, on one page

Comparisons

  • Brevo vs Klaviyo What each costs at your list size, how they work with Shopify, and which one a business that lives on enquiries needs.
  • Brevo vs Mailchimp What each costs at your list size, the free plans after 2025's cuts, where your data lives, and what moving from Mailchimp takes.
  • Pixel vs Conversions API Why Meta wants both, how deduplication works, what consent still blocks, and which setup fits a store or a business on enquiries.
  • Tag gateway vs server-side GTM What Google's free gateway changes, what a server container adds, what each costs, and why Google recommends both.
  • Stape vs Google Cloud Where to host a server-side Tag Manager container: what each costs at small-business traffic, what each leaves to you, and how to switch.
  • Consent Mode basic vs advanced What each mode sends before and after a choice, what Google models back, the open legal question, and why neither covers Meta.

Related services

Free field guide

Meta says 500. Shopify says 350. Find out how far your ad numbers are off, and fix it in an afternoon.

Guides on Marketing