How Jarva runs advertising through official platform APIs
Jarva builds and operates a portfolio of its own consumer brands, and we run paid advertising for those brands in-house. Because we operate several brands at once, we manage advertising through an internal marketing-operations platform that connects to each advertising platform using its official API — rather than logging into each ad account by hand.
The platform, in plain terms
Our internal tool is a private, in-house system used only by Jarva to operate advertising for the ad accounts we own. It is not a product we sell, and it is not offered to anyone outside Jarva. Across every connected platform, it uses the platform's official API to:
- Create and configure campaigns, ad groups / ad sets, and ads for our own brands
- Set and adjust campaign budgets, bids, schedules, and targeting based on performance
- Manage keywords, audiences, and creative, and change campaign or ad status (pause, resume, archive)
- Retrieve performance reporting — impressions, clicks, conversions, and spend — into our internal dashboards for cross-platform analysis and budget allocation
Google Ads API
We use the Google Ads API to programmatically manage the Google Ads accounts we own and operate under our own Google Ads manager account.
Only our own
Every Google Ads account we access through the API is owned and operated by Jarva under our own manager account.
None
We do not manage advertising on behalf of outside parties, agencies, or clients.
No
We do not resell, sublicense, or otherwise provide Google Ads API access to any third party.
What we do with the Google Ads API
- Create and configure campaigns, ad groups, and ads for our brands
- Set and adjust campaign budgets and bids based on performance
- Manage keywords, audiences, and campaign status
- Retrieve performance reporting (impressions, clicks, conversions, spend) into our internal dashboards
Campaign types we manage
Search, Performance Max, Display, and Shopping campaigns for the direct-to-consumer brands we own. We do not manage App or Local campaigns.
How access is authorized
The platform authenticates with OAuth 2.0 credentials for our own Google user, together with our developer token and our manager account. All calls are scoped to customer IDs belonging to that manager account.
How the system is put together
Four layers, all private to Jarva. Nothing in this stack is exposed publicly or offered to anyone outside the company.
Auth
Securely stores our OAuth refresh token, developer token, and manager account reference, and obtains access tokens as needed.
Orchestration
Issues API requests to create and adjust campaigns and to pull reporting, on a schedule and on demand.
Data store
Retrieved performance metrics are written to our private internal database — never to a public endpoint.
Dashboard
An internal, authentication-gated view where our team reviews cross-platform performance and directs budget. Access limited to Jarva personnel.
The other platforms
We use the same in-house pattern on each platform's official API — always limited to accounts we own and operate.
Marketing API
Manage campaigns, ad sets, ads, budgets, and audiences, and pull reporting for our owned ad accounts.
Reddit Ads API
Create and manage campaigns and ads and retrieve performance data for our owned account.
Pinterest Ads API
Manage campaigns, ad groups, and ads and pull reporting for our owned account.
TikTok Marketing API
Manage campaigns, ad groups, ads, creative, and reporting for our owned account.
Data & scope of use
We use these platforms' APIs and the data they return only to operate advertising for accounts we own. We do not sell data obtained through advertising-platform APIs, we do not share it with unrelated third parties, and we do not use it to build products for anyone outside Jarva. Full details are in our privacy policy.
Developer & API contact
For questions about our API use or this integration.