ROAS tracking
Put ad spend next to the first-party traffic and revenue it produced, so return on ad spend comes from your own data rather than a reconciliation spreadsheet.
Spend meets on-site behaviour
Modovisa matches spend against the utm_campaign values your links actually carried. Because both sides live in the same workspace, a campaign row leads directly to the sessions it produced and, on paid plans, to replays of those sessions.
- Enter spend manually, or import it with Ads Connect on Pro Lite and above
- ROAS shown alongside UTM tables in the Campaigns workspace (Growth+)
- First-party numbers, not a second platform's modelled attribution
Why platform ROAS and site ROAS disagree
Ad platforms report conversions they can attribute, using their own windows and modelling. Your site sees the visits and outcomes that actually happened. Neither is lying; they are measuring different things. Having a first-party number gives you something stable to compare against.
Getting a usable number
It comes down to disciplined tagging and consistent spend entry. The Campaigns link builder handles the first; Ads Connect handles the second by syncing Meta and Google Ads spend over OAuth so nothing depends on someone remembering to update a sheet.
Plans and limits
Free is $0 for 1,000 events a month on one site with 30 days of history. Standard is $14.99 for 25,000 events, Growth $29.99 for 100,000, and Pro Lite $49.99 and up for 250,000+ — paid plans include unlimited sites and unlimited retention.
Frequently asked questions
Which plan do I need for ROAS?
Growth for the Campaigns workspace and ROAS views with manually entered spend. Pro Lite and above adds Ads Connect for automatic spend import.
Which ad platforms can be connected?
Meta Ads and Google Ads, connected over OAuth on Pro Lite and above.
Will my ROAS match what Meta or Google reports?
Usually not exactly. Modovisa reports on first-party sessions tied to your UTM parameters, while ad platforms apply their own attribution windows and modelling.