Blog
Guides10 min read

Lifecycle Marketing Attribution Without an MMP: From Email Click to In-App Revenue

Your email platform knows who clicked. Your app knows who bought. Almost nobody joins the two. Here's how to use LinkForty as the attribution layer for lifecycle campaigns: links that open the app, credit that follows the tap, and revenue reported per campaign.

LinkFortyLIFECYCLE MARKETING / GUIDEFrom email clickto in-app revenueLifecycle attributionwithout an MMP.Know which link brought them back.See what happened after the tap.Report conversions by campaign.EMAIL / DEEP LINKING / CONVERSIONSTHE ATTRIBUTION JOURNEY01 EMAIL CAMPAIGNWin-back email · CTA link02 APP OPENDeep link → right screen03 ATTRIBUTED EVENTpurchase · revenue + currencyLAST-CLICK CREDITThe most recent LinkForty link gets credituntil another LinkForty link opens the app.

The question your lifecycle stack can't answer

You run a win-back email on Tuesday. By Friday the email platform says 4,000 opens and 600 clicks. Your product analytics says purchases were up that week. The question everyone actually wants answered is the one in between:

Which of those purchases came from the email, and which link in it?

Most lifecycle teams can't say. The email platform stops counting at the click. The app's analytics starts counting at the session, with no idea a link was involved. The join between them is a spreadsheet someone builds once and never updates.

There's a second problem hiding under the first. The click your email platform counted probably didn't open your app at all.

Why mobile measurement partners don't solve this

The usual answer to "attribution" is a mobile measurement partner (MMP). MMPs are built to answer an acquisition question: which ad network earned this install? They're good at it, priced for it, and wired into ad networks for it.

Lifecycle marketing asks a different question. The people you email already have your app. You aren't paying an ad network, and there's no install to credit. What you need is:

  1. The link in the message has to open the app, on the screen the message promised.
  2. Whatever the user does next (subscribes, buys, finishes onboarding) has to be credited to that link.
  3. The result has to roll up by campaign, next to every other channel.

That's a link problem before it's an analytics problem, and it's the part LinkForty is built for.

How LinkForty credits a lifecycle click

Here's the model in one paragraph, because everything else builds on it.

Every time a LinkForty link opens your app, the SDK records which link it was. Every in-app event the app sends afterward carries that link, and LinkForty credits the event to it. When a different link opens the app later, that one takes over. If the app wasn't installed, the user goes to the store, and when they first open the app the install is matched to the click and the user lands on the content they tapped (deferred deep linking). Their later events are credited to that link.

That's last-click attribution: the most recent link to open the app gets the credit. It's simple, it's predictable, and it answers "what did this email produce?" without a data team.

Three details matter for lifecycle work:

  • Credit stays until another link replaces it. A user who taps your Tuesday email and buys on Saturday is credited to the Tuesday email, as long as no other LinkForty link opened the app in between.
  • Re-engagement counts. A user who installed from an Instagram ad in March and taps your win-back email in November is credited to the email for what they do now, not to the ad.
  • No device IDs. None of this uses IDFA or GAID, and there's no App Tracking Transparency prompt.

This is the step most teams skip, and it quietly breaks everything after it.

Email platforms track clicks by rewriting every link in the message to point at their own tracking domain, which then redirects to your real link. On iOS, a Universal Link reached through a redirect often doesn't open the app. Safari is forgiving. Chrome on iOS, Gmail, Outlook and most in-app browsers aren't: they send the reader to the App Store or the website instead, even though the app is installed. (The in-app browser problem, in more detail.)

The fix is to put the LinkForty link in the email directly and turn off the email platform's click tracking for those messages.

Turning off click tracking doesn't mean losing clicks. LinkForty counts the tap either way: on its server when the link goes to the store or the web, and through the SDK when it opens the app. LinkForty Cloud also has email connectors for OneSignal, Braze, Iterable, MoEngage and CleverTap. You add the platform's user-ID merge tag to each link, for example:

https://yourapp.toapp.me/winback-hero?braze_id={{${braze_id}}}

When a subscriber taps that link, LinkForty sends a linkforty_click event to their profile in your email platform. A click that reaches LinkForty's server (the app isn't installed, the reader is on a desktop, or an in-app browser skipped the Universal Link) is always sent. A click that opens the installed app is sent when the app runs a recent LinkForty SDK: React Native or Expo 1.11.0, iOS or Android 1.9.0, or Flutter 0.7.0 or later. Setup for each provider is in the email link tracking guide.

Attribution is only as specific as your links. If every email in a series points at the same link, LinkForty can tell you the series worked, not which email did.

Give each message its own link, and each placement inside a message its own link when the placement matters: the hero button and the footer link are different links. Tag them so they roll up:

UTM fieldExampleWhat it groups
utm_campaignwinback_novThe whole series
utm_mediumemailEmail next to SMS, social and paid
utm_sourcebrazeThe platform that sent it

