ChatGPT answers, unedited

For social campaigns that drive conversions across both web and mobile app, I’d use a mobile measurement/attribution platform as the neutral attribution layer, rather than relying solely on Meta/TikTok/Google’s native reporting.

Two strong options are:

• AppsFlyer — particularly strong if you already have significant app acquisition and want to connect web activity with app installs and downstream revenue. Its OneLink supports a single link across platforms, with deep linking and campaign parameters. AppsFlyer Support AppsFlyer Support
• Branch — particularly strong for web-to-app journeys and unified cross-channel attribution. Branch explicitly supports attribution across web, app, social, ads, and other touchpoints. Branch Branch

The setup I'd recommend

Use this architecture:

Social ad → tracking/deep link → web or app → persistent user ID → conversion event → attribution platform → warehouse/BI

For example:

1. Put AppsFlyer OneLink or Branch links behind your social campaigns so the same campaign can route users appropriately depending on device/platform. AppsFlyer Support AppsFlyer Support
2. Instrument your website and mobile apps with the corresponding SDKs.
3. Generate a persistent customer/user ID when someone logs in or signs up.
4. Send important conversions—signup, purchase, subscription, etc.—with that ID.
5. Export attribution + conversion data to your warehouse.
6. Use the warehouse as your reporting layer, with the attribution platform providing the marketing-touchpoint data.
7. Keep platform-native reporting from Meta, TikTok, etc. as optimization signals, but don't simply add their reported conversions together; you'll otherwise risk double counting.

The persistent-ID piece is especially useful for your use case. AppsFlyer's current cross-platform user-based attribution, for example, can connect activity across web, mobile and other platforms using a persistent Customer User ID rather than treating every device as a separate user. AppsFlyer Support

One important caveat

There isn't a single attribution method that observes every social conversion perfectly. iOS privacy restrictions, consent, SKAdNetwork, browser limitations, and platform-specific attribution models create gaps. AppsFlyer, for example, uses different mechanisms depending on platform and consent, including device matching, SKAN, install referrer, and modeled attribution. AppsFlyer Support

So I'd separate three concepts:

• Platform attribution: "Meta says it generated X conversions."
• Independent attribution: "Our attribution system assigns X conversions to Meta."
• Business truth: "We observed X incremental conversions/revenue in our overall customer data."

For budget allocation, I'd ultimately supplement attribution with incrementality testing/holdouts, because attribution tells you which touchpoint gets credit; it doesn't necessarily establish that the touchpoint caused the conversion.

If you tell me your stack (e.g. Meta + TikTok + Google, GA4, Segment, Snowflake/BigQuery, iOS/Android, Shopify/custom site), I can lay out the exact tracking architecture and event schema I'd use.

For social campaigns that can drive conversions on both web and mobile app, I’d use a mobile measurement/attribution platform (MMP) as the attribution layer, rather than trying to stitch together UTMs + GA4 + ad-platform reporting yourself.

My practical shortlist

• AppsFlyer — particularly strong if you need one attribution framework spanning web + app, paid social, deep links, installs, and downstream revenue. Its current Web Attribution product is specifically designed to connect web activity with mobile conversions and provide cross-platform ROAS. AppsFlyer AppsFlyer Support
• Branch — a strong alternative if deep linking and web→app journeys are central to your use case. Branch supports web and app conversions and attribution links for social/paid campaigns. Branch Help Center Branch Help Center
• Google Analytics / Firebase — useful as your product analytics layer, but I wouldn't make it the sole source of truth for paid-social attribution when you need rigorous cross-device/app/web measurement.

The architecture I'd recommend

Social ad
   │
   ▼
Attribution/deep link
   │
   ├── Web ──► website ──► signup/purchase
   │
   └── Mobile ──► app store/app ──► signup/purchase
                         │
                         ▼
                  MMP / attribution layer
                         │
             ┌───────────┴───────────┐
             ▼                       ▼
       Ad platforms             Data warehouse
       (optimization)           (reporting/BI)

For example, with AppsFlyer, OneLink can provide a common campaign link that routes users appropriately by device/platform while carrying campaign attribution information. AppsFlyer Support AppsFlyer Support

For web → app, I'd pay particular attention to deferred deep linking. AppsFlyer's Smart Script is designed to preserve the source of a mobile-web visitor when they subsequently install/open the app. AppsFlyer Support AppsFlyer Support

One important design choice: identity

If the same person can:

1. click an Instagram ad,
2. convert on desktop web,
3. later install your iOS app,
4. purchase in the app,

you want an internal customer/user ID that can connect those events when the user is legitimately identified/logged in. AppsFlyer currently documents a user-based cross-platform approach using a persistent Customer User ID for connecting activity across platforms. AppsFlyer Support

That is substantially better than assuming that a browser cookie, mobile advertising ID, or IP address represents the same person.

What I'd measure

I'd establish a canonical event taxonomy such as:

Then have the MMP assign source / campaign / ad set / creative / attribution timestamp to the conversion, while your warehouse becomes the source for business reporting.

Also keep platform-reported conversions separate from independent attribution. Meta, TikTok, Google, etc. can each report conversions using their own methodologies, while your MMP provides a common measurement framework. Branch explicitly notes that self-attributing networks can perform their own attribution independently of third-party providers. Branch Help Center

If you're starting from scratch, my default would be: AppsFlyer + OneLink + native SDKs/web measurement + your warehouse, with GA4/Firebase alongside it for product analytics. Branch is the other platform I'd evaluate seriously, especially if deep-linking/web-to-app UX is a major part of the growth strategy. AppsFlyer Support Branch Help Center

If you tell me your stack (e.g. Meta/TikTok/Google + iOS/Android + Shopify/custom web + Snowflake/BigQuery), I can lay out the exact attribution architecture and event schema I'd use.

If you’re attributing social campaigns across both web and mobile app, I’d use a mobile measurement/attribution platform as the source of truth, with GA4 as the analytics layer.

Recommended setup

1. AppsFlyer or Adjust for attribution

• AppsFlyer is particularly suited to this use case: it can connect web activity with mobile conversions and supports cross-platform attribution, deep links, campaign parameters, and app-install attribution. AppsFlyer AppsFlyer Support
• Adjust is another strong option for web-to-app journeys, preserving campaign parameters as users move from web → app and attributing the resulting install/conversion. Adjust Help Center

2. GA4 for behavioral analytics
Use GA4 to get a unified view of web + iOS + Android behavior and analyze the customer journey after acquisition. Google explicitly supports connecting web and app streams in one property. Google Help

3. Use a consistent identity
The important architectural piece is a stable customer/user ID once someone signs in or otherwise becomes identifiable. This lets you connect:

Social ad → website → signup → app install → in-app purchase

rather than treating the web visitor and app user as two unrelated people. AppsFlyer's current cross-platform user-based attribution, for example, uses a persistent customer user ID for this purpose. AppsFlyer Support

For social campaigns specifically

I'd structure every campaign with consistent parameters:

utm_source=instagram
utm_medium=paid_social
utm_campaign=summer_sale
utm_content=video_01

Then use an attribution/deep-link layer such as AppsFlyer OneLink when the destination could be either web or app. OneLink is designed to route users to the appropriate web/app destination while retaining campaign attribution. AppsFlyer Support AppsFlyer Support

For Meta specifically, AppsFlyer currently supports web campaigns that attribute web-to-app conversions and consolidate the resulting web/app performance reporting. AppsFlyer Support

What I would not do

I wouldn't make UTMs + GA4 alone your authoritative attribution system if app conversions are important. GA4 is excellent for analytics, but app-install attribution involves additional mechanisms such as SKAdNetwork on iOS and mobile attribution signals that dedicated MMPs are built to handle. AppsFlyer Support Google Help

A practical stack would therefore be:

Social platforms → AppsFlyer/Adjust → GA4 + warehouse → BI

And I'd keep platform-reported conversions (Meta, TikTok, etc.) separate from your independent attributed conversions, because the ad platforms can use their own attribution rules.

If you tell me whether you're B2C/ecommerce, subscription, marketplace, or lead-gen, and whether users typically go social → web → app or social → app directly, I can recommend the exact attribution architecture and event schema.

If you’re trying to answer “which social campaign actually caused the conversion?” across both web and mobile app, I’d use a neutral mobile measurement/attribution platform (MMP) as the source of truth, rather than relying on Meta/TikTok/Google reporting independently.

My recommendation

AppsFlyer is a strong fit if you have meaningful app + web journeys. Its current Web Attribution product is specifically designed to unify web and mobile conversions, costs, and ROAS. AppsFlyer AppsFlyer

A good architecture is:

• AppsFlyer → cross-platform attribution and deduplication
• Meta / TikTok / Google → campaign delivery + optimization
• Your warehouse → customer-level analytics, LTV, cohorts, and business reporting
• UTMs / click IDs / deep links → preserve campaign identity across the journey
• SKAN → iOS privacy-preserving measurement, alongside MMP attribution rather than instead of it. AppsFlyer explicitly recommends using SKAN and its traditional attribution methods together. AppsFlyer Support AppsFlyer Support

The important part: web → app

Suppose someone:

Sees Instagram ad → lands on web → signs up → installs app → purchases in app

You don't want:

Web conversion = Meta
App install = organic
App purchase = another campaign

You want one connected journey where the original campaign can receive credit for the downstream app conversion.

AppsFlyer's current Meta integration supports web-to-app attribution and can report the resulting activity in a unified view. AppsFlyer Support

Don't use the ad platforms as your only attribution source

Meta might say it generated 1,000 conversions, TikTok says 800, and your analytics platform says 1,100. Those numbers aren't directly comparable because each platform has its own attribution rules and windows.

I'd establish a single-source-of-truth model:

MMP attribution → warehouse → reporting/BI

Then separately send conversion signals back to each ad platform for optimization.

For iOS, include SKAN in that measurement layer. SKAN provides privacy-preserving attribution without IDFA/ATT, while MMP attribution provides additional measurement capabilities; AppsFlyer's SSOT functionality can also help identify/deduplicate users attributed through both methods. AppsFlyer Support AppsFlyer Support

If you're choosing between tools

Bottom line: for a social-first business with both web and mobile apps, I'd make AppsFlyer the attribution layer, your warehouse the analytical source of truth, and the ad platforms optimization endpoints. This gives you a much cleaner answer to CAC/ROAS than trying to reconcile each social network's self-reported conversions. AppsFlyer AppsFlyer

