Google Ads and Meta Ads, run with written rules.
We build and run your Search, Shopping, Facebook and Instagram campaigns: keywords, feeds, audiences, ads and tracking. Every campaign starts paused, has a daily cap and a stop-or-scale rule decided before launch — and goes live only with your OK.
How we run ads
- Search and Shopping (Merchant Center)
- Meta
- Facebook and Instagram
- Start
- Paused, live only with your OK
- Budget
- Daily cap on every campaign
- Accounts
- In your name; you pay Google or Meta
Search and Shopping
Search campaigns
Built and run through the official Google Ads API from our own tools: exact keywords, negative keywords, tight ad groups, a daily budget cap and a maximum cost per click.
Shopping and Merchant Center
Product feeds cleaned and kept accurate in Merchant Center. For a shop client, we got a 16-country feed of 345 products approved.
Facebook and Instagram
Campaigns and creatives
Campaigns, ad sets and creatives, boosts of your Instagram posts, and A/B tests to compare versions before spending more.
Pixel and Conversions API
The Meta pixel on your site, and purchases sent server-side through the Conversions API, so results are counted from your own data.
Rules we apply to every campaign
Paused until you say go
Campaigns are created paused and go live only with your explicit OK.
A daily cap
Every campaign has a daily budget cap. Google notes a campaign can spend up to twice its average daily budget on a given day, but no more than 30.4 times it over a month — we plan with that in mind.
A stop-or-scale rule, written first
Before launch we write the rule that decides what happens next, for example: "3 or more sales under the target cost: scale; 0 or 1: stop" — and we read it at day 14.
Your accounts, your data
Ad accounts, pixels and data stay in your name. The ad spend is paid by you directly to Google or Meta.
Counting what really happened
Ads are only as good as the tracking behind them. We set up GA4 with a consent banner where Refuse is as easy as Accept, and the e-commerce events Google documents for a shop — add to cart, begin checkout, purchase — as we have on 26 of our own selling sites. On the Meta side, the Conversions API connects the sales recorded by your server to Meta's systems.
Related
Sources (checked 6 October 2026)
- Google Ads Help — About keyword matching options
- Google Ads Help — About negative keywords
- Google Ads Help — Overdelivery and average daily budgets
- Google Merchant Center Help — Product data specification
- Meta for Developers — Meta Pixel
- Meta for Developers — Conversions API
- Google Analytics — Measure ecommerce
Frequently asked questions
Who pays for the ad spend?
You do, directly to Google or Meta, from ad accounts in your name. Every campaign has a daily budget cap.
Can a campaign start without my approval?
No. Campaigns are created paused and go live only with your explicit OK.
When do you decide whether a campaign works?
Before launch we write a stop-or-scale rule, for example "3 or more sales under the target cost: scale; 0 or 1: stop", and we read it at day 14.
Do you guarantee a return on ad spend?
No. We guarantee the set-up, the caps, the rules and an honest reading of the results — not a ROAS figure.
Do you handle Google Shopping?
Yes, with product feeds in Merchant Center. Google uses that product data to match products to searches, so we keep it accurate.
Why use the Meta Conversions API as well as the pixel?
The pixel tracks actions in the browser; the Conversions API sends events such as purchases from your server to Meta, so sales are counted from your own records.
Which campaign should run first?
Tell us what you sell and where: we will send you the campaign plan, its daily cap and its stop-or-scale rule.