Skip to main content
adjar import is the starting point for every Adjar project. It connects to your live Google Ads account via the API and writes a complete snapshot of your campaigns, ad groups, keywords, creatives, and conversion actions to a TOML config. Once imported, your account lives in plain text — human-readable, diffable, and ready to be managed by you or an AI agent.

​
Syntax

adjar import --account <id> [-o <output-file>]
With no -o, the config is written to stdout.

​
Flags

​
--account <id>
string
required
The Google Ads account ID to import — shown top-right in the Google Ads UI. Pass the plain numeric ID with no hyphens (e.g., 4821937650, not 482-193-7650).
​
-o, --out <file>
string
Path to the TOML file to write (e.g., config/google.toml). The parent directory is created automatically if it does not exist. Omit to print the config to stdout instead.
​
--platform <platform>
string
default:"google"
The ad platform to import from. Google Ads is the only platform in v1.
​
--credentials <path>
string
Path to the platform credentials JSON file (e.g. google.json). Alternatively set ADJAR_CREDENTIALS. See Authentication.

​
Examples

# Export to a file
adjar import --account 4821937650 -o config/google.toml

# Preview the config without writing it
adjar import --account 4821937650

​
Output

adjar import writes a single self-contained TOML file containing the account’s metadata and every campaign, ad group, keyword, creative, and conversion action. For a large account you can split this into multiple files with a top-level imports directive after the fact — see the config reference.

​
After import: commit to version control

Once the import completes, commit the entire config directory to your repository. This snapshot becomes the baseline that adjar plan diffs against: 
git add config/
git commit -m "chore: initial import of Google Ads account 4821937650"
From this point forward, all changes flow through the plan → apply cycle rather than through import.

​
Re-running import

Re-run adjar import to refresh your local config from the live account state at any time — for example, after making changes directly in the Google Ads UI, or to onboard a new team member against the latest live state: 
adjar import --account 4821937650 -o config/google.toml
Re-running adjar import overwrites the output file with the live account state. Commit or stash any uncommitted local changes first — they will be lost.

​
Next steps

After importing, edit your TOML files and use adjar plan to preview what will change before pushing anything back to Google Ads.