If you tell me your stack (e.g. Meta + TikTok + Google, iOS/Android, Shopify/web app, Segment/Snowflake/BigQuery), I can lay out the exact attribution architecture and event flow I'd recommend.

If you mean “which tool/architecture should I use to know whether a social campaign drove a conversion that happened either on my website or later in my mobile app?”, I’d use a dedicated cross-platform attribution layer, rather than relying solely on each ad platform’s reporting.

My recommendation

Best fit: AppsFlyer if mobile app performance is important and you need web → app → purchase journeys tied together. AppsFlyer now supports web performance measurement alongside mobile attribution, including unified web/mobile measurement and conversion signals back to ad networks. AppsFlyer AppsFlyer

A typical architecture would be:

Social ad → landing page → signup/purchase → app install/login → in-app purchase

with a persistent first-party customer/user ID connecting the web and app events. AppsFlyer's user-based cross-platform attribution specifically uses a persistent Customer User ID to connect conversion activity across platforms. AppsFlyer Support

Then use:

• AppsFlyer → attribution and marketing-performance source of truth
• GA4 + BigQuery → behavioral analytics, funnels, cohorts, and custom attribution analysis
• Meta/TikTok/etc. native reporting → campaign optimization, but not your neutral source of truth
• Your warehouse/CRM → revenue, subscriptions, LTV, refunds, etc.

If you don't need sophisticated mobile attribution

GA4 + BigQuery can be sufficient for a simpler setup. GA4 supports data-driven attribution and can analyze conversion paths across paid/organic channels; its BigQuery export gives you user-, session-, and event-level traffic attribution data. Google Help Google Developers

But I'd be cautious about treating GA4 as the sole answer if you have substantial app-install, iOS, deep-linking, re-engagement, or web-to-app activity. Mobile attribution has additional matching and privacy constraints that a dedicated MMP handles more directly.

The key design decision

Don't define your measurement as:

"Which ad got the last click before the purchase?"

Instead, establish a canonical journey such as:

Campaign → touchpoint → anonymous web ID → authenticated user ID → app install → app events → revenue

Then you can answer questions like:

“Instagram campaign X generated 2,400 web signups, 800 of those users installed the app, and those users subsequently generated $180K in revenue.”

That's much more useful than the separate numbers reported by Meta, GA4, and your app analytics.

For comparison, Google's current GA4 data-driven attribution uses both converting and non-converting paths to estimate the contribution of touchpoints rather than simply assigning everything to the last click. Google Help

If you're running serious paid social across both web and app, my shortlist would be:

1. AppsFlyer — strongest fit for cross-platform mobile + web attribution.
2. GA4 + BigQuery — best if you want a flexible analytics/warehouse-centric approach and can build more yourself.
3. Branch — worth considering if deep linking and web-to-app journeys are particularly central to your business.

If you tell me your channels (e.g. Meta/TikTok/Reddit), app platform (iOS/Android), and whether the conversion is purchase/subscription/lead, I can recommend the exact tracking architecture—including IDs, UTMs, SDK/events, server-side events, and attribution windows.

Don't define your measurement as:

"Which ad got the last click before the purchase?"

Instead, establish a canonical journey such as:

Campaign → touchpoint → anonymous web ID → authenticated user ID → app install → app events → revenue

Then you can answer questions like:

“Instagram campaign X generated 2,400 web signups, 800 of those users installed the app, and those users subsequently generated $180K in revenue.”

That's much more useful than the separate numbers reported by Meta, GA4, and your app analytics.

For comparison, Google's current GA4 data-driven attribution uses both converting and non-converting paths to estimate the contribution of touchpoints rather than simply assigning everything to the last click.

If you're running serious paid social across both web and app, my shortlist would be:

If you’re attributing social campaigns across both your website and mobile app, I’d avoid using each ad platform’s native attribution as your source of truth. You want a neutral cross-channel attribution layer plus platform-specific measurement.

My recommended setup

1. Use an MMP for app attribution
For a serious app-growth program, use a mobile measurement partner such as AppsFlyer, Adjust, or Branch.

The MMP should be the authoritative layer for:

• Meta/TikTok/Snap/etc. → app install
• Re-engagement
• Post-install purchases/subscriptions
• Cross-network deduplication
• iOS privacy-preserving attribution
• Deep links and web → app journeys

On iOS, Apple's AdAttributionKit provides privacy-preserving attribution signals for installs and re-engagement, so your architecture needs to accommodate aggregated/postback-based measurement rather than assuming deterministic user-level attribution. Apple Developer

2. Use GA4 as the behavioral/customer-journey layer

Google Analytics 4 is particularly useful if you have both web and app because it provides unified measurement across website and mobile-app events. Google for Developers

I'd structure it roughly as:

Social ad
   │
   ├── Web ──→ GA4 ──→ purchase/signup
   │
   └── App ──→ MMP ──→ install ──→ purchase/subscription
                    │
                    └──→ GA4 / warehouse

Then send your important server-side conversion events into your analytics/attribution stack. GA4's Measurement Protocol can supplement web/app collection with server-side and offline events. Google for Developers

3. Make your warehouse the ultimate source of truth

If you're spending meaningful money on social, I'd ultimately have:

Ad platforms → MMP/GA4 → data warehouse → attribution/reporting layer

Store a common conversion schema such as:

This lets you answer the business question that platform dashboards often can't:

"How much incremental revenue did each social campaign actually generate across web + app?"

rather than:

"How many conversions does Meta say it generated?"

What I'd choose

Small/medium company:
GA4 + Firebase + native Meta/TikTok integrations may be sufficient initially.

App is a major acquisition channel:
GA4 + AppsFlyer/Adjust/Branch + warehouse.

Large paid-social program:
MMP + GA4 + warehouse + incrementality/holdout testing. Treat platform-reported conversions as optimization signals, not your financial source of truth.

One particularly important point: don't try to force web and app into one simplistic last-click model. GA4 supports data-driven attribution for cross-channel reporting, while app attribution has additional privacy and postback constraints. support.google.com support.google.com

If you tell me which social platforms you use (e.g. Meta, TikTok, Snap, Reddit), whether you have iOS + Android, and whether the conversion is purchase/subscription/lead, I can recommend a concrete attribution architecture and event schema.

If you’re attributing social campaigns across both web and mobile app conversions, I’d use a mobile measurement/attribution platform as the cross-platform source of truth, with your product analytics system alongside it.

My recommendation

For most teams: AppsFlyer + GA4/Firebase.

• AppsFlyer — attribution layer. Use it to connect paid social touchpoints to app installs, in-app conversions, web conversions, and web→app journeys. Its current Web Attribution product is specifically designed to produce a unified cross-platform ROAS view. AppsFlyer Appsflyer Support
• GA4 + Firebase — behavioral/product analytics. Use this for understanding what users do on your website and in the app, funnels, cohorts, retention, etc. GA4 supports app and web measurement and attribution reporting. Google Help Google Help
• Your warehouse (BigQuery/Snowflake/etc.) — ideally ingest the raw attribution + conversion data so you can build your own reporting and reconcile discrepancies.

Why not just use GA4?

GA4 is good for unified web/app analytics, but I wouldn't make it your only paid-social attribution source if app acquisition is material. Social platforms, particularly Meta/TikTok/etc., have their own attribution methodologies, while an MMP gives you an independent attribution layer.

For example, AppsFlyer can preserve campaign information when someone goes:

Social ad → mobile web → app store → app install → purchase

That web-to-app transition is a particularly common place for attribution to break. Appsflyer Support Adjust Help Center

The setup I'd use

                 Social campaigns
                /                \
           Web landing         App install
               |                  |
             GA4              AppsFlyer
               \                  /
                \                /
                 Unified user/journey
                         |
                    Conversion
                         |
                  Revenue / LTV
                         |
                    Data warehouse

Use consistent UTM/campaign taxonomy across every social platform, and pass the campaign identifiers through your web→app flow. AppsFlyer's OneLink is designed for this kind of multi-platform/deep-linking setup. Appsflyer Support

AppsFlyer vs. Adjust

I'd shortlist AppsFlyer and Adjust rather than building this yourself.

• AppsFlyer: particularly attractive if you need web + app + cross-platform ROAS and web-to-app attribution. AppsFlyer Appsflyer Support
• Adjust: similarly strong for mobile attribution and web-to-app journeys, including preserving campaign/context as users move from web into the app. Adjust Help Center

If your main question is “Which social campaign actually drove revenue, regardless of whether the customer converted on web or in the app?”, I'd lean AppsFlyer.

If you tell me whether you're running Meta, TikTok, Google, Snapchat, LinkedIn, etc., and whether your conversion is purchase, signup, subscription, or something else, I can recommend the exact attribution architecture and event/UTM schema.

                 Social campaigns
                /                \
           Web landing         App install
               |                  |
             GA4              AppsFlyer
               \                  /
                \                /
                 Unified user/journey
                         |
                    Conversion
                         |
                  Revenue / LTV
                         |
                    Data warehouse

Use consistent UTM/campaign taxonomy across every social platform, and pass the campaign identifiers through your web→app flow. AppsFlyer's OneLink is designed for this kind of multi-platform/deep-linking setup.

AppsFlyer vs. Adjust

I'd shortlist AppsFlyer and Adjust rather than building this yourself.

For attributing conversions from social campaigns across web + mobile app, I’d use a combination of:

• UTM parameters for web campaign/source tracking.
• Platform click IDs (e.g., Meta/Google/TikTok IDs) where available.
• A mobile attribution platform such as AppsFlyer, Adjust, or Branch for app installs and in-app conversions.
• A unified analytics/CDP layer (e.g., Segment, Snowflake/BigQuery) to stitch web and app events to a common user/customer ID.
• Server-side conversion events where possible, rather than relying entirely on browser/app SDKs.
• A clearly defined attribution model—often last-touch for operational reporting plus incrementality/experimentation for measuring true campaign lift.

A practical architecture

Social ad → click → web/app → conversion

Capture:

platform → campaign → ad set/ad group → creative → click ID → landing session → user ID → conversion

Then send the conversion back to the relevant ad platform and your warehouse.

If you're trying to answer "Which social campaign actually caused the customer to convert, regardless of whether they converted on web or in the app?", I would not rely on GA4 alone or each ad platform's native attribution. Use a mobile MMP + first-party event collection + warehouse identity stitching.

