@arsel.sa/web-sdk 1.1.0 → 1.2.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/CHANGELOG.md CHANGED
@@ -5,7 +5,28 @@ versioning follows [Semantic Versioning](https://semver.org/).
5
5
 
6
6
  Breaking changes to the public surface wait for a major release, and are listed here explicitly.
7
7
 
8
- ## [Unreleased]
8
+ ## [1.2.0] — 2026-09-02
9
+
10
+ ### Changed
11
+
12
+ - **`screen()` now emits `arsel.screen_view`, not `arsel.screen`.** The Android and
13
+ iOS SDKs have always used `screen_view`, and the split meant a segment or in-app
14
+ rule keyed on one name silently never matched the other platform. Renamed here
15
+ rather than on mobile because two of the three SDKs already agreed, and because
16
+ `screen()` only shipped in 1.1.0 — the exposure is ten days wide. If you built a
17
+ segment or automation on `arsel.screen`, repoint it at `arsel.screen_view`.
18
+
19
+ ### Added
20
+
21
+ - **`arsel.app_installed`.** Emitted once per browser profile, on the first `init()` the SDK ever
22
+ runs there, ahead of the first `arsel.session_start`. Carries `sdk_version` and `platform`. A
23
+ browser has no install step, so this means "the first time we saw this device" — clearing site
24
+ data or opening a private window resets the store and re-fires it, and web install counts run
25
+ high by exactly that much.
26
+
27
+ **Browsers that already used an older version get no install event.** They are seeded silently on
28
+ their first load after the upgrade: emitting would have reported the whole existing audience as
29
+ installs on the day you shipped. Install-based segments start empty and fill forward.
9
30
 
10
31
  ## [1.1.0] — 2026-08-23
11
32