Google Ads

Guide · 31 Oct 2026

Google Ads app conversion values: check revenue and currency

For existing AppsFlyer or Adjust integrations, review the purchase amount, revenue-sharing settings, and currency behind the reported value.

G2P Media · · 4 min read

Google Ads app conversion values: check revenue and currencyGoogle Ads

At a glance

FieldDetail
WhatValidate the purchase amount and currency behind an app conversion value.
Who it matters toApp advertisers reviewing purchase revenue sent to Google Ads.
WhereGoogle Ads conversion actions supplied through AppsFlyer or Adjust.
When it appliesWhen reviewing existing purchase measurement or changing value settings.
ActionTrace the revenue fields and sharing settings before comparing totals.

Google Ads app conversion values should be reviewed as an amount, a currency, and a conversion-action setting. Our suggested sequence is to inspect the source purchase event, confirm what the measurement provider shares, and then compare equivalent conversion actions inside Google Ads. Keep a record of these checks alongside the existing integration.

Check what each part of the value path does

The following checks address different parts of purchase measurement. Apply the rows relevant to your integration.

CheckpointDocumented behaviorLimitationSuggested check
AppsFlyer fieldsaf_revenue maps to Google Ads value; af_currency maps to currency_code.af_price describes an individual item's price.Inspect the revenue amount and currency together.
Adjust sharingPurchase-revenue sharing requires the revenue option and a mapped revenue event.Mapping without that option sends counts without event data.Review both the sharing option and event mapping.
Adjust reportingRevenue-based metrics use the app's reporting currency.Reported amounts may have undergone currency conversion.Record the original and reporting currencies.
Google Ads settingsAn existing conversion action's Value setting can be edited.Changes apply to conversions occurring afterward.Record the change time before assessing results.

Inspect the purchase fields

AppsFlyer distinguishes af_price, an individual product price that can accompany an action without counting as revenue, from af_revenue, the total purchase amount counted as revenue. Its documentation says the revenue value must exclude comma separators, currency symbols, special characters, and text. AppsFlyer's event structure provides the field mappings.

Our suggested check is to retain a purchase-event example with its amount and currency, then ask the implementation owner to confirm which fields were populated. A populated price field alone should prompt a revenue-field review.

For Adjust integrations, check the In-app revenue sharing option and the mapped revenue event together. Adjust says this option covers in-app purchase revenue; it excludes revenue from displaying ads within the app. Treat that boundary as part of the measurement specification when reviewing a mixed monetization app. Adjust's Google Ads guide documents the distinction.

Separate currency conversion from missing revenue

Adjust converts monetary values into the app's selected reporting currency using daily exchange rates. Its callback placeholders can expose original amounts and currencies as well as converted amounts and currencies. However, the information sent to an integrated advertising partner depends on that partner's integration definitions. Adjust's currency documentation explains these reporting boundaries.

Our suggested approach is to label each amount as received or converted before comparing it. Do not assume that a value displayed in a measurement dashboard describes the exact currency representation sent to Google Ads. Partner transmission and dashboard presentation need their own checks.

Verify equivalent actions inside Google Ads

Google's comparison guidance concerns conversion actions within Google Ads. It explicitly excludes comparisons between Google Ads and a measurement provider's dashboard. Google recommends matching the app, platform, Value, Count, and conversion-window settings, then comparing conversion counts. It also advises matching the currency type and currency codes in events sent to Google Ads. Google's app conversion comparison guide recommends counts as the main reconciliation measure because a missing high-value event can distort a value comparison.

Use the symptoms below to choose a focused review, rather than treating every difference as the same measurement problem.

SymptomSuggested review
Purchase counts appear without expected revenue detailFor Adjust, inspect purchase-revenue sharing and the mapped event.
AppsFlyer records an item priceCheck whether the purchase total also populates af_revenue.
Values differ between imported actions inside Google AdsCompare counts and settings first, then check event currency codes.
Earlier values remain unchanged after editing ValueReview later conversions separately; Google documents prospective application.

What to review

These are suggested checks for your measurement review.

  • Check that purchase revenue and item price have distinct definitions in your event specification.
  • Review the revenue-sharing settings for the provider actually used by the app.
  • Keep original event currency separate from the currency used to display reports.
  • Compare equivalent conversion actions inside Google Ads using counts before interpreting value differences.
  • Record value-setting changes and evaluate subsequent conversions separately.

Use the measurement data-path review to document the amount, currency, sharing choice, and conversion action together.

Discuss your app.

Discuss your app