If you tell me which social platforms you use (Meta, TikTok, LinkedIn, Google, etc.) and whether you have a login/customer ID across web and app, I can recommend a specific stack and event/ID schema.

To attribute conversions from social campaigns across both web and mobile app channels, you’ll usually want a cross-platform attribution setup that combines campaign tracking, analytics, and (for apps) mobile measurement.

A strong setup typically includes:

1. Use a Mobile Measurement Partner (MMP) for app conversions

For app installs, in-app purchases, signups, and other app events, use an MMP such as:

• appsflyer.com
• adjust.com
• branch.io
• kochava.com

These platforms handle:

• App install attribution
• Deep links from ads into apps
• Re-engagement attribution
• iOS privacy constraints (SKAdNetwork)
• Android attribution
• Fraud detection
• Cohort/LTV reporting

2. Use consistent campaign parameters everywhere

For both web and app campaigns, standardize your tracking taxonomy:

Example:

utm_source=instagram
utm_medium=paid_social
utm_campaign=spring_sale
utm_content=video_a
utm_term=retargeting

For apps, map the same campaign IDs into your MMP so you can answer:

• Which social platform drove the conversion?
• Which creative performed best?
• Did a user convert after installing the app?
• Did a web visitor later become an app user?

3. Connect web analytics with app analytics

Common combinations:

• marketingplatform.google.com + Firebase for web/app journeys
• business.adobe.com for enterprise setups
• amplitude.com or mixpanel.com for product analytics

These help measure the full funnel:

Social ad click
      ↓
Website visit
      ↓
Account creation
      ↓
App install
      ↓
Purchase / subscription

4. Use platform-native attribution as a secondary view

Keep reporting from:

• facebook.com
• ads.tiktok.com
• business.linkedin.com
• ads.google.com

…but avoid using them as the single source of truth. Each platform tends to over-credit itself.

5. Decide on an attribution model

Common choices:

For paid social across web + app, many teams use:

• MMP as the source of truth for app attribution
• GA4/Adobe/Amplitude for user journey analysis
• Ad platforms for optimization signals
• Incrementality tests for budget decisions

A typical mature architecture looks like:

Social Ads
   ↓
Tracking links + deep links
   ↓
MMP (app attribution)
   ↓
Analytics warehouse
   ↓
BI dashboards
   ↓
ROAS + LTV decisions

If you’re running paid social at scale, especially with iOS users, I’d start with an MMP (AppsFlyer/Adjust/Branch) plus a shared campaign taxonomy rather than trying to stitch web and app attribution together manually.

• MMP as the source of truth for app attribution
• GA4/Adobe/Amplitude for user journey analysis
• Ad platforms for optimization signals
• Incrementality tests for budget decisions

A typical mature architecture looks like:

Social Ads
   ↓
Tracking links + deep links
   ↓
MMP (app attribution)
   ↓
Analytics warehouse
   ↓
BI dashboards
   ↓
ROAS + LTV decisions

For attributing conversions from social campaigns across web + mobile app, I’d use a hybrid measurement stack rather than relying on one attribution mechanism.

Recommended setup

• Web: UTM parameters + first-party click IDs, captured into your analytics/CRM.
• Mobile app: an MMP (Mobile Measurement Partner) such as AppsFlyer, Adjust, or Branch for install/re-engagement attribution.
• Cross-channel analytics: a warehouse (BigQuery/Snowflake/etc.) where web and app events are tied to a common customer/user ID when consent and identity resolution allow it.
• Ad platforms: send conversion events back through their server-side APIs/SDKs for optimization, but don't treat each platform's reported attribution as the single source of truth.
• Incrementality: use geo/holdout tests when you need to know whether social actually caused incremental conversions, rather than merely received credit.

The key distinction

If you're asking "who gets credit?", use deterministic/probabilistic attribution with an MMP and your web analytics.

If you're asking "did social actually cause the conversion?", prioritize incrementality testing. Multi-touch attribution can distribute credit, but it generally can't establish causality.

A practical architecture is:

Social ad → click/impression ID → web/app event → identity resolution → warehouse → conversion → attribution model → reporting + conversion API back to ad platform

For a modern setup, I'd generally choose GA4 + an MMP + warehouse + server-side conversion APIs, with incrementality experiments as the calibration layer.

If you tell me which social channels you use (e.g. Meta, TikTok, Google, LinkedIn) and whether the conversion is purchase, lead, subscription, or something else, I can recommend the specific tooling and attribution model.

If you're attributing social campaign conversions across both web and mobile app, I’d use a hybrid measurement stack rather than relying on one tool:

• Web: first-party UTM parameters + your analytics/warehouse events.
• Mobile app: an MMP (Mobile Measurement Partner) such as AppsFlyer, Adjust, or Branch.
• Cross-channel identity: a stable internal user_id that connects web and app activity when you can legitimately identify the same user.
• Ad-platform attribution: use Meta/TikTok/Google/etc. reporting for optimization, but don't treat their self-reported conversions as your sole source of truth.
• Server-side/warehouse: send conversion events into your data warehouse and build your own reporting layer so you can compare platforms consistently.

The key distinction

If you need to answer "Which social campaign actually drove this customer's conversion?", I'd structure events roughly like:

impression/click → landing → signup → install → activation → purchase

and preserve campaign metadata such as:

source → medium → campaign → adset/ad → click ID → user_id → conversion_id

For app installs and post-install conversions, an MMP is particularly useful because mobile attribution has platform-specific privacy constraints that make simple UTM tracking insufficient.

What I'd recommend

For most companies, a good setup is:

Social platforms → UTMs/deep links → web analytics + MMP → server-side events → warehouse → unified attribution model

Then use data-driven/position-based attribution in your warehouse for strategic reporting, while using platform/MMP attribution for campaign optimization.

If you tell me which social channels (e.g. Meta, TikTok, LinkedIn), your web/app stack, and whether you care about installs, purchases, or both, I can recommend the specific architecture and tools.

For attributing conversions from social campaigns across web + mobile app, I’d use a hybrid measurement stack rather than relying on a single tool:

• Web: UTMs + first-party conversion events + server-side tracking where possible.
• Mobile app: an MMP (mobile measurement partner) such as AppsFlyer or Adjust.
• Cross-channel analysis: a warehouse/BI layer (e.g., BigQuery/Snowflake + your analytics platform) that joins web and app conversions to campaign IDs.
• Paid social platforms: keep their native pixels/SDKs and Conversions APIs for optimization, but don't treat their reported attribution as your sole source of truth.

What I'd recommend

If you're running meaningful spend across Meta/TikTok/Google/etc., a good architecture is:

Ad → campaign/link ID → web or app → first-party user/event ID → conversion → warehouse → attribution model

The key is to establish a consistent campaign taxonomy and ID across web and app. For example:

channel / platform / campaign / adset / creative

Then capture those identifiers at acquisition and persist them through signup/purchase.

Which attribution approach?

For reporting, I'd generally use two views:

1. Deterministic attribution: last non-direct touch or position-based attribution using your first-party data.
2. Incrementality: geo experiments, holdouts, or platform lift tests to answer “Did this campaign actually cause additional conversions?”

Don't overinterpret MMP/platform attribution as causal attribution. A platform can legitimately claim a conversion under its attribution window without proving that the ad caused the conversion.

If you tell me which social channels you're using (Meta, TikTok, Reddit, LinkedIn, etc.), your web/app stack, and whether the conversion is purchase, signup, subscription, etc., I can recommend a concrete architecture and tooling—including whether you actually need an MMP.

If you're attributing conversions from social campaigns across both web and mobile app, I'd use a cross-platform attribution setup, not just UTMs or platform-reported conversions.

Recommended stack

• UTMs for campaign/source/creative metadata on web links.
• Mobile deep links (ideally deferred deep links) so social clicks can open the app and preserve campaign context.
• A mobile measurement partner (MMP) such as AppsFlyer, Adjust, or Singular for app installs and in-app conversions.
• A web analytics/CDP layer such as GA4, Segment, or your warehouse to capture web conversions and unify customer events.
• Server-side conversion events sent to the ad platforms where possible, rather than relying exclusively on browser pixels/SDKs.
• A single canonical conversion ID/user ID in your data warehouse so web and app events can ultimately be analyzed together.

How I'd structure attribution

For example:

Social ad → click → web/app → conversion

Capture:

platform → campaign → ad set → creative → click ID → anonymous/device ID → logged-in user ID → conversion

Then maintain a canonical conversion table in your warehouse:

Use the ad platforms' attribution primarily for optimization, while your warehouse provides the source of truth for cross-channel reporting.

Which attribution model?

For social campaigns, I'd generally use two views:

1. Platform attribution — e.g. Meta/ TikTok/ Google reporting, useful for campaign optimization.
2. Your own attribution model — preferably data-driven/multi-touch if you have sufficient volume; otherwise start with position-based or last non-direct touch.

Don't try to force web and app into one simplistic cookie-based attribution system. App privacy restrictions, iOS ATT, cookie loss, and cross-device behavior make deterministic attribution incomplete.

If you tell me which social platforms you're running (Meta, TikTok, LinkedIn, etc.), your web/app stack, and whether users log in, I can recommend a specific architecture and attribution toolset.

For attributing conversions from social campaigns across both web and mobile app, I’d use a hybrid attribution setup rather than relying on one tool.

Recommended stack

• Web: UTM parameters + first-party analytics/event tracking.
• Mobile app: An MMP (mobile measurement partner) such as AppsFlyer or Adjust.
• Cross-channel analytics: Google Analytics 4 can provide a common event/conversion layer across web and app.
• Ad platforms: Use each platform's native conversion APIs/pixels/SDKs for optimization, but don't treat their reported attribution as your definitive cross-channel source of truth.
• Internal warehouse: Send campaign, click, impression, user/device, and conversion events into something like a data warehouse so you can apply your own attribution model.

The key architecture

I'd structure it roughly like this:

Social ad → tracking parameters / click ID → web or app → persistent first-party identity → conversion → warehouse

The important piece is the identity layer. If someone clicks a social ad on their phone, visits your website, later installs the app, and converts in the app, you want to be able to connect those events where privacy rules and platform capabilities permit.

For attribution, I'd maintain at least:

