Skip to content

Beyonetix OS module

Ad Pilot: Google Ads, search data and shop revenue in one view

You see in one place what advertising and search contribute to revenue. A guard checks every proposal against the limits that apply to your account.

In short

Ad Pilot is the advertising module of Beyonetix OS (BEYOS). It reads Google Ads, Search Console and shop revenue separately for each tenant and shows what the advertising contributes to revenue. Today Ad Pilot does not write changes back into the ad account.

Updated: November 2026

What it is for

Who Ad Pilot is meant for

Anyone who advertises on Google and runs a shop usually keeps the figures in three places: the ad account, Search Console and the shop. Ad Pilot lays them side by side. You notice where Google reports more revenue than the shop booked, and where ads run for terms on which your page already ranks high.

Ad Pilot does not replace the Google Ads interface. It analyses, checks proposals and keeps a log. Today you make the change itself in the account.

  • Shop operators with their own ad account
  • Marketing leads who look at paid and organic search together
  • Teams that analyse several brands or accounts separately

Analysis

From the account to the search term

Every level of your account can be viewed on its own and compared with the others.

Campaigns down to ads Campaigns, ad groups, keywords and ads show their figures from Google Ads, each level on its own.
Search terms and patterns You see the actual search terms, plus an analysis by word groups, exclusion lists and audiences. Conspicuous terms stand out sooner.
Budget pacing The overview shows whether the daily budget fits the monthly target. You set the monthly target for each tenant.
on request Shopping and Performance Max Analysis of Shopping campaigns and Performance Max, split by channel.

Revenue

Revenue and measurement truth

Google counts revenue in its own way. Ad Pilot shows next to it what the shop actually booked.

Revenue from the shop Orders, products and channels from the shop sit next to the costs. One shop system is currently connected in operation, others we settle in the project.
Actual return on advertising Revenue from advertising according to the shop sits beside the figure Google reports. Google's count is shown separately.
Do the numbers add up? The report shows where Google reports more than the shop, which actions count twice and which are used for bidding. It also covers where orders come from and how good the data is.
on request Real value and customer value What an order is really worth after cancellations and what a new customer brings over time.
on request Monthly report A report to pass on to the shop operator.

Search

Search and visibility

Paid and organic search sit side by side, so you do not pay twice.

Search Console next to advertising Search performance, keywords, pages and click rate sit next to the ads. The "Paid twice" view shows terms you pay for while also ranking well organically. Pages that take clicks from each other become visible.
Visibility and competitors Visibility index, topics, competitors and opportunities from the interplay of organic and paid. The data comes from an external SEO service whose monthly quota limits the volume.
on request Visit data from Analytics We set up the connection of Analytics data for reconciliation per project.

Budget protection

Check first, then change

A guard sits in front of every change. It works with fixed rules and does not ask a language model.

Guard for the money It checks daily and monthly limits, step sizes and learning phases. More on budget protection
Dry run Every change is checked first in the dry-run mode of the Google interface. You see what would change before anything happens.
Emergency stop It locks the write route at once, for one tenant or for all at the same time.
Separate per tenant Each tenant sees only its own data.

Approval

Approval and log

Proposals wait for a decision. What happens stays traceable.

Approval inbox Proposals arrive as approvals with a preview in euros. Several changes can be reviewed together as a bundle. A person decides.
Change log The log shows changes, including those someone made directly in the account, and the quotas used.
Roles and permissions Fixed permissions govern who may view, analyse, manage and approve.

Proposals

Assistant, agents and rules

These building blocks are developed and set up on request. They propose. Nothing is carried out without your decision.

on request Assistant in the console You write in plain language what you want to change. A proposal comes out of it. Every value in it must appear in your sentence or be backed by your data.
on request Agents with roles Roles such as analysis, budget or keyword research propose changes in a fixed schema. By default every proposal needs approval. To the agent platform
on request Rules and daily briefing Rules create approvals, anomalies are only reported. A briefing sums up the situation and tasks for each tenant.

Process

How you work with Ad Pilot

Six steps from the first account to the log.

1 Connect accounts For each tenant you connect the Google Ads account, Search Console and the shop. Analytics can be added.
2 Fetch the data Ad Pilot fetches the data regularly, from the campaign down to the search term.
3 Analyse You read the daily overview, the advertising, the revenue, the visibility and the report "Do the numbers add up?".
4 Check Every proposal for a change first passes the dry run and the budget guard.
5 Approve The proposal waits in the approval inbox with a preview in euros. A person decides.
6 Apply and look back Today you apply the approved change yourself in the account. The log records what happened, including changes made from outside.

Technical details

What Ad Pilot connects and how it works

Technical details of Ad Pilot
PropertyDetail
Data sources Google Ads, Search Console, shop revenue, plus visibility data from an external SEO service. Analytics and Merchant Center on request.
Shop systems One shop system is connected in operation. We discuss others in the project.
Tenants Data and reports are separated per tenant, and the monthly target applies per tenant.
Write route into the ad account Switched off until approved. Dry run and guard check proposals all the same.
Budget guard A fixed rule set without a language model, placed in front of every change.
Permissions Fixed permissions for viewing, analysing, managing, approving and user administration.
Interface The console is in German.
Integration into Beyonetix OS Ad Pilot runs as a building block of its own. We work out the link to other modules in the project.

Questions and answers

Questions about Ad Pilot

Does Ad Pilot write changes into my Google Ads account?

Not today. Ad Pilot reads, analyses and checks proposals. The route that writes changes into the account is switched off until it has been approved. You apply an approved change yourself in the account.

Which data sources does Ad Pilot use?

Google Ads, Search Console and the revenue from your shop. Visibility data from an external SEO service comes on top. Analytics can be connected on request.

What does "Do the numbers add up?" mean?

The report puts the revenue Google reports next to the orders in your shop. It shows where Google reports more, which actions are counted twice and which ones feed the bidding.

How is my budget protected when a proposal is wrong?

Every proposal passes a dry run and a guard with fixed rules, then lands in the approval inbox. A person decides there. An emergency stop locks the write route at once.

Can I keep several brands or accounts apart?

Yes. Ad Pilot works with tenants. Each tenant sees only its own data, and the monthly target applies per tenant.

Is Ad Pilot part of Beyonetix OS?

Yes, it is the advertising module of the platform. How far it is linked to other modules we settle in the project.

Do you know what your advertising contributes to revenue?

We look at your accounts and your shop and discuss what can be analysed.