RevenueFlex GAM Reporting

RevenueFlex GAM Reporting

The application RevenueFlex uses to run and extract reports, and to create and maintain ad units, in the Google Ad Manager networks it operates on behalf of its publishers — and a free, self-service report download and inventory management service that any Google Ad Manager user can connect their own network to.

What it is

RevenueFlex is an ad monetization service for mobile game and mobile app publishers. Publishers run RevenueFlex's Google Ad Manager ad units in their apps, and RevenueFlex creates, prices and reports on those ad units under its own Google Ad Manager network and the child networks of publishers who have delegated their inventory to it through Google's Multiple Customer Management (MCM) program.

RevenueFlex GAM Reporting (internally "App Manager") is the server application that does this work. It has two parts:

Reporting

Runs Ad Manager reports — impressions, unfilled impressions, eCPM and revenue per ad unit, app and publisher network — and extracts them into RevenueFlex's own database so revenue can be reconciled and paid out to publishers.

Ad unit creation

Creates ad units and placements for publishers' apps in the managed networks, and verifies that each one exists, is active and is priced as intended.

Data extraction

Downloads report and configuration data on a schedule and makes it available to RevenueFlex operators and to each publisher for its own ad units and apps.

Public report downloads and inventory management

The public service is the same reporting and inventory code, offered as a free service to external Ad Manager users on their own networks. It works like this:

  1. Sign in with Google. Google asks you, on its own consent screen, to let the service see your e-mail address and access Google Ad Manager on your behalf. The service records your Google account e-mail and account id and keeps the refresh token Google issues, encrypted, on its server.
  2. Choose a network. The service lists the Ad Manager networks your Google account can see; you pick the one to report on.
  3. Download reports. Pick a report from the catalogue (network, ad unit, app, country, device, creative size, placement, order and line item, advertiser and child-network breakdowns, daily or hourly) — or one of the reports you saved in Ad Manager yourself — a date range, and CSV or ZIP. The service runs the report in Ad Manager, streams the result straight to you and keeps none of it — only a log line saying which report, network and date range was downloaded and how many rows it had.
  4. Manage inventory, if you want to. On the account page, or through the API, you can search, create, activate, deactivate and archive ad units and placements, change which ad units a placement holds and which teams an ad unit belongs to, and list, invite and manage the MCM child publishers of a parent network. Each change is made in the network you chose, with your own Ad Manager rights, and is written to a change log on your account (what was changed, when, through the page or which key, and whether Ad Manager accepted it). Nothing is ever deleted — Ad Manager itself offers archiving, not deletion, for ad units and placements, and the service offers nothing beyond that.
  5. Automate it. From the account page you can create API keys, each with a name, an expiry date (or none) and a set of capabilities — catalogue reports, saved reports, inventory read, inventory write, MCM read, MCM write — and revoke them at any time. A key can do only what its capabilities allow; keys with no write capability cannot change anything. Your own programs then use plain HTTPS requests; the API reference describes the calls.

The catalogue report definitions are built in code by the service; your saved reports are read from your network only when you ask to list or run them. Changes are made only in the network you chose, only when you ask for them on the page or with a key that holds the matching write capability, and never on their own schedule — the public service runs no jobs of its own. You can disconnect your Google account or delete your account and everything stored about it from the account page at any time. A form on the same page lets you ask for reports the catalogue does not yet have.

Which Google data it accesses, and why

The application connects to the Google Ad Manager API and, for signing in to the public report service, to Google's OpenID Connect endpoint. It requests these OAuth 2.0 scopes:

ScopeWhat it grantsWhat the application does with it
https://www.googleapis.com/auth/admanager View and manage the Google Ad Manager networks the authorizing account administers. Operations application: runs and downloads reports; lists, creates and verifies ad units and placements; reads app, network, team and pricing configuration — all within the networks RevenueFlex manages.
Public service: lists the networks your account can see; runs and downloads the catalogue reports and your saved reports on the network you chose; reads its ad units, placements, teams, apps and child publishers; and, only on your explicit request (page action or an API key you gave the write capability), creates ad units and placements, changes their status, membership and teams, and invites or manages child publishers there. Nothing is deleted.
openid, email Your Google account id and e-mail address (public report service only). Identifies you when you sign in to the report service, so your network choice, API keys, download log and change log belong to you and to nobody else. The operations application does not request these scopes.

It does not request or use access to Gmail, Google Drive, Contacts, Calendar, YouTube, Google Analytics or any other Google service, does not request your name, profile picture or other profile information, and does not access the personal data of any end user of a publisher's app. The Google account involved is that of an Ad Manager user, and the application uses it solely to act on the network that user chose. A full description of what is collected, how it is stored and how long it is kept is in the Privacy Policy.

How authorization works

  1. An administrator of a Google Ad Manager network that RevenueFlex manages starts the connection from inside the operations application — or an external user clicks Sign in with Google on the public service — and is sent to Google's standard OAuth consent screen.
  2. Google shows the scopes above; the user grants or declines them. Nothing is accessed before consent.
  3. Google returns a refresh token to the application's server, where it is stored privately. It is never sent to a browser, a publisher, or any third party.
  4. From then on the application calls the Ad Manager API from its own servers with short-lived access tokens minted from that refresh token.
Revoking access. Anyone who authorized the application can withdraw its access at any time from their Google Account at myaccount.google.com/permissions, or by asking RevenueFlex at info@revenueflex.com. Users of the public service can also click Disconnect Google access or Delete my account on their account page. Once revoked, the stored token stops working immediately and is deleted.

Who operates it

RevenueFlex GAM Reporting is operated by RevenueFlex, the ad monetization service at revenueflex.com. The application runs at appmanager.revenueflex.com (the public service under appmanager.revenueflex.com/reports/), on infrastructure RevenueFlex controls. Questions about the application, its Google integration or these pages: info@revenueflex.com.

Policies