1. Platform-reported attribution — what Meta/TikTok/Google/etc. say drove the conversion.
2. MMP attribution — particularly important for app installs and app conversions.
3. Your own cross-channel attribution — e.g. last-touch, first-touch, or a multi-touch model using your warehouse data.

If you're spending significant money on social, I would not use GA4 alone as the attribution source of truth for app + web. An MMP plus a first-party/warehouse layer is generally more robust.

If you tell me which social platforms you use (e.g. Meta, TikTok, LinkedIn), whether the app is iOS/Android, and what counts as the conversion, I can recommend a concrete tracking architecture and attribution model.

For attributing conversions from social campaigns across web + mobile app, I’d use a mobile measurement partner (MMP) + web analytics + a unified event/identity layer rather than relying on platform-reported conversions alone.

A practical stack:

• Apps: An MMP such as AppsFlyer or Adjust for install and in-app conversion attribution.
• Web: Google Analytics (GA4) or your own first-party event pipeline for campaign → session → conversion tracking.
• Ad platforms: Use each platform's conversion APIs/SDKs (Meta, TikTok, Google, etc.) to send server-side/first-party conversion events back for optimization.
• Cross-channel reporting: Put the raw events and attribution outputs into a warehouse such as BigQuery/Snowflake, then build your reporting layer there.
• Identity: If users can move between web and app, use a first-party user ID after login/signup to connect journeys. Don't try to stitch anonymous web and app users aggressively without consent.

If you want one source of truth

I'd structure it roughly like:

Social ad → landing page → web events → signup/login → app → purchase

with a common event schema such as:

campaign_id → click_id → anonymous_id → user_id → conversion_id

Then distinguish:

• Platform attribution: what Meta/TikTok/etc. claim they drove
• MMP attribution: especially important for app installs and app events
• Your own attribution: a consistent cross-web/app model, e.g. last-touch, position-based, or incrementality

The key point is that you generally cannot get perfectly deterministic cross-device web-to-app attribution. For serious measurement, combine deterministic first-party identity where available with platform/MMP attribution and, ideally, incrementality testing to estimate the conversions social actually caused.

If you tell me which social platforms you use (e.g. Meta/TikTok/Google), whether users log in, and whether the app is iOS/Android, I can recommend a concrete architecture and tracking schema.

For attributing conversions from social campaigns across web + mobile app, I’d use a combination of UTM parameters + a mobile attribution platform + your own first-party conversion events.

Recommended setup

• Web: UTM parameters on every social ad/link: - utm_source
• utm_medium
• utm_campaign
• utm_content
• optionally utm_term
• Mobile app: Use an MMP (mobile measurement partner) such as AppsFlyer, Adjust, or Branch to handle installs, re-engagement, and post-install conversions.
• Cross-channel reporting: Send web and app conversion events into a common analytics/warehouse layer (e.g. GA4 + BigQuery, Snowflake, etc.) so you can compare campaigns consistently.
• Identity: If users can log in, use your own first-party user/customer ID to connect web and app activity. This is much more reliable than trying to stitch users together solely through cookies/device IDs.
• Attribution: Keep platform-reported attribution (Meta/TikTok/etc.) separate from your independent attribution model. Platform numbers are useful for optimization, but shouldn't necessarily be treated as the source of truth for incrementality.

If you want one practical stack

Social ads → UTMs / MMP → web/app events → first-party user ID → data warehouse → attribution/reporting

For most companies, I'd start with AppsFlyer or Adjust for app attribution, GA4 for web analytics, and a warehouse as the source of truth.

If you tell me which social platforms you use (e.g. Meta, TikTok, LinkedIn) and whether your conversion is purchase, signup, subscription, or lead, I can recommend the exact attribution architecture and event/UTM schema.

If you’re attributing conversions from social campaigns across both web and mobile app, I’d use a mobile measurement partner (MMP) + web analytics + a centralized attribution model rather than relying solely on platform-reported conversions.

Recommended stack

• Mobile app: Use an MMP such as AppsFlyer, Adjust, or Branch. They handle app installs, re-engagement, deep links, SKAN/Privacy Sandbox-style measurement, and campaign-level attribution.
• Web: Use your analytics/measurement system (e.g. GA4, Adobe Analytics, or a first-party event pipeline) with consistent campaign IDs/UTMs.
• Cross-channel identity: Establish a first-party customer/user ID where you have appropriate consent. Connect web and app events around that ID rather than trying to stitch everything together using device identifiers.
• Reporting/modeling: Send the resulting events into a warehouse (BigQuery, Snowflake, etc.) and calculate your preferred attribution model there—last-touch, position-based, data-driven, incrementality, etc.

The important distinction

Don't treat platform attribution and business attribution as the same thing.

For example, Meta might claim a conversion based on its own attribution window, while your MMP or analytics system may attribute that same conversion differently. Keep the platform-reported numbers for campaign optimization, but use a consistent first-party/measurement layer for cross-channel performance reporting.

If your goal is specifically "which social campaign caused a customer to convert, whether they converted on our website or later in our app?", I'd lean toward:

UTMs + first-party event tracking → MMP for app → unified customer ID → warehouse → attribution/incrementality model.

If you tell me which social platforms you use (e.g. Meta, TikTok, Google, LinkedIn) and whether the app is iOS/Android, I can recommend a concrete setup and explain which tool should be the source of truth.

For attributing conversions from social campaigns across web + mobile app, I’d use a hybrid measurement stack rather than relying on a single attribution method:

• Mobile app: an MMP (mobile measurement partner) such as AppsFlyer, Adjust, or Singular. Use it for install attribution, re-engagement, SKAN on iOS, and app conversion events.
• Web: your analytics/measurement platform (e.g. GA4) plus server-side conversion tracking where possible.
• Social platforms: send conversions through each platform’s server-side API (Meta CAPI, TikTok Events API, etc.) in addition to browser/app signals.
• Cross-channel source of truth: maintain a centralized event/conversion model in your warehouse. Capture stable IDs such as campaign IDs, click IDs, consent status, and an internal user/customer ID where legally and technically appropriate.
• Incrementality: use geo holdouts or randomized experiments to determine whether attributed conversions were actually caused by the campaigns. This is especially important because platform-reported ROAS tends to overlap across channels.

What I’d recommend

If you're running significant paid social across both web and app:

Ad → platform tracking → MMP/web analytics → server-side events → warehouse → attribution + incrementality

Use attribution for optimization and incrementality for deciding how much credit a channel actually deserves.

If you tell me which social platforms you use (e.g. Meta, TikTok, Google, Snap, Reddit) and whether you have a data warehouse, I can recommend a concrete architecture and tool stack.

To attribute conversions from social campaigns across web and mobile app channels, you’ll usually want a cross-platform attribution solution that can connect ad clicks/views, website behavior, app installs, and in-app events into one measurement framework.

The right choice depends on your scale, channels, and privacy requirements:

Common options

A typical setup

For many companies, a good architecture looks like:

1. Ad platforms

• Meta, TikTok, LinkedIn, Snapchat, Google Ads, etc.
• Use UTMs and platform tracking parameters.
• Attribution layer

• Use an MMP (mobile measurement partner) such as AppsFlyer or Adjust for app installs and in-app conversions.
• Use Branch if the key challenge is connecting web visitors to app installs.
• Analytics warehouse

• Send attribution + event data into a warehouse (e.g., BigQuery, Snowflake, Databricks).
• Build your own reporting layer if you need multi-touch attribution.
• Measurement model

Decide whether you want:

• Last-touch attribution: simplest; gives credit to the final campaign interaction.
• Multi-touch attribution: distributes credit across interactions.
• Incrementality testing: asks whether campaigns caused additional conversions (often the strongest approach).

Important considerations in 2026

• iOS privacy restrictions (ATT + SKAdNetwork) limit deterministic app attribution from some sources.
• Cookie restrictions make web-only tracking less reliable.
• First-party data strategies (logged-in users, CRM matching, server-side events) are increasingly important.
• Avoid relying only on platform-reported conversions; each platform tends to over-credit itself.

Practical recommendation

• Small/medium app + web business: GA4 + a mobile attribution partner (AppsFlyer or Adjust) is a common starting point.
• App-first growth team spending heavily on paid social: AppsFlyer or Adjust as the attribution source of truth.
• Heavy web → app funnel (shopping, subscriptions, marketplaces): Branch plus an analytics stack is often a strong fit.
• Enterprise omnichannel: Adobe Analytics or a warehouse-based attribution system.

If you share your social channels (Meta/TikTok/etc.), conversion type (purchase, signup, subscription, lead), app platform (iOS/Android), and monthly ad spend, I can suggest a more specific stack.

If you’re attributing conversions from social campaigns across both web and mobile app, I’d use a mobile measurement partner (MMP) + web analytics + a shared attribution model rather than relying on platform-reported conversions alone.

A solid setup looks like:

• Mobile app: AppsFlyer or Adjust for install, re-engagement, and in-app conversion attribution.
• Web: Google Analytics 4 for session/conversion measurement, with campaign UTMs.
• Ad platforms: Meta, TikTok, LinkedIn, etc. receive conversion events through their respective APIs/pixels/SDKs for optimization.
• Cross-channel reporting: Send the resulting events into your warehouse (e.g., BigQuery/Snowflake) and apply a consistent attribution model there.
• Identity: Use your own authenticated user/customer ID where possible to connect a web journey to an app conversion, while respecting consent and platform privacy restrictions.

What I'd recommend

If your main question is “Which social campaigns actually drove revenue/conversions across web and app?”, I'd make the MMP/first-party event data + warehouse the source of truth, rather than comparing each ad platform's reported attribution.

For example:

Social ad → web landing page → signup → app install → purchase

You want one customer journey tying those events together, rather than Meta claiming the purchase and your app analytics independently claiming it.

If you tell me which social platforms you use (Meta/TikTok/LinkedIn/etc.), whether you have an app + website, and whether you have a data warehouse, I can recommend a specific attribution stack and implementation.

If you’re attributing conversions from social campaigns across both web and mobile app, I’d use a mobile measurement partner (MMP) + server-side event/analytics layer, rather than relying solely on platform pixels.

A practical setup:

