Sources & Events¶
Sources¶
A source is anything you connect under Settings → Integrations so Adwize can read data for monitoring, modeling, or recommendations.
Sources fall into a few kinds:
| Kind | What it does | Examples |
|---|---|---|
| Monitoring | Sends collection / event health into Adwize | Google Tag Manager, Custom API |
| Commerce & messaging | Copies store or ESP data in (read-only) | Shopify, Klaviyo |
| Warehouses | Copies enabled tables or prefixes in | Warehouses (BigQuery, Cloud Storage, Snowflake, Postgres, MySQL, DuckDB, Azure Synapse, Microsoft Fabric) |
| Google tools | Connects Ads, Analytics, or Sheets for the workflows that use them | Google Ads, Google Analytics, Google Sheets |
In the app: open Settings → Integrations, add a connection, then set the account Schedule at the top of that page (Manual, Daily, or Weekly) for when connected sources refresh. Each connection still has its own first-load window.
Pages titled Coming Soon under Integrations are not live in the app yet.
Self-hosted monitoring ingest: adwize-oss.
Events¶
An event is a single action from a monitoring source (GTM or the Custom API).
| Field | Type | Description |
|---|---|---|
source |
string | Origin (for example gtm, api) |
event_type |
string | Action type (for example page_view, purchase, error) |
data |
object | Payload fields you want to monitor |
timestamp |
datetime | When Adwize received the event |
Example¶
{
"source": "gtm",
"event_type": "purchase",
"data": {
"transaction_id": "TXN-12345",
"value": 99.99,
"currency": "USD"
}
}
In the app: work collection health and alerts from Monitoring → Overview and Today. There is no separate Events page — /events redirects to Overview. Programmatic access stays on the Events API.
Domain validation¶
For API POST ingest, Adwize can enforce allowed domains from Settings. Unauthorized origins receive 403 Forbidden.
The GTM monitoring tag uses a pixel path meant for browser traffic from the site where GTM is installed — see GTM integration if pixel and API behavior differ.