A link template holds the store and web URLs, UTM tags and attribution windows for a series, so every new link starts from the same defaults. The UTM Library lists every value you've used, with counts, so a stray Email next to email is easy to spot before it splits a campaign into two rows.

The same goes for SMS. A text message with a LinkForty link works the same way, and utm_medium=sms puts it in its own row.

Step 3: Send the events that mean money

Clicks tell you the message was interesting. Events tell you it worked. Have the app send the moments you care about:

await LinkForty.trackEvent('subscription_started', {
  plan: 'annual',
  revenue: 49.99,
  currency: 'USD',
});

Two things to get right:

  • Revenue is read from the revenue property, with a currency code. LinkForty reports revenue per currency and never converts between them. A refund the app sends as a negative revenue is subtracted, so totals are net. Send refunds with trackEvent (for example trackEvent('refund', { revenue: -49.99, currency: 'USD' })): the trackRevenue() helper rejects negative amounts.
  • Mark your goals. In the Event Library, mark the events that count as conversions (subscription_started, purchase, onboarding_complete). Conversion reports then show those events, not every screen view.

If the email sends people to your website instead of the app, add the web pixel. LinkForty adds a click ID (lf_click) to web destinations, and the pixel credits the visit and any conversion in it to the link. The credit lasts for that browser tab's session, up to 7 days after the click.

Step 4: Read it by campaign

With links tagged and events flowing, three reports answer the lifecycle questions.

Analytics → Campaigns gives one row per campaign, source or medium: clicks, installs, website sessions, conversions, and app and web revenue per currency, side by side. Open a row to see its daily trend, the links that carried it, and the latest conversions one by one, with the link and value of each. This is where winback_nov gets compared with onboarding_d3 and with your paid campaigns.

Events → Conversions reports each goal by the link that brought the user: completions, conversion rate, value, and the median time from click to completion. For lifecycle teams, the time column is useful on its own. A win-back email that converts in 40 minutes and one that converts over four days are different emails.

Day views answer "what happened on Tuesday?" Click any day on the conversions or installs chart and you get that day's completions, each credited link, and the individual events.

Everything above is in the date range you pick. A purchase on Saturday from a Tuesday click shows up when Saturday is in the range.

Step 5: Send the results back to your lifecycle stack

Attribution is more useful when your other tools can act on it.

  • Your email platform gets the linkforty_click event from Step 1, on the user's profile. Use it the way you'd use any custom event.
  • Webhooks send clicks, attributed installs and conversions to your own endpoint, signed with HMAC-SHA256. That's the route into a warehouse or an internal tool. (Webhooks guide.)
  • Analytics integrations forward clicks, installs and events to Segment, Mixpanel, Amplitude, PostHog, Google Analytics 4, CleverTap, Zapier, n8n or Slack, so the link sits next to the rest of the user's history. (Integrations guide.)

What this is, and what it isn't

Last-click attribution answers one question well: which link most recently brought this user in, and what did they do? It's worth being clear about the questions it doesn't answer.

  • It isn't multi-touch. If a user reads three emails and buys after the third, the third gets the credit. LinkForty doesn't split credit or weight earlier touches.
  • It isn't incrementality. Credit means the user tapped the link and then converted, not that they wouldn't have converted without it. For "did this campaign cause extra revenue?", run a holdout group in your email platform and compare it with the LinkForty numbers for the people who got the email.
  • It isn't cross-device. A tap on a laptop and a purchase on a phone are two different journeys.
  • It doesn't see taps on other links. A user who opens the app from the home screen after your email is still credited to the email, until another LinkForty link opens the app.

None of that makes last-click weak. It makes it legible. When a number on the Campaigns page looks wrong, you can open the row and see the actual events behind it.

A checklist for your next campaign

  • Click tracking is off in your email platform for this message.
  • Every button and link in it is a LinkForty link, one per placement that matters.
  • Links carry utm_campaign, utm_medium and utm_source, from the UTM Library.
  • If you use OneSignal, Braze, Iterable, MoEngage or CleverTap, links carry the user-ID merge tag and the connector is on.
  • The app sends the goal event, with revenue and currency where money changes hands.
  • The goal is marked in the Event Library.
  • After the send, check Analytics → Campaigns for the campaign's row, and Events → Conversions for the links.

Get started

LinkForty's links, SDKs and attribution reports are on every plan, including the free one; paid plans keep more history. Email connectors, analytics integrations and webhooks come with the paid plans. Start with the SDK integration guide, make one link for your next email, and see what it brings back.

attributionlifecycle marketingemail deep linkingre-engagementcampaignsin-app eventsbrazeonesignaliterable
Keep reading

More from the blog

GuidesOct 27, 2026The LinkForty Team

Firebase Dynamic Links Alternative: What to Use Now That It's Shut Down

Firebase Dynamic Links stopped working on August 25, 2025. The right replacement depends on what you used it for: links that open your app, Firebase Auth email links, or deferred deep linking and attribution. Here is each path, what to look for in a replacement, and how to move.

Deep linking that just works

Route every click to the right place across web and mobile, and see what people do after they land. Start free, no credit card required.