Skip to main content
The Adjar CLI is the primary interface for managing your Google Ads accounts as version-controlled TOML config. Set up your credentials, then use import, plan, apply, and report to pull your live account into plain text, review every proposed change as a human-readable diff, push updates back to Google Ads with full confidence, and measure the result. The entire workflow is designed to be auditable, reversible, and automation-friendly. Not installed yet? The Quick Start covers installation and your first end-to-end loop.

​
The core workflow

Adjar keeps two kinds of plain-text artifact in a git repo: your ads config (.toml) — the source of truth for campaigns, keywords, budgets, and creatives — and your performance reports (.md). The four commands move data between your live Google Ads account and those files, and an AI agent reads and edits them to drive the loop. Every change is a git commit, so the whole account carries a reviewable, revertible history — and the report from one round becomes the input to the next. The Adjar core workflow as a loop: adjar import pulls the live Google Ads account into plain-text TOML config, and adjar report pulls performance into Markdown reports — both versioned in git. The AI agent reads the reports and edits the config; adjar plan shows you the diff, you review and approve, and adjar apply pushes the change back to Google Ads. Each command is defined by what plain-text file it produces or consumes:
1

Import — produces the ads config

adjar import reads your live account and writes it out as TOML config. Run it once to get started, or again any time to refresh from the live account. Commit the result as your baseline — every future change is a diff against it.
2

Plan — consumes the config, produces a diff

Edit the TOML files (by hand or via your agent), then run adjar plan to preview every change as a human-readable diff against the live account. Plan is read-only — it never touches Google Ads. Nothing ships until you’ve seen exactly what will change.
3

Apply — pushes the config to Google Ads

Once the plan looks right, adjar apply executes it against the Google Ads API and writes any newly assigned IDs back into your config files, keeping repo and live account in sync. Commit after every apply, so each change is a labeled point in git history you can revert to.
4

Report — produces a performance report

adjar report pulls a day or month of live performance as data-only Markdown. This is the measure step: the agent reads the report alongside the config — its full context — and what it surfaces becomes the next round’s edits.
Because both the config and the reports are just text in the repo, any AI agent can read the current state and how it’s performing, then propose the next change as a TOML edit. You stay in the loop at plan/apply: the agent drafts, you review the diff, and only you approve what goes live.

​
Authentication

Each platform’s credentials live in a JSON file (google.json for Google Ads) that you point Adjar at with --credentials or the ADJAR_CREDENTIALS environment variable. Get Google Ads API access walks through producing that file, its fields, and how Adjar resolves it.

​
Command summary

CommandWhat it does
adjar importExport your live account to TOML config
adjar planPreview changes as a diff (read-only)
adjar applyApply the diff to your live account
adjar reportPull a daily or monthly performance report

​
Global flags

​
-h, --help
flag
Print usage information and exit. Available on adjar and every subcommand (e.g. adjar plan --help).
​
-V, --version
flag
Print the installed Adjar CLI version and exit. Available on the top-level adjar command only.