How Adwize works¶
This page maps the product loop to what you do in the app. It matches the language on getadwize.com.
The loop¶
1. Observe¶
Connect the tools and data you already use to run the business.
In the app: Settings → Integrations (for example Google Tag Manager or Custom API). Open-source teams can also ingest with adwize-oss.
2. Resolve¶
Connect identity and journey signals across sources so the same customer and path are coherent.
In the app: this underpins Insights (Beta). You work with connected business context rather than configuring identity graphs by hand in Monitoring.
3. Model¶
Train scores and forecasts for the business problem — not another disconnected dashboard.
In the app: Insights surfaces such as Simulate let you work with modeled scenarios when enabled for your workspace.
4. Reason¶
Give specialist agents your context, playbooks, and constraints.
In the app: the AI Assistant on every page, plus Insights recommendations and related Beta surfaces.
5. Act¶
Review recommendations and prepare governed actions.
In the app: Insights Audiences, recommendations you review before they go further, and Monitoring alerts you acknowledge or resolve.
App map¶
| Loop stage | Typical app area |
|---|---|
| Observe | Settings → Integrations; Monitoring Overview |
| Resolve | Insights (connected context) |
| Model | Insights → Simulate |
| Reason | AI Assistant; Insights recommendations |
| Act | Insights → Audiences; Monitoring alerts on Today / Overview |
Also in the product story: Analytics, Monitoring, Intelligence, and Reasoning. Docs below focus on Monitoring (generally available), Insights (Beta), Audits, and the open-source foundation.