GA4 has just opened a door that had been closed for far too long: app conversions are now included in certain cross-channel reports. It sounds like a full view of the customer journey. Not so fast. Google is letting us look into more rooms, but it is still keeping a few keys in its pocket.
TL;DR: The no-nonsense summary
- More app data: GA4 adds these conversions to performance reports, attribution analysis and attribution models.
- Separate attribution: app settings can be managed independently from web settings.
- Gradual rollout: the feature may not yet be available in your property.
- Incomplete budgeting: cross-channel budgeting remains limited to web conversions.
In this article
App conversions in GA4 are actions recorded in an app that Analytics presents as conversions compatible with Google Ads. Since September 29, 2026, they may appear in three areas: conversion performance, attribution analysis and attribution models.
The expansion appears in the official Google Analytics release notes. And the key word is “may.” Google is expanding access property by property and has not published a timetable for completing the rollout.
What do app conversions add to GA4?
App conversions let you compare how channels contribute to a conversion, when they enter the journey and how much credit they receive under the selected model. That is far more useful than looking at a final number and pretending the last click did all the work.
In the cross-channel performance report, you can select conversions, choose an attribution model when using the Analytics view, and switch between conversion time and interaction time.
That final distinction matters. Conversion time places the result when the final action happened. Interaction time places it when the credited touchpoint occurred. If a campaign assisted a conversion days earlier, the two views can tell different chronological stories without either one necessarily being wrong.
Last-click analysis adds another layer: it lets you compare assists and last-touch conversions using metrics such as conversions, revenue and ad cost. The last-click model documentation also includes traffic-source filters.
In plain advertising-account terms: you may uncover a campaign that rarely closes the deal but often appears before the channel that gets the credit. That does not prove the campaign caused the sale. It does prevent you from writing it off solely because it did not finish the play.
What changes in GA4 attribution models?
GA4 lets you adjust attribution for app conversions separately. Web and app no longer necessarily have to rely on a single configuration for credit allocation in compatible reports.
Google does not detail every setting that can be controlled independently in the announcement. Promising surgical-level customisation would be reading more into the documentation than is there, a popular sport whenever Analytics launches something new.
In data-driven analysis, GA4 estimates the impact of each interaction. It then categorises touchpoints in multi-touch journeys as early, mid or late, and separates single-touch journeys, according to the official explanation of the data-driven model.
What does that give you? You can see which channels tend to open the journey, which ones nurture it and which appear close to conversion. Comparing this with last click reveals campaigns whose apparent value changes dramatically depending on the model.
Be careful: attribution is not causality. A model allocates credit using the information it observes and its own rules. It does not prove what would have happened if you had switched off a channel. That distinction separates useful analysis from a slick presentation that can justify any budget.
App attribution does not cover the full organic journey
App conversions imported from Analytics into Google Ads are attributed using Google paid channels. The option that combines paid and organic channels applies only to web conversions.
This limitation is documented in GA4 attribution settings. So this update is still far from offering complete app attribution across advertising, organic traffic and every other touchpoint.
Nor do all key-event-related reports automatically receive app data. Google cites Attribution Paths as an example of a report that may not support it, and recommends using key events where appropriate. Before celebrating a unified view, check each report individually.
Can GA4 budget across web and apps yet?
Short answer: no. GA4 cross-channel budgeting still supports web conversions only. Being able to analyse apps more effectively does not remove that limitation.
The tool’s forecast plans and scenarios are for planning. They do not modify budgets or spending in linked accounts, as Google explains in its cross-channel budgeting documentation.
This is the editorial trap in the announcement: seeing app conversions in more reports does not mean you can allocate money between web and apps from the same system. Analysis and budgeting are two different capabilities. Mixing them turns a real improvement into a promise Google has not yet delivered.
If you run campaigns linked to Analytics, review your structure, goals and measurement before changing investment, too. The complete guide to Google Ads gives you the context you need to avoid turning a reporting change into an automatic bidding decision.
What to check before using these reports
Availability must be checked in every property. Google has not confirmed dates for Spain or the European Union, public eligibility criteria or a global activation schedule.
First, check whether your app conversions appear in the three announced areas. If they do, compare conversion time with interaction time. Then review assists against last touch and compare the outcome with the data-driven model.
And do not move budget merely because a campaign gains credit when you change models. My view is fairly clear: this update improves diagnosis, but it also multiplies the ways to tell a convenient story. More columns do not create better judgement.
App conversions in GA4 finally provide a less one-sided view for those working with Google Ads. That is welcome. But access is still rolling out, organic app attribution remains excluded, and budgeting is still locked to web. It is a useful step forward. The full business view will have to wait.
