The workspace exists to answer one question repeatedly: is this merchant worth advertising? Everything below is in service of that.
Step 1 — Connect the networks
I add my own API credentials for each affiliate network I belong to. The workspace stores them encrypted and uses them only when I ask it to, to pull the list of programmes my account has been approved for.
Credentials belong to the account that saved them. The workspace never uses one person’s network credentials to do work for anyone else, and background jobs are restricted to the operator’s own keys.
Step 2 — Compare and shortlist
For each programme the workspace shows what the network publishes: commission rate, cookie duration, the regions where promotion is permitted, whether deep linking is allowed, and the merchant’s own description of the offer. Where a network does not publish a field, the workspace leaves it blank rather than guessing — and where a value is inferred rather than published, it is marked as inferred.
Alongside that sit two figures that help size a merchant: a third-party estimate of monthly visits, and the merchant’s public customer review score. Both are sourced here.
Step 3 — Research the keywords
For a shortlisted merchant I ask for keyword ideas from a seed term or from the landing page I intend to advertise, with average monthly search volume and the top-of-page bid range, for the country I plan to target. This is a read-only call to the Google Ads API.
I then write the ad copy and the landing page myself, and check the headline and description lengths before anything is sent.
Step 4 — Create and manage the campaign
This is the step the access request is for, and it is not built yet — today I do it by hand in the Google Ads interface. When it is built it will work like this:
- The campaign is validated against the API first, without being created, so errors surface before anything touches the live account.
- It is then created paused: budget, campaign, location and language targeting, ad group, keywords and a responsive search ad.
- I review it in the Google Ads interface, and only then confirm it should be enabled.
- Afterwards the reporting calls show which search terms spent money without converting, and I add those as negative keywords once I have approved the list.
Each of those write operations will be a separate confirmation, and nothing in the chain will happen on a schedule. The safeguards page lists what the tool will not do at all, and which guards are already in the code.
Who can open it
The workspace is login-only. Accounts are created by me, not by public sign-up, and a new account sees nothing until I approve it. It runs on a private server behind HTTPS with no public interface to its data.