- What does ROAS mean here, and where does revenue come from?
- ROAS is platform-reported by default: Google Ads conversion value over cost, Meta purchase value over spend, each on the attribution window set in that platform. Where GA4 is connected you can switch a workspace to GA4 revenue, which removes cross-platform double counting but drops view-through. The source is shown on every card and in every report. Shopify order data lands in Q4 2026, which adds order-level revenue, blended MER and new-customer CPA next to platform ROAS.
- Does it account for incrementality?
- Not with lift tests, no. Recommendations use platform and GA4 data, so retargeting and brand search are read with that in mind: a finding on those campaigns says so, and a budget move into them is capped at 25% of the campaign budget per step, with a re-read after seven days before the next step. Revenue estimates are shown as a range that decays with budget (the top of the range assumes current returns, the bottom assumes half of them on the added spend). If you run holdouts or an MMM, their results do not feed MarketLin today.
- How does it handle learning phase and seasonality?
- A finding needs the campaign or ad set to be out of learning phase, the conversion volume to be above a minimum, and the change to hold against a 60-day baseline. A year-over-year check flags seasonality where a year of history exists. The basis is printed on every finding, so you can disagree with it.
- What can MarketLin change in my accounts?
- Nothing on its own. It reads daily and drafts changes. A change is applied only after a person in your workspace with approval rights confirms it, and every applied change is logged with who and when. An owner switches on applying approved changes per workspace, and can switch it off again; until then, approving hands you the change list to apply yourself.
- Who on my team can do what?
- Three roles per workspace. Owner: billing, connecting and disconnecting accounts, approving changes, inviting people. Admin: connecting accounts, editing brand context, approving changes, scheduling and sending reports. Member: sees the clients assigned to them, drafts ads, prepares reports, and can approve changes only if an owner grants it. Clients do not log in; they receive the reports you schedule.
- Which scopes, and why does Google Ads look like full access?
- Google Analytics and Search Console use read-only scopes. Google Ads has no read-only scope, so the standard scope is requested and the approval rule above is what limits its use. Meta uses ads_read and business_management; ads_management is requested only if you turn on applying approved changes. The full table is in the Privacy Policy.
- Where is data processed?
- Stored on Google Cloud in Stockholm. The AI models that write recommendations and ads run with US providers (Anthropic, OpenAI, Google) under EU transfer safeguards and receive aggregated campaign metrics and your brand context, not end-customer personal data. The sub-processor list names every one of them.