Introduction
Agoraform is an open-source Go CLI for Marketing as Code. You declare marketing-platform configuration in YAML, review a non-mutating plan, and apply creates and updates through provider APIs.
This documentation describes Agoraform v0.3.0. It is generated from the public repository at tag v0.3.0, not from main.
What v0.3.0 includes
Section titled “What v0.3.0 includes”| Area | v0.3.0 |
|---|---|
| Commands | validate, plan, apply, import |
| Providers | Matomo, Google Ads (googleads) |
| Matomo resources | matomo.goal, matomo.variable, matomo.trigger, matomo.tag |
| Google Ads resources | googleads.conversion_action, googleads.customer_conversion_goal |
| References | Logical $ref dependencies |
| Import | Supported Matomo resources plus supported Google Ads conversion measurement |
| Matomo publication | Declarative through provider configuration, visible in plan, executed during apply |
| State | Local agoraform.state.json |
| Mutations | Create and update |
v0.2.0 introduced the dependency-aware Matomo Tag Manager workflow. v0.1.0 was the first public release and managed matomo.goal only.
Workflow
Section titled “Workflow”validate -> plan -> apply -> planThe last plan reports no changes when desired configuration, local state, and remote state are unchanged. import adopts supported existing remote objects without mutating them.
What v0.3.0 does not include
Section titled “What v0.3.0 does not include”- There is no
destroycommand.applydoes not delete remote resources. - Meta Ads is not implemented.
- Google Ads support is limited to website (
WEBPAGE) conversion actions andWEBSITEcustomer conversion-goal biddability. Search campaigns, budgets, ad groups, keywords, targeting, ads, offline/call/app conversions, and conversion-event uploads are not implemented. - Google Ads authentication uses a developer token plus a single-user OAuth refresh token. Service-account, multi-user, and interactive OAuth flows are not implemented.
- Matomo Tag Manager is limited to one configured container (
MATOMO_CONTAINER_ID) and the variable, trigger, and tag types documented for v0.2.0. - Remote state, workspaces, locking, and encryption are not implemented.
- Rollback, scheduled publication, and approval workflows are not implemented.
Pre-1.0 releases may introduce documented breaking changes.
Next steps
Section titled “Next steps”- Install Agoraform v0.3.0
- Follow the quick start
- Read Marketing as Code