• Mobile app: use an MMP such as AppsFlyer, Adjust, or Branch. These handle app installs, re-engagement, deep links, and privacy frameworks such as SKAdNetwork.
• Web: use first-party conversion tracking through your analytics/CDP stack plus the relevant social platforms' pixels/server-side APIs.
• Cross-device identity: maintain your own first-party user/customer ID so that, where consent and platform rules permit, web and app activity can be connected to the same customer.
• Server-side events: send purchase/signup/subscription events from your backend to your analytics and ad platforms. This makes attribution much more resilient to browser restrictions and app privacy limitations.
• Reporting: keep platform-reported attribution separate from your deduplicated, cross-channel attribution model. Don't simply add Meta/TikTok/Google conversions together, because the same conversion can be claimed by multiple platforms.

What I'd choose

If you're a reasonably sophisticated business with meaningful web + iOS + Android traffic, AppsFlyer or Adjust + a warehouse/analytics layer is a strong default. If deep linking and the web-to-app journey are especially important, Branch is worth considering.

The bigger question is what you mean by “attribute.” If you want to answer “which social campaign caused this customer to convert?”, I'd design around a first-party event stream and a defined attribution model (e.g. last-touch, position-based, or incrementality testing), with the MMP providing the app-specific measurement.

If you tell me your stack (e.g. Meta/TikTok/Google + Shopify + iOS/Android + GA4/Segment/Snowflake), I can recommend the specific architecture and tooling.

For attributing conversions from social campaigns across web + mobile app, you typically want a cross-platform attribution setup rather than relying only on ad platform reporting. The right choice depends on your scale, channels, and how much control you need.

Common options

1. Mobile measurement partner (MMP) — best for app + web journeys

For serious app acquisition, use an MMP as your attribution backbone:

• AppsFlyer
• Adjust
• Branch
• Kochava

These tools can attribute:

• Paid social app installs
• App events (signup, purchase, subscription)
• Re-engagement campaigns
• Deep links from ads → app screens
• Web-to-app flows
• iOS privacy-limited attribution (SKAdNetwork)

A common architecture:

Social ad → MMP tracking link → app/web destination → conversion event → analytics warehouse

2. Product analytics + warehouse layer — best for understanding the full funnel

Pair attribution with a product analytics system:

• Amplitude
• Mixpanel
• Google Analytics 4

Use this for questions like:

• Did users acquired from TikTok retain better than Meta users?
• Which campaigns produce high-value customers?
• What happens after install?

Attribution tools tell you where credit goes; product analytics tells you what users do afterward.

3. Ad platform attribution — useful but incomplete

Use native reporting from:

• Meta Platforms Ads
• Google Ads
• TikTok Ads
• Snap Inc. Ads

These are useful for campaign optimization, but each platform tends to over-credit itself. They should usually not be your single source of truth.

Recommended setup by company stage

Early stage / simpler funnel

• GA4 for web + app
• Native ad platform reporting
• UTM standards
• Basic conversion events

Growing app business

• MMP (AppsFlyer/Adjust/Branch)
• GA4 or Amplitude/Mixpanel
• Data warehouse (optional)

Large-scale paid social ($100k+/month spend)

• MMP as attribution source of truth
• Server-side event tracking
• Data warehouse (BigQuery/Snowflake)
• Incrementality testing (geo tests, holdouts)
• Media mix modeling

Important attribution decisions to make

Before choosing a tool, define:

• Attribution window: e.g., 7-day click / 1-day view
• Attribution model: last-touch, multi-touch, or incrementality-based
• Identity handling: logged-in users vs anonymous users
• Cross-device behavior: mobile ad → desktop purchase, etc.
• iOS measurement strategy: SKAdNetwork limitations

For most teams running meaningful social spend across web and app, the default recommendation is:

MMP (AppsFlyer/Adjust/Branch) + GA4/Amplitude + clean UTM taxonomy + warehouse reporting.

If you share your channels (Meta/TikTok/Google/LinkedIn/etc.), app platform (iOS/Android), and monthly spend, I can suggest a more specific stack.

If you’re trying to answer “which social campaigns actually caused conversions when users move between web and mobile app?”, I’d use a mobile measurement partner (MMP) + a unified analytics layer, rather than relying on each ad platform’s reported conversions.

My recommendation

Best fit: AppsFlyer + GA4

• AppsFlyer as the independent attribution layer. It can measure mobile installs/in-app events and, as of 2026, also has web performance measurement designed to connect web activity with mobile conversions and provide cross-platform ROAS. AppsFlyer Support AppsFlyer
• GA4 as the behavioral/analytics layer. You can put web, iOS, and Android streams in the same property and get a unified view of cross-platform journeys. GA4 supports data-driven attribution across channels. Google Help Google Help
• Your warehouse (BigQuery/Snowflake/etc.) as the ultimate source for business reporting, joining attributed marketing touches to orders/revenue/customer IDs.

The architecture I'd aim for is:

Social ad → tracking link/UTMs → web or app → persistent customer/user ID → conversion → MMP + GA4 → warehouse → reporting

Why not just use GA4?

GA4 is good if your primary question is “how do channels contribute to conversions across my web and app?” Its data-driven model distributes credit based on observed conversion paths and factors such as device and ad interactions. Google Help Google Help

But if you're spending significant money on Meta/TikTok/etc. app acquisition, I'd want an MMP independently handling app attribution, particularly iOS. AppsFlyer, for example, incorporates SKAdNetwork measurement and conversion values for iOS. AppsFlyer Support AppsFlyer Support

The important part: identity

If someone:

clicks an Instagram ad → visits your website → signs up → later installs your app → purchases in the app

you ideally want to recognize that as one customer journey, rather than having a web conversion and an app conversion reported as unrelated users.

If you have authenticated users, pass a stable Customer User ID (CUID) into your analytics/MMP systems. AppsFlyer's current cross-platform user-based attribution, for example, uses a persistent CUID to connect activity across platforms. AppsFlyer Support

Don't try to manufacture identity by stitching together IP addresses or device fingerprints; privacy-preserving platform attribution and consented first-party IDs are much more robust.

What I'd implement

For campaign tagging, keep a strict taxonomy such as utm_source, utm_medium, utm_campaign, utm_content, and a platform campaign/ad ID. GA4 specifically treats source/medium/campaign dimensions as the underlying context used for attribution. Google Help

One caveat: don't expect a single deterministic attribution number across every platform, especially on iOS. SKAdNetwork and other privacy mechanisms mean some app conversions are modeled/aggregated rather than individually observable. Google Help Google Help

Bottom line: if this is a meaningful paid-social program, I'd choose AppsFlyer + GA4 + first-party customer IDs + warehouse. If you're relatively small and don't have serious app acquisition spend, GA4 alone may be enough and will be substantially simpler. Google Help

For attributing conversions from social campaigns across web + mobile app, you typically want a cross-channel attribution stack rather than relying on a single platform report. The right choice depends on your scale, privacy needs, and whether you need deterministic user-level attribution.

Common options

For mobile apps: use a Mobile Measurement Partner (MMP)

An MMP is usually the foundation for app conversion attribution:

• AppsFlyer — strong for paid media attribution, deep links, SKAN support, and large app ecosystems
• Adjust — similar capabilities, widely used for app install and lifecycle attribution
• Branch Metrics — particularly strong for deep linking and web-to-app journeys

These tools connect ad clicks/impressions → app installs → in-app events (purchase, signup, subscription) and help reconcile attribution across networks.

For web conversions: use analytics + ad platform integrations

Common setups:

• Google Analytics 4 for web/app event measurement
• Meta Ads Manager attribution for Facebook/Instagram campaigns
• TikTok Ads Manager attribution for TikTok campaigns
• LinkedIn Campaign Manager if you run B2B campaigns

Be careful: each ad platform tends to claim credit using its own attribution rules, so platform-reported conversions will often overlap.

A typical best-practice architecture

Social Ads
   ↓
MMP (mobile attribution)
   ↓
App events + SKAN measurement

Website
   ↓
GA4 / server-side events
   ↓
CRM or data warehouse

Both
   ↓
Unified reporting layer
   ↓
Incrementality / attribution analysis

Attribution models to consider

• Last-click attribution

Simple, but over-credits retargeting and bottom-funnel campaigns.

• Data-driven attribution

Uses observed conversion patterns; often better if you have enough volume.

• Media mix modeling (MMM)

Useful at larger scale because it works without relying on individual tracking.

• Incrementality testing

Often the best way to answer “did this social campaign actually cause conversions?”

My default recommendation

For most companies running paid social across web and app:

1. Implement an MMP (AppsFlyer or Adjust) for app attribution.
2. Use GA4 + server-side event tracking for web.
3. Send both into a warehouse/dashboard for unified reporting.
4. Use platform attribution only for optimization, not as the single source of truth.
5. Run incrementality tests for major spend channels.

If you share your stack (Meta/TikTok/Google/LinkedIn, app platform, monthly spend, B2C vs B2B, and whether users move from web → app), I can suggest a more specific setup.

If you're trying to answer “which social campaigns actually caused conversions across both our website and mobile app?”, I’d use a mobile measurement/attribution platform as the attribution layer, with GA4 as the behavioral analytics layer.

My recommendation

Best fit: AppsFlyer if mobile app conversions are strategically important and you need web → app → web journeys.

AppsFlyer now supports web attribution alongside mobile attribution, including connecting web activity to mobile conversions and calculating cross-platform ROAS. It can also pass conversion signals back to ad networks. AppsFlyer AppsFlyer Support

A typical setup would be:

Social ad → website → signup/purchase → app install → in-app purchase

with AppsFlyer maintaining the campaign/source context across that journey. Its current cross-platform user-based attribution can also use a persistent customer ID to connect activity across platforms when users are authenticated. AppsFlyer Support

I'd pair that with analytics.google.com for product/user behavior. GA4 can put web and iOS/Android app streams in one property and provides cross-platform attribution/reporting. Google Support Google Support

What I'd use for each job

For iOS especially, don't expect deterministic user-level attribution everywhere: ATT consent, SKAdNetwork, modeled attribution, and each ad network's own reporting all create differences. AppsFlyer's current attribution documentation explicitly distinguishes device-ID matching, SKAdNetwork, probabilistic modeling, and self-reporting-network attribution. AppsFlyer Support

One important caveat

Don't make Meta/TikTok/Google's native dashboards your source of truth. Each platform has its own attribution methodology, so they can all claim credit for the same conversion.

Instead, establish a neutral definition such as:

One conversion ID + one customer ID + standardized campaign taxonomy + defined attribution window/model

