Report on cross-environment conversions

Measure conversions across different devices and environments like mobile and desktop

People own multiple devices that can access the Internet, and will often view your ads in one environment and then convert on another. Cross-environment conversion reporting shows the effectiveness of your advertising campaign across all environments (tablet, mobile, and desktop; app and web), regardless of the device or environment a user converts on. 

Cross-environment reporting links together cookies (for web), resettable device IDs (for mobile apps), and anonymized Google sign-ins, to identify a user across different environments.  This allows Google to determine the path taken by the user, from first seeing an ad to conversion. No data about the specific user is retained and all reporting is anonymized.

Cross-environment conversion reporting can be complex due to the nature of attribution and conversion tracking in apps. Cross-environment conversions that occur on devices or browsers other than the original ad can be attributed differently, or not measured at all, compared to traditional cookie-based conversion measurement. But overall, including cross-environment metrics will offer a more complete conversion picture in your reporting.

Generate a cross-device conversions report

To generate a cross-device conversion report in Report Builder, click the New Report dropdown and choose Standard > Cross-Device Conversions.

Cross-environment conversion metrics:

Cross environment metrics include both standard conversions and cross-environment conversions. These metrics include conversions from users across different environments, such as an app and a browser, or two different browsers, regardless of if the different environments were on a single device or multiple devices.

Relevant dimensions for cross-environment metrics:

Limitations

  • Mobile device IDs must be passed back for cross-environment reporting to work. (Google Ad Manager publishers do this automatically.)
  • Floodlight tags and activities must be implemented correctly for cross-environment reporting to work.
  • Custom Floodlight variables are incompatible with cross-environment reporting.
  • There is very little cross-device data in China.
  • In-app browsers are complex, and have varying compatibility with cross-device reporting.
  • Cross-device reporting is not supported at an event level in Data Transfer.
Was this article helpful?
How can we improve it?