@debugbundle/cli 1.11.0 → 1.13.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -0
- package/dist/main.cjs +721 -120
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -65,6 +65,19 @@ The CLI reads local project configuration from `.debugbundle/` and can use membe
|
|
|
65
65
|
|
|
66
66
|
## AnalyticsBundle
|
|
67
67
|
|
|
68
|
+
Public project flows support customer-defined acquisition and activation steps across sites,
|
|
69
|
+
auth pages and apps. Read definitions and aggregate reports with:
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
debugbundle analytics flows list --project <project-id> --json
|
|
73
|
+
debugbundle analytics flows report --project <project-id> --key onboarding --window 30d --json
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
Owners/admins can use `analytics flows save --project <project-id> --definition-json '<JSON>'`
|
|
77
|
+
and `analytics flows archive --project <project-id> --key onboarding`. See the
|
|
78
|
+
[flow contract](https://debugbundle.com/docs/api/analytics/#public-acquisition-and-activation-flows)
|
|
79
|
+
for definitions, capture, full UTC day report windows, and partial coverage.
|
|
80
|
+
|
|
68
81
|
Analytics commands require connected member authentication and a project with AnalyticsBundle enabled. They query aggregate rollups or request an asynchronous analysis artifact; they do not read raw analytics events.
|
|
69
82
|
|
|
70
83
|
```sh
|