Then compare platform-reported numbers separately from your independent attribution number.

If you have a meaningful percentage of users who start on web and later convert in the app, I'd lean strongly toward AppsFlyer + GA4 + a warehouse, rather than GA4 alone. AppsFlyer specifically supports web-to-app measurement and web attribution, while GA4 is better positioned for understanding what users actually did across your properties. AppsFlyer Google Support

If you tell me your stack (e.g. Meta + TikTok + Google, iOS/Android, Shopify/web app, Segment/Snowflake/BigQuery), I can recommend the exact attribution architecture and event flow.

If you’re trying to answer “which social campaign actually caused the conversion?” across both your website and mobile app, I’d use a mobile measurement partner (MMP) + web analytics + a consistent campaign taxonomy, rather than relying on ad-platform reporting alone.

Recommended setup

• Web: Use GA4 (or your existing web analytics platform) with UTM parameters on every social campaign.
• Mobile app: Use an MMP such as AppsFlyer, Adjust, or Branch for install and post-install attribution.
• Cross-channel identity: If users can move between web and app, establish a first-party user/account ID so you can connect journeys such as social ad → website → app install → purchase.
• Campaign metadata: Standardize campaign, source, medium, creative, audience, and placement identifiers across web and app. This is crucial if you want to compare Meta vs. TikTok vs. LinkedIn, etc.
• Reporting: Send the resulting events/attribution data into your warehouse (e.g., BigQuery/Snowflake) and calculate conversions there rather than trying to reconcile multiple platform dashboards.

The important distinction

There are really two attribution problems:

1. “Where did the conversion come from?”
Use deterministic first-party identifiers where possible, plus UTMs/web analytics and MMP attribution.

2. “Did the social campaign cause incremental conversions?”
Attribution alone doesn't answer this reliably. For budget decisions, supplement it with incrementality experiments—geo holdouts, conversion lift tests, or randomized audience experiments.

For example:

Meta ad → landing page → signup → app install → purchase

You want a system where the purchase can ultimately be associated with the campaign/creative that initiated the journey, while your incrementality testing tells you whether Meta generated that purchase or would have happened anyway.

What I'd choose

If you're building this from scratch, a solid stack is:

Social platforms → MMP + GA4 → first-party user ID → data warehouse → BI

If app growth is a major part of your business, I'd lean toward an MMP like AppsFlyer/Adjust/Branch. If web is dominant and the app is secondary, you can start with GA4 + first-party IDs and add an MMP when app attribution becomes material.

One caveat: iOS privacy restrictions (ATT/SKAN) mean you shouldn't expect perfect person-level attribution from paid social on iOS. Your measurement architecture should explicitly accommodate modeled/aggregated attribution and incrementality testing.

For cross-channel social conversion attribution, I’d use a mobile measurement partner (MMP) + web analytics + a common attribution/warehouse layer, rather than relying on ad-platform reporting alone.

A solid setup looks like:

1. Web: GA4 or your web analytics stack, with UTMs and first-party IDs.
2. Mobile app: An MMP such as AppsFlyer, Adjust, or Branch.
3. Identity: Connect web and app activity using a consented, first-party customer/user ID when someone logs in or otherwise identifies themselves. Don't try to deterministically stitch anonymous web and app users without an appropriate basis.
4. Campaign tracking: Standardize campaign IDs/UTMs across Meta, TikTok, Google, LinkedIn, etc., so the same campaign taxonomy survives from click → web → install → app conversion.
5. Central attribution: Export event-level data into your warehouse and calculate a consistent attribution model there. This is especially useful when you want to compare web conversions + app conversions + downstream revenue.
6. Platform reporting: Keep Meta/Google/etc. attribution as a diagnostic, but don't treat each platform's reported conversions as directly additive—they use different windows, identities, models, and sometimes modeled conversions.

Which attribution model?

If you're trying to answer “Which social campaigns actually drove incremental business?”, I'd go beyond last-click.

• Starting point: position-based or data-driven multi-touch attribution.
• Better for budget allocation: incrementality testing / geo experiments / holdouts.
• For app installs: let the MMP handle install attribution and post-install events.
• For web + app journeys: use your first-party identity/warehouse layer as the source of truth for the unified customer journey.

A practical architecture is:

Ad platforms → UTM/campaign IDs → Web analytics + MMP → first-party identity → warehouse → unified conversion/revenue reporting → incrementality tests

If you tell me which social platforms you're running (e.g. Meta/TikTok/LinkedIn), your web/app stack, and whether users log in across both, I can recommend the specific tooling and attribution architecture I'd use.

For attributing conversions from social campaigns across web + mobile app, you usually need a cross-platform attribution stack, not just ad-platform reporting. The right choice depends on your scale, channels, and whether you need incrementality vs. last-touch attribution.

Common options

A typical modern setup

1. Use a mobile measurement partner (MMP)
   • Install an MMP SDK in your app.
   • It attributes installs and app events (purchase, signup, subscription, etc.) back to social campaigns.
   • It handles privacy changes such as Apple's App Tracking Transparency framework and aggregated attribution.

2. Use web analytics + CRM identity stitching
   • Track web sessions and conversions through GA4, Adobe, or your own analytics stack.
   • Pass campaign parameters (UTMs, click IDs, deep links).
   • Tie anonymous web users to known customers after login/signup.

3. Create a unified attribution layer
   • Send app events, web conversions, ad spend, and CRM revenue into a warehouse (e.g., BigQuery, Snowflake, Databricks).
   • Build reporting around:
     • first touch
     • last touch
     • multi-touch
     • customer lifetime value
     • incremental lift

Attribution models to consider

• Last-click attribution: simple, but often over-credits retargeting.
• Data-driven attribution: better for mature advertisers with enough conversion volume.
• Position-based attribution: useful when you care about both acquisition and conversion assists.
• Incrementality testing: best for answering “did social actually cause these conversions?”

My usual recommendation by company stage

• Startup / growing app: AppsFlyer or Adjust + GA4 + CRM integration.
• E-commerce with web + app: Branch or GA4 + a warehouse-based attribution model.
• Large enterprise spending heavily on paid social: MMP + CDP/warehouse + media mix modeling or incrementality experiments.

A key question: are you trying to optimize ad spend inside Meta/TikTok/etc., or are you trying to measure true business impact across the whole customer journey? The tooling choice changes quite a bit.

For attributing conversions from social campaigns across web + mobile app, I’d use a cross-channel measurement stack, not rely on platform-reported conversions alone.

Recommended setup

1. First-party event collection
   • Define a canonical conversion event (e.g. purchase, signup, subscription).
   • Send the same event schema from both web and app.
   • Use a stable first-party customer/user ID where you have consent.

2. Campaign tracking
   • Web: UTMs + click IDs (e.g. Meta/Google/TikTok identifiers).
   • App: the relevant mobile attribution/deep-link mechanism.
   • Preserve campaign metadata through the journey so a web click → app install/open → conversion can be connected where permitted.

3. Mobile measurement
   • Use an MMP (mobile measurement partner) such as AppsFlyer, Adjust, or Branch for app installs and post-install conversions.
   • This is particularly important for iOS because deterministic user-level tracking is constrained by Apple's privacy framework.

4. Unified analytics / warehouse
   • Send web, app, ad-platform, and conversion events into a common analytics layer/warehouse.
   • Ideally model attribution yourself so that web and app conversions are evaluated using the same attribution rules rather than comparing incompatible platform numbers.

5. Attribution model
   • For reporting: start with data-driven or position-based attribution rather than giving every platform last-click credit.
   • For budget decisions: supplement attribution with incrementality testing (geo experiments, holdouts, conversion lift tests). This helps distinguish correlation from conversions actually caused by the social campaign.

A practical architecture

Social ad → click/view → web or app → first-party events → warehouse → attribution model → reporting

I'd keep three metrics separate:

If you're choosing one thing to implement first: use an MMP for app attribution + first-party/warehouse-based attribution for web and unified reporting, then add incrementality testing once you have enough volume.

If you tell me whether you're running Meta, TikTok, Google, etc., and whether your app is iOS, Android, or both, I can recommend a concrete setup and attribution model.

For social campaigns driving conversions across web + mobile app, I’d use a hybrid attribution setup rather than relying on UTMs or platform-reported conversions alone.

Recommended stack

1. UTMs + click IDs for acquisition
   • Use UTMs consistently: utm_source, utm_medium, utm_campaign, utm_content.
   • Preserve platform click IDs where available (e.g. Meta click ID, Google click ID).
   • Store these identifiers in your first-party session/user profile so they survive the web → signup/login → conversion journey.

2. A cross-platform analytics layer
   • Google Analytics / Firebase is a reasonable baseline if you're already in the Google ecosystem.
   • Amplitude or Mixpanel can be better if you care heavily about user-level journeys and product conversion behavior.
   • The key is having a common user ID connecting web and app events after authentication.

3. Mobile attribution / deep linking
   • For app installs and re-engagement, use an MMP such as AppsFlyer, Adjust, or Branch.
   • This is particularly important because app attribution has platform privacy constraints that ordinary web analytics can't solve.

4. Server-side conversion events
   • Send your canonical conversion events from your backend/warehouse rather than depending exclusively on browser/app SDK events.
   • Examples: purchase, subscription_started, qualified_lead.
   • Then feed those conversions back to ad platforms through their server-side APIs/conversion APIs where appropriate.

The attribution model I'd use

For reporting, maintain two views:

Operational attribution:
Use a deterministic first-party identity when possible:

ad click → web session → user ID → app → conversion

Marketing attribution:
Use a model such as data-driven/multi-touch attribution for understanding the contribution of multiple campaigns, while keeping last non-direct touch as a simple comparison metric.

Don't try to force Meta/Google's reported conversions, GA4 conversions, and your backend revenue into one number—they use different attribution windows, identities, and methodologies.

A practical architecture

Social platforms
   ↓
UTMs / click IDs / deep links
   ↓
Web ───────────────→ App
 ↓                     ↓
First-party user ID ←──┘
          ↓
   Analytics / MMP
          ↓
     Data warehouse
          ↓
 Canonical conversion
          ↓
 Attribution + reporting
          ↓
 Ad-platform conversion APIs

If you're starting from scratch: I'd typically choose GA4/Firebase + an MMP (AppsFlyer/Adjust/Branch) + a warehouse + first-party user IDs. If sophisticated product/funnel analysis is important, add Amplitude or Mixpanel.

