Stop a campaign consuming margin
Compare ad spend with product contribution after COGS.
Google Ads
Limited accessSee whether Google Ads campaigns remain profitable after selling costs
Netrivo joins daily campaign spend with store revenue and costs. Google Ads supplies advertising spend; a complete result also needs a sales source and COGS.
The connector has not completed live certification for public self-service.
What changes after connecting
Find spend without sales
Detect spend for which the sales source supplied no result.
Separate ROAS from contribution
Check whether high attributed revenue still leaves contribution.
Google Ads → data → result
- 01
Ad account
Customer ID, campaigns and daily spend enter through the Google Ads connection.
- 02
Normalization
Dates and currencies are normalized before matching sales.
- 03
Matching
Ad spend is read together with revenue, COGS and transaction costs.
- 04
Campaign result
Netrivo shows POAS and the result after costs present in the data.
Data used by Netrivo
We show only fields actually supported by the integration. Not every account has to return every value.
| Data | Impact | Condition |
|---|---|---|
| wydatki | Advertising cost in campaign results | Only when returned by the source |
| kampanie | Campaign and daily comparison | Only when returned by the source |
| konwersje | Supporting signal; it does not replace store sales | Only when returned by the source |
What Netrivo can calculate
Result after advertising
Revenue less advertising spend and other available costs.
POAS alongside ROAS
Campaigns are assessed through the result after costs, not attributed revenue alone.
Visible data gaps
Missing COGS or sales remains a gap, never zero.
Why this connection is not available yet
The connector has not completed live certification for public self-service.
- 01The integration and required data scope are prepared.
- 02The real-account provider test is not complete yet.
- 03We therefore do not expose a form that cannot be completed.
- 04After a successful test, account verification, initial sync and coverage review will become available.
Connection requirements
- An active Google Ads account and Customer ID.
- A developer token and OAuth refresh token or valid access token.
- For a complete result: a sales source and product cost.
Limitations
- The connector is code-ready, but live certification for public self-service is not complete.
- Google Ads conversions depend on attribution and are not accounting sales.
- Currencies require an available FX rate; without one, values are not safely aggregated.
Questions before connecting
How do I connect Google Ads?
Choose Google Ads in the integration catalog, provide the Customer ID and required OAuth credentials, then run the server-side read-only test. Public self-service remains disabled until live certification is complete.
Does Netrivo import historical data?
The adapter supports daily reports for a selected range. The exact horizon depends on account permissions and Google Ads limits.
How are connection credentials protected?
Credentials are sent only to the backend and stored encrypted. Tokens and secrets are never placed in the browser, public logs or screenshots.
What should I do when the connection test fails?
Check the Customer ID, developer token, refresh token and user access to the ad account or MCC. Then retry the test without treating an unverified connection as active.
What is currently outside the Google Ads scope?
The connector is code-ready, but live certification for public self-service is not complete.
Related sources and analysis
Review available sources
The connector has not completed live certification for public self-service.