Skip to main content
Dashboards can pull revenue from analytics platforms, ad platforms with revenue tracking, e-commerce systems, and uploaded files — and combine that revenue with ad spend to compute ROAS.

​
Where revenue can come from

Revenue is available from many connected data sources. Common ones, for example:
  • Analytics platforms — Google Analytics 4, Piano Analytics, Amplitude
  • Ad platforms with revenue tracking — Google Ads, Meta Ads, TikTok Ads, Criteo, Pinterest Ads, X (Twitter) Ads (revenue / conversion value depends on conversion tracking being set up on the platform)
  • MMPs — AppsFlyer, Adjust, Branch, Singular
  • E-commerce — Shopify, WooCommerce, Shopee, Lazada, Amazon Vendor Central
  • Custom imports — CSV files, Google Sheets, BigQuery, PostgreSQL
If a needed platform isn’t connected yet, browse the full list under the Data sources tab.

​
How to add revenue to a dashboard

1

Confirm the revenue source is connected

Open the Data sources tab and check that the analytics, ad, or e-commerce platform supplying revenue is listed and has no warning icon.
2

Add or open a widget

Add an ads table, custom table, or single-metric widget where the revenue should appear.
3

Pick the revenue metric

In the widget’s settings panel, select the relevant revenue or conversion-value metric — for example, Revenue, Conversion value, or a conversion-specific metric.
4

Add ROAS if needed

For native ad-platform ROAS (Google Ads, Meta, TikTok), pick the platform’s ROAS metric. For ROAS that combines an e-commerce revenue source with ad spend, use a data blend.

​
If revenue still isn’t showing

The dashboard can only show revenue events that the platform itself receives. For example, Meta Ads only exposes purchase / conversion value events that Meta Ad Manager already receives from the Pixel. If the platform’s Pixel or tag isn’t configured to fire purchase events with a value, no revenue will appear in the dashboard.See the connector-specific troubleshooting page for setup specifics — for example, Meta Ads, Google Ads, Google Analytics 4.
Open the widget settings panel and confirm the selected metric is a revenue metric, not a count metric like “Conversions”. For Meta, prefer Conversion value (Purchase, 7d Click) or similar, not “Purchases”.
When an ad account’s currency differs from the workspace currency, conversion values are converted to the workspace currency at the day’s exchange rate. See Multi-currency reporting for the details.
For ROAS widgets that blend revenue from an e-commerce source with ad spend, mismatched join keys, date formats, or campaign-name spellings will produce empty or zero rows. See Data blending and Data integration FAQs.
Newly connected e-commerce sources can take time to backfill historical orders, and most ad-platform conversion data arrives with a delay due to attribution windows. See Refresh strategies.

​
Still stuck?

Contact support

Include the dashboard URL, the widget settings, and the names of the connected revenue data sources.