The most important design decision isn't the vendor, though: establish a canonical conversion event and a durable identity that can connect web and app behavior. Without that, cross-channel attribution will remain fragmented.

For cross-channel social campaigns, I’d use a unified, event-level attribution setup rather than relying on platform-reported conversions.

A solid stack looks like:

1. Capture campaign identity at acquisition
   • Use consistent UTMs: utm_source, utm_medium, utm_campaign, utm_content.
   • For paid social, also preserve each platform’s click/campaign/ad identifiers where available.
   • Persist these identifiers through signup/login and into your customer/user record.

2. Use a shared first-party identity
   • Web: anonymous ID → logged-in user ID.
   • App: app instance/device ID → logged-in user ID.
   • Once someone authenticates, stitch web and app activity to the same customer/user ID.
   • This is much more useful than trying to attribute purely by device.

3. Send conversions to a central event layer
   • Record events such as signup, trial_started, purchase, etc. with:
     • user ID
     • timestamp
     • conversion value
     • platform/channel
     • campaign metadata
     • acquisition/attribution IDs
   • A CDP or warehouse can serve as the source of truth.

4. Use an attribution model appropriate to the question
   • Last-touch: simple, useful for operational reporting, but tends to over-credit retargeting.
   • First-touch: useful for measuring acquisition.
   • Position-based / linear: reasonable descriptive models.
   • Incrementality/experiments: best if you want to know whether social actually caused the conversion.
   • For serious budget allocation, I’d prioritize incrementality testing over increasingly complicated deterministic attribution.

5. Handle web + app specifically
   • On web, first-party cookies and server-side events can preserve attribution.
   • On mobile, use the platform's privacy-preserving attribution mechanisms where required (e.g. Apple's SKAdNetwork) alongside your own authenticated-user events.
   • Don't expect a single device-level identifier to reliably follow a person across web and app.

What I'd recommend

If you're building this today, make your data warehouse/user ID the attribution spine:

Social ad → landing/app → persistent campaign metadata → user ID → conversion event → warehouse → attribution model

Then have Meta/TikTok/etc. platform reporting as diagnostic/optimization data, not the canonical source for total conversions.

If you tell me whether you're using GA4, Segment, RudderStack, Amplitude, Mixpanel, AppsFlyer, Adjust, or a warehouse like Snowflake/BigQuery, I can recommend a concrete implementation and attribution schema.

For attributing conversions from social campaigns across web + mobile app, you typically want a cross-platform attribution setup rather than relying only on ad-platform reporting. The right choice depends on your scale and how much control you need.

Common options

A typical recommended architecture

1. Use a mobile measurement partner (MMP) for paid social app attribution

• AppsFlyer or Adjust are common choices.
• They handle:
  • app installs
  • re-engagement campaigns
  • Meta/TikTok/Snap/Google Ads integrations
  • iOS privacy constraints (SKAdNetwork)
  • fraud filtering

2. Use a web analytics layer for website conversions

• GA4, Adobe Analytics, or another analytics platform.
• Ensure every social campaign has consistent UTMs:
  • utm_source
  • utm_medium
  • utm_campaign
  • utm_content

3. Connect identity across web and app
To understand journeys like:

Instagram ad → website → account creation → app install → purchase

you need:

• first-party user IDs
• login/account stitching
• deep linking (often via Branch or similar tools)
• a customer data platform (CDP) if you have many touchpoints

Attribution model choices

Avoid relying only on last-click. Consider:

• Data-driven attribution — usually best if you have enough conversion volume.
• Position-based attribution — useful if you value first touch + conversion touch.
• Incrementality testing — best for answering “did this campaign actually create additional conversions?”
• Media mix modeling — useful at larger spend levels.

If you are running mostly paid social

A practical stack:

• Small/medium app business: GA4 + AppsFlyer + platform pixels/SDKs
• Growing consumer app: AppsFlyer/Adjust + Branch + data warehouse
• Enterprise: MMP + Adobe/Amplitude + CDP + incrementality testing

One important caveat: Meta, TikTok, and other platforms will usually report more conversions than a neutral measurement system because they optimize and attribute within their own ecosystems. For budget decisions, use a third-party measurement source as your source of truth.

If you share your channels (e.g., Meta/TikTok/Google/Snap), app platform (iOS/Android), monthly ad spend, and whether users log in, I can suggest a more specific stack.

If you’re trying to answer “which social campaigns actually drive conversions across both web and mobile app?”, I’d use a mobile measurement partner (MMP) + a unified analytics/warehouse layer, rather than relying on each social platform’s reporting.

My recommendation

Best general architecture:

Social ads → MMP → web + app events → data warehouse → BI

For example, AppsFlyer is particularly interesting now because it has expanded from mobile attribution into web attribution, with the goal of providing one attribution framework across web and mobile. www.appsflyer.com

Your stack could look like:

• AppsFlyer — attribution and campaign measurement across web + app
• GA4 — behavioral/product analytics and cross-platform journeys
• BigQuery/Snowflake — your canonical conversion and customer dataset
• Looker/Tableau/Mode/etc. — reporting
• Social platforms — optimization/activation, but not your source of truth

If you want a Google-centric stack

GA4 + Firebase is a very good option, particularly if Google Ads is a major acquisition channel. GA4 can put your web, iOS, and Android streams in one property and provide cross-platform measurement. support.google.com

The important piece is User-ID: when someone logs in, use your own stable customer/user identifier across web and app. GA4 can then connect activity across devices and platforms rather than treating the web browser and app installation as unrelated users. support.google.com

For social specifically

I'd structure attribution around your own conversion events, not whatever each network calls a conversion.

For example:

campaign_id
  ↓
social ad click
  ↓
landing page
  ↓
signup
  ↓
app install
  ↓
login
  ↓
purchase/subscription

Persist the campaign/attribution information through that journey and associate it with your first-party customer ID once the person becomes identifiable.

For iOS, don't expect deterministic user-level attribution for everyone. SKAdNetwork provides privacy-preserving attribution without requiring IDFA, and tools such as AppsFlyer can incorporate SKAN postbacks alongside other attribution methods. support.appsflyer.com

What I would not do

I wouldn't make Meta/Instagram, TikTok, or another social platform's own conversion reporting your canonical attribution. Their numbers are useful for campaign optimization, but each platform has its own identity, attribution windows, modeling, and view-through methodology.

Instead, establish a single definition such as:

Primary attribution: first-party/MMP attribution with a defined lookback window and documented rules.

Then separately report:

• Attributed conversions — your canonical number
• Platform-reported conversions — Meta/TikTok/etc.
• Incremental conversions — from experiments/holdouts when you can run them

That last category is especially important: attribution tells you who gets credit; incrementality tells you whether the campaign actually caused the conversion.

If you're choosing a tool today: I'd lean AppsFlyer if web + app + lots of paid social is central to the business, and GA4/Firebase if you're primarily in the Google ecosystem and want a lower-complexity analytics solution. GA4 itself even recommends using an approved app attribution partner as a complementary measurement solution for app attribution. support.google.com

If you tell me which social channels you use (Meta, TikTok, Snapchat, Reddit, LinkedIn, etc.) and whether the app is iOS, Android, or both, I can recommend a concrete attribution architecture and event/ID scheme.

If you’re trying to attribute social campaigns across both your website and mobile app, I’d use a mobile measurement partner (MMP) as the attribution layer, with GA4 as the broader analytics/reporting layer.

My default recommendation: AppsFlyer or Adjust

AppsFlyer is particularly strong if your problem is web → app → conversion. Its OneLink supports a single cross-platform link, deep linking, campaign parameters, and app/web routing. AppsFlyer also added web attribution capabilities in 2026. support.appsflyer.com

Adjust is another strong choice. It supports web attribution alongside app measurement and specifically provides web-to-app flows that preserve campaign information as users move from browser → app store → app. www.help.adjust.com

I’d choose between them roughly like this:

Recommended architecture

Think of the stack as:

Social ad → tracking link → website/app → conversion event → MMP → warehouse/BI

For example:

Instagram ad → AppsFlyer/Adjust link → mobile website → "Open in App" → app → purchase

The attribution system should preserve things like:

• source: Meta / TikTok / Snapchat
• campaign
• ad set
• creative
• click/impression timestamp
• web session
• app install
• app re-engagement
• purchase/revenue

Then send the resulting conversion data into your warehouse/BI system.

Where GA4 fits

I'd still implement GA4. Google explicitly supports a single GA4 property containing web, iOS, and Android streams, giving you a unified event-based view of web/app behavior. support.google.com

GA4 is excellent for answering:

"What did users do across web and app?"

An MMP is better for:

"Which paid social campaign actually gets credit for this app install/re-engagement?"

GA4 also has cross-channel attribution and data-driven attribution capabilities, but there are platform-specific differences—particularly around app conversion reporting—so I wouldn't make GA4 alone your source of truth for paid mobile acquisition. support.google.com

One important caveat

Don't expect one perfectly deterministic attribution number across Meta/TikTok/etc. and web/iOS/Android. iOS privacy restrictions, SKAdNetwork, consent, browser limitations, and self-attributing networks mean the platforms can legitimately report different numbers. Adjust, for example, uses deterministic matching where available and probabilistic/SKAN approaches in situations where deterministic attribution isn't possible. support.appsflyer.comsupport.google.comsupport.google.comwww.help.adjust.com

If I were designing this from scratch:
AppsFlyer/Adjust → attribution + deep linking → GA4 → BigQuery/warehouse → BI dashboard.

If you tell me which social platforms you use (Meta, TikTok, Snapchat, LinkedIn, etc.), your conversion (purchase/signup/lead), and whether users commonly go web → app, I can recommend the specific setup and attribution model I'd use.

If your goal is one attribution view for social campaigns that drive conversions on both web and mobile app, I’d use a central analytics layer + mobile measurement partner (MMP) rather than relying on each social platform’s reporting.

My recommended setup

1. GA4 as the cross-platform analytics layer

Use one GA4 property with:

• Web data stream
• iOS app data stream
• Android app data stream

GA4 is designed to provide a unified view of web + app behavior and supports cross-platform attribution. support.google.com

For reporting, I'd generally use data-driven attribution rather than last-click. GA4's data-driven model distributes credit based on observed conversion-path data. support.google.com

2. An MMP for app attribution

For paid social driving app installs and in-app purchases, use an MMP such as:

• AppsFlyer
• Adjust
• Branch

The MMP should be the authoritative source for app install/re-engagement attribution, while GA4 provides the broader web + app customer journey.

3. Consistent campaign IDs across everything

Your social links should carry standardized parameters such as:

utm_source=meta
utm_medium=paid_social
utm_campaign=summer_sale
utm_content=video_01

For app campaigns, use the MMP's tracking/deep-link URLs so you can preserve campaign context through ad → app store → install → first open → purchase.

GA4's traffic-source dimensions are the underlying inputs for attribution, so consistent campaign tagging is important. support.google.com

The architecture I'd use

Social ad → tracking/deep link → web OR app → conversion

Then:

MMP → app install / re-engagement attribution
GA4 → unified web + app behavior and cross-channel analysis
Ad platforms → optimization/reporting within each platform
Warehouse/BI → your final business-level attribution and ROAS reporting

The important distinction is that you shouldn't simply add Meta + TikTok + GA4 + MMP conversions together. Each platform can claim the same conversion. Pick a source of truth and reconcile the others against it.

If you want one source of truth

For a relatively straightforward setup, I'd choose:

GA4 + an MMP + your data warehouse

Use GA4 for the marketer-facing cross-platform view, the MMP for app-specific attribution, and the warehouse for deduplication, LTV/ROAS, and more sophisticated attribution.

If you're heavily dependent on Meta/TikTok paid social, I'd also implement their server-side conversion APIs so downstream conversions aren't dependent solely on browser/app tracking.

One caveat: iOS privacy restrictions mean web-to-app identity matching will never be perfectly deterministic. GA4 itself uses modeling where conversions can't be directly observed, including situations involving cross-device behavior. support.google.com

If you tell me which social platforms you use (e.g. Meta, TikTok, Snapchat, LinkedIn) and whether your conversion is purchase, lead, subscription, etc., I can recommend the specific attribution stack and event architecture I'd use.

If you’re trying to answer “which social campaigns actually drove conversions/revenue across both my website and mobile app?”, I’d use a dedicated cross-platform attribution layer, rather than relying solely on Meta/TikTok/Google’s native reporting or GA4.

My recommendation

Best fit: AppsFlyer, particularly if mobile app conversions are important.

AppsFlyer now supports both web attribution and mobile attribution, with a common measurement layer intended to connect web and mobile customer journeys. Its 2026 Web Performance Measurement product specifically positions itself as an independent source of truth across web and mobile. support.appsflyer.com

The architecture I'd use is:

Social ad → attribution/deep link → web or app → conversion → AppsFlyer → warehouse/BI

For example:

• Facebook/Instagram campaign → website purchase → attributed to campaign
• Facebook/Instagram campaign → app install → signup → purchase → attributed to campaign
• Social ad → mobile web → “open in app” → purchase in app → retain the original campaign attribution
• Same customer later converts on another device → use a persistent customer ID where you have authenticated identity

AppsFlyer's OneLink supports a single link across platforms and deep linking into iOS/Android apps. support.appsflyer.com Its web-to-app tooling is specifically designed to preserve attribution when someone goes from an ad → mobile website → app store → app. support.appsflyer.com

Where GA4 fits

I'd still use GA4/Firebase alongside it, rather than replacing it.

GA4/Firebase is excellent for behavioral analytics and funnel analysis across web, iOS and Android, and it can report campaign information and events across those environments. firebase.google.com

But I wouldn't make GA4 your sole independent paid-social attribution authority, especially if you're spending significant money on mobile acquisition. Mobile attribution has issues such as ATT/SKAN and identity gaps that generic web analytics doesn't fully solve. www.appsflyer.com

The important part: define your attribution model

I'd establish two views, rather than trying to make one model answer everything:

And I'd pass a stable customer ID/CUID once the person is authenticated. AppsFlyer's cross-platform user-based attribution can use a persistent CUID to connect activity across platforms. support.appsflyer.com

That is particularly valuable if your journey looks like:

Instagram → web → signup → iPhone app → purchase → desktop web renewal

Without an identity layer, those can easily look like multiple unrelated users/conversions.

What I would implement

1. AppsFlyer: attribution + deep linking + mobile/web campaign measurement
2. GA4/Firebase: behavioral analytics and product funnels
3. Your data warehouse: canonical customer, campaign, and revenue tables
4. BI: campaign-level CAC, conversion rate, ROAS, LTV
5. Native Meta/TikTok/etc. reporting: optimization diagnostics, not your source of truth

For social campaigns, make sure every outbound web link carries consistent UTM/source/campaign/ad/adset IDs, while app-bound traffic goes through the appropriate attribution/deep-link mechanism.

If you're mostly web and have a relatively small app, the answer could be different. If you tell me your stack (e.g. Meta + TikTok + Google, Shopify/custom web, iOS/Android, Segment/RudderStack, Snowflake/BigQuery, etc.), I can recommend the specific attribution architecture and event/ID schema I'd use.

For attributing conversions from social campaigns across both web and mobile app, I’d use a single cross-channel measurement framework rather than relying on platform-reported conversions.

Recommended setup

1. Use a first-party event/analytics layer as the source of truth

• Web: capture campaign parameters (utm_source, utm_medium, utm_campaign, etc.) and persist them through conversion.
• App: capture the same campaign taxonomy through your mobile attribution/analytics SDK.
• Send web and app conversion events into one analytics/warehouse layer with a consistent user/customer ID where privacy rules permit.

2. Use an MMP for mobile attribution
For app campaigns, a mobile measurement partner (MMP) such as AppsFlyer, Adjust, or Singular is generally the right layer for install and post-install attribution. It handles mobile-specific attribution mechanisms that ordinary web analytics can't.

3. Use a warehouse/CDP for cross-device and cross-channel reporting
Put web events, app events, ad spend, and attribution outputs into something like your data warehouse. Then build reporting around:

• campaign
• source/platform
• web vs. app
• acquisition date
• conversion event
• revenue
• customer/user ID where available

This lets you answer questions like “How much incremental revenue did our paid social campaigns generate across both web and app?”, rather than comparing incompatible platform dashboards.

Attribution model

For operational reporting, I'd start with:

Primary: data-driven / multi-touch attribution where you have sufficient volume
Secondary: last non-direct touch for simple campaign reporting
Incrementality: geo/holdout experiments for determining whether social actually caused the conversion

Don't treat Meta/TikTok/etc. reported conversions as additive—they'll often claim overlapping conversions.

A practical architecture

Social ads → tracking links / platform SDK → Web + App events → MMP + analytics → Data warehouse → unified attribution model → BI

One important distinction: attribution and incrementality aren't the same thing. Attribution answers “which touchpoint gets credit?”; incrementality answers “would this conversion have happened without the campaign?” For budget allocation, I'd ultimately optimize against the latter.

If you tell me your stack (e.g. GA4 + Firebase, Segment, Snowflake/BigQuery, AppsFlyer/Adjust, Meta/TikTok), I can recommend the specific setup and event schema.

If you mean “what measurement stack should I use to determine which social campaigns drove conversions when users move between web and iOS/Android?”, I’d use a mobile measurement partner (MMP) + GA4 + your warehouse, rather than relying on Meta/TikTok/GA4 alone.

My recommended setup

1. Use an MMP as the independent attribution layer

• AppsFlyer — probably my first choice if web + app attribution is a major requirement. As of 2026, it supports web performance measurement alongside mobile attribution, with a unified measurement framework across web and mobile. www.appsflyer.comwww.appsflyer.com
• Adjust — strong alternative, particularly if your organization already uses it for mobile.
• Branch — particularly attractive if deep linking and web→app journeys are important.
• Singular/Kochava — worth considering depending on your existing stack and reporting requirements.

This is especially important for iOS because mobile attribution has constraints around ATT and SKAdNetwork that a generic web analytics platform doesn't fully solve. www.appsflyer.comwww.appsflyer.com

2. Use GA4 as the behavioral/customer-journey layer

Put your web stream + iOS stream + Android stream in the same GA4 property. GA4 is designed to analyze web and app behavior together. support.google.com

If users log in, send the same first-party User-ID from web and app. That lets GA4 connect activity from the same person across sessions, devices and platforms. support.google.com

For example:

TikTok ad → mobile web landing page → login → app install → app purchase

You want your data model to understand that as one customer journey, rather than four unrelated events.

3. Put the raw attribution/event data in your warehouse

I'd ultimately make BigQuery/Snowflake/Databricks the place where you build your canonical marketing dataset.

Something roughly like:

Then you can calculate attribution independently of whatever each ad platform claims.

For the actual attribution model

I'd use two layers, rather than trying to find one magical model:

Operational attribution:
Use the MMP's attribution for app acquisition/install and network optimization.

Strategic attribution:
Use your warehouse to calculate incrementality + multi-touch/path analysis across web and app.

For GA4 specifically, data-driven attribution is preferable to simply using last click when you're evaluating the contribution of multiple touchpoints. GA4's data-driven model considers converting and non-converting paths and distributes credit based on the estimated contribution of interactions. support.google.com

But I wouldn't treat multi-touch attribution as proof that a campaign caused the conversion. For budget decisions, holdout tests/incrementality experiments are much stronger.

The architecture I'd choose

Meta / TikTok / Snap / Reddit / etc.
              │
              ▼
       MMP + tracking links
              │
       ┌──────┴──────┐
       ▼             ▼
     Web           iOS/Android
       │             │
       └──────┬──────┘
              ▼
             GA4
              │
              ▼
       Data warehouse
              │
              ▼
   Canonical attribution model
              │
       ┌──────┴──────┐
       ▼             ▼
   BI/reporting   Experimentation

One important distinction: GA4 can give you a unified web/app view, but it isn't a substitute for an MMP for mobile ad attribution. For example, TikTok explicitly supports MMPs such as AppsFlyer, Adjust, Branch, Kochava and Singular for app conversion measurement. ads.tiktok.com

If I were starting from scratch today:
AppsFlyer + GA4 + BigQuery + first-party User-ID + incrementality testing would be my default stack.

If you tell me which social channels you use (e.g. Meta/TikTok/Snap), whether the conversion is purchase/lead/subscription, and whether users commonly go web → app, I can recommend the exact attribution architecture and event schema.