PushizoDocs

Changelog

Format: Keep a Changelog; versioning: semver. New changes are collected at the top under the [Unreleased] heading; before the version tag (vX.Y.Z), the heading is replaced with the version number and date (the release workflow…

Format: Keep a Changelog; versioning: semver. New changes are collected at the top under the [Unreleased] heading; before the version tag (vX.Y.Z), the heading is replaced with the version number and date (the release workflow publishes this section as the GitHub Release notes).

[Unreleased]

Changed (agreements)

  • The Terms of Use were rewritten (tr/en): business-use representation, customer obligations, fees and refunds, disclaimer of warranties, limitation of liability, indemnification, suspension and termination, force majeure, evidence agreement, jurisdiction.
  • Privacy Policy and KVKK notice: data processed when signing in with Google/Apple/GitHub, session records, data breach notice, the response period (30 days) and export/deletion from the dashboard.

Fixed

  • Sign-in with Google and Apple did not open a session when the dashboard and the API were on different hosts (ADR-0096 addendum).
  • Enterprise SSO (SAML/OIDC) sign-in did not open a session for the same reason; fixed without changing the addresses registered at the identity provider (ADR-0096 addendum).
  • Legal pages on the website (Terms of Use and others) returned 404 after their revalidation period: the production server runs from the repository root, so the content directory was not found.

Security

  • Dependency updates: Next.js 16.4.3 → 16.4.6, nodemailer 10.0.15 → 10.6.0 (address parsing fixes), hono 4.13.19, @hono/node-server 2.1.9, fast-uri 3.1.9 / 4.2.3.

Added (Phase 68: AI-assisted setup)

  • MCP server: create_app, get_setup_status, get_sdk_snippet (228 → 231 tools). The assistant creates the app, returns the same setup code as the dashboard guide and verifies the first subscriber (ADR-0097).
  • Local (stdio) MCP server: upload_channel_credentials. The push key (.p8, .p12, Firebase service account) is uploaded from a file path; its contents never enter the conversation or a tool result. Files are read only from below the working directory or PUSHIZO_CREDENTIALS_DIR.
  • CLI: pushizo channels status and pushizo channels <apns|fcm|hms|adm|wns|webpush> (uploads the key from a file and validates it; the output is status only).
  • Public API: POST /v1/mcp/apps, GET /v1/apps/{app}/setup/status, GET /v1/apps/{app}/setup/snippet, with matching methods in the server SDKs (Node and PHP: apps.setupStatus, apps.setupSnippet, mcp.createApp).
  • @pushizo/mcp-server and @pushizo/cli 0.4.0 are published on npm (2026-11-18; the SDKs stay at 0.3.0).

SDK 0.3.0

  • All SDKs move to version 0.3.0 and are published (including Android; the previous Android version was 0.2.1): npm, Maven Central (Android, Java, KMP), CocoaPods/SPM, PyPI, RubyGems, NuGet (Pushizo, Pushizo.Maui), Packagist, Go, pub.dev, Unity. .NET MAUI and Kotlin Multiplatform are on a registry for the first time. crates.io (Rust) and the MCP Registry (com.pushizo/mcp) are on 0.3.0 too. The bridges depend on native Android and iOS 0.3.0; React/Vue/Angular and Capacitor depend on @pushizo/web 0.3.0.
  • Contents: the SDK changes listed under "coverage completion" and "Phases 67a–67b" below (Android delivery hardening, site search, content card view, ready-made chat UI, observers, login with a profile, 518 operations in the server SDKs).
  • Upgrade note: on Flutter, React Native, Capacitor and Cordova setBadgeCount / clearBadge now return bool.

Added (coverage completion and social sign-in)

  • Sign in and sign up with Apple; the Google, Apple and GitHub buttons now also appear on the sign-up page (ADR-0096).
  • Public API: inbox teams and assignment rules, ad campaign and creative creation, email bounces and list hygiene, session analytics, recent events, user timeline, subscription listing and cleanup, webhook event types and replay, form/survey/landing page management (ADR-0095). 518 operations in total; all server SDKs cover them.
  • MCP server: 73 → 228 tools (including Phase 55–67 capabilities); write tools only produce drafts.
  • Client SDKs: content card view, custom in-app renderer, badge and login with a profile on Web; User.setProperty, feature flag and inbox observers and a ready-made chat UI on iOS and Android. Bridge SDKs (Flutter, React Native, Capacitor, Cordova, Unity, MAUI, KMP) and the React/Vue/Angular wrappers now match the native APIs; the Android Delivery API was added to the bridges.
  • The marketing site opens in the browser/device language and falls back to English (ADR-0094); the pushizo.com/bot page.

Changed

  • In the bridge SDKs the badge calls (setBadgeCount, clearBadge) now return a result on Flutter, React Native, Capacitor and Cordova (void → bool).
  • The site search crawler downloads up to 4 MB per page (previously 1 MB).

Fixed

  • The Python, Go, Java, .NET, Ruby and Rust SDKs were missing the companies, AI agents, SQL, custom agents, data pipeline and affinity operations (56 operations).
  • Android SDK: java.time usage removed; sending events and delivery receipts could crash on Android 6–7.

Added (Phases 67a–67b)

  • Android delivery hardening: the Android SDK diagnoses vendor/ROM and background restrictions and, through Pushizo.Delivery, guides the user to the right settings screen; delivery receipts are also sent in the background. New report GET /v1/apps/{app}/analytics/android-delivery and Analytics → Android in the dashboard (ADR-0092).
  • On-site AI search (Growth+): search that indexes your site's content, an optional AI answer that cites its sources, the Web SDK Pushizo.Search and a ready-made search window (/v1/apps/{app}/site-search, POST /sdk/v1/apps/{app}/search, ADR-0093).
  • Marketing site: flags in the language selector, entrance and scroll animations, a refreshed hero.

Added (Phases 65–66)

  • Company/account objects (B2B, all plans): companies, person ↔ company roles, the company.* segment condition and {{ company.* }} template variables (/v1/apps/{app}/companies, ADR-0090).
  • Warehouse segments (Growth+): segments that run a query in BigQuery, Snowflake or Databricks and pull only person IDs, refreshed on a schedule, with cost caps and encrypted connections (/v1/apps/{app}/warehouse-segments, ADR-0091).

Added (Phases 61–64)

  • Telegram and Viber channels (Starter+): a channel per bot token, subscription linking via deep links (/v1/apps/{app}/messenger-links), text/image/button messages, delivered/read, the inbox and the AI agent (ADR-0086).
  • SQL editor and SQL segments (Growth+): read-only queries over allowed views, saving the result as a segment refreshed on a schedule (/v1/apps/{app}/sql/*, ADR-0087).
  • Data pipelines (Growth+): rule and JavaScript transforms on incoming event and person data, quarantine, webhook and HTTP pull sources (/v1/apps/{app}/data-pipelines, ADR-0088).
  • Pre-send checks (all plans): brand, banned phrase, link, personalization and KVKK/İYS checks; a critical finding requires explicit acknowledgement before sending (POST /v1/apps/{app}/campaigns/{id}/preflight, preflight_ack). Custom AI agents (Growth+): scheduled agents that only produce drafts (/v1/apps/{app}/custom-agents, ADR-0089).

Added (Phase 60)

  • Conversational AI agent (Growth+): automatic replies on WhatsApp, SMS, RCS and live chat using an FAQ and webhook tools (order status, appointments), handoff rules, a monthly token cap, a run log and metrics. /v1/apps/{app}/ai-agents, Dashboard → Inbox → AI agent (ADR-0085).

Changed

  • API error messages are now English by default; clients that send Accept-Language: tr receive Turkish. Error codes (error.code) are unchanged; integrations should keep deciding by code. The dashboard uses its own language preference. Responses carry a Content-Language header.
  • MCP server (@pushizo/mcp-server): tool and parameter descriptions, server instructions and hints are in English; tool names and schemas are unchanged.

Added

  • Developer documentation in English: every page and the API reference under /en/docs/...; language switcher, hreflang, a bilingual sitemap and /en/llms.txt.
  • Setup wizard: Amazon Fire OS (ADM), Windows (WNS), Email and SMS added to the platform choices; platforms are grouped as Mobile / Web and desktop / Messaging. Expo and Kotlin Multiplatform added to the mobile frameworks; the "Native" option covers Swift, Objective-C, Kotlin and Java; every option has a description, and those awaiting release show a "Coming soon" badge. The credentials step has validated forms for Amazon (Client ID + Secret) and Windows (Package SID + Secret), plus a channel status card for email/SMS; the SDK step has Windows C# registration code, a Kotlin Multiplatform guide and extra Huawei/Amazon module lines for native Android. New document docs/sdk/windows.md.

Fixed

  • Push click-through rate always showed 0%: tapping the notification (body) only counted as an open, and a click was only recorded on action buttons. Now every tap on a push counts as a click (clicked_at, counts.clicked, the delivery.clicked webhook, the message.clicked segment). No SDK change is needed; existing data is not changed retroactively.

Added

  • Web page personalization (Growth+, Phase 59): experiences that change elements on your site (CSS selector) per person — text, image, link, hide/show; page conditions, visitor/device/segment targeting, A/B (control group), conversion goal (SDK event, page, click) and a daily report. /v1/apps/{app}/web-personalizations, a Web SDK applier (anti-flicker, disabled with webPersonalization: false), a dashboard editor with a visual picker, Node SDK webPersonalizations (ADR-0083). Web SDK main bundle budget 40→42 KB.
  • Content cards (Phase 58b): card impression/click/dismiss rates (cards) in campaign statistics and a card panel in the dashboard; ContentCards in the React Native, Flutter, Capacitor, Cordova, Unity, .NET MAUI, KMP mobile and Web SDKs; ready-made card views Android HsContentCardsView and iOS HSContentCardsView (ADR-0082 addendum).
  • Content cards: content_card in message content (classic, image + text, image only; pinning, priority, button text); SDK card feed GET /sdk/v1/apps/{app}/users/{user}/cards and impression/click/dismiss events; Android and iOS Pushizo.ContentCards (ADR-0082). Cards do not appear in the notification inbox list.
  • Sentiment tag: messages a person writes in the inbox and live chat are tagged positive/negative/neutral using a lexicon; last_sentiment on the profile, segment condition sentiment (ADR-0081).
  • Affinity tags (Growth+): an affinity score from event properties (category, brand) that decays over time; /v1/apps/{app}/affinity/*, segment condition affinity.<property>, {{ affinity.<property> }} in templates, an Affinity Tags page in the dashboard.
  • Per-person frequency (Growth+): app setting adaptiveFrequency; a personal weekly cap based on engagement is enforced at delivery.
  • Frequency priority: frequency_priority (low/normal/high) on campaigns and journeys; for a person at the cap, a high-priority message replaces a not-yet-sent low-priority delivery (ADR-0080).
  • App uninstall report: GET /v1/apps/{app}/analytics/uninstalls (daily series, iOS/Android, rate, last message before uninstall, CSV). On mobile push, a "device not registered" response closes the subscription with reason uninstall.
  • Campaign goals: a primary + up to two secondary conversion events (goals); the A/B winner is picked by the primary goal, and the goal breakdown appears in campaign and variant statistics.
  • Last IP and search by IP: app settings ipCapture (off/full/masked, default off) and ipRetentionDays; ip parameter on the user list, last_ip on the profile.
  • Server-side transactional synthetic monitoring: infra/scripts/synthetic.sh tests the end-to-end notification flow every 15 minutes and writes the result as a Prometheus metric; PushizoSyntheticFailing and PushizoSyntheticStale alerts. infra/scripts/latency-report.sh latency diagnostics report.
  • required_plan (the lowest plan that unlocks the feature) in the HS_PLAN_FEATURE_REQUIRED error details; plan remains the current plan.
  • MCP server 0.2.0: 19 new read tools (RFM, predictive models, feature flags, path analysis, report builder, decision agents, catalog and recommendations, channel score, geofences, Wallet templates); 73 tools in total. Write tools are only listed for keys with the mcp:write or admin scope; rate limit and timeout errors return with a retry hint.
  • Catalog read endpoints (GET /v1/apps/{app}/catalogs…) are also available with the analytics:read scope; writes require admin.

Fixed

  • Default ad API versions moved to supported versions: Meta v26.0, Google Ads v26, LinkedIn 202610 (the previous ones were deprecated). Google campaign dates use startDateTime/endDateTime, Meta lookalike without country, Google Customer Match membership duration 540 days, lookalike seed is the list ID (ADR-0041 addendum). Awaiting verification with a real account.
  • PHP SDK: Phase 33–48 resources added (schema coverage 361/361).
  • The Python SDK could not be imported (the generated Wallet pass method is a reserved word); the generator now guards Python reserved words. Wallet and recommendation methods have the same names as in Node across all server SDKs (wallet.getPass, listPasses, recommendations.updateConfig…).
  • The KMP mobile package is ready for Maven Central publishing: com.pushizo:pushizo-kmp 0.2.0 (Android + iOS targets), maven-kmp publish target, public repository pushizo-kmp.
  • SDK versions 0.2.0 (web, frameworks, Node, CLI, Python, Ruby, Rust, PHP, Go, Java, .NET; Android 0.2.1); @pushizo/web peer dependency ^0.2.0.
  • iOS SDK 0.2.0: Objective-C facade (@import Pushizo;, PZ-prefixed classes) and Pushizo.xcframework (iOS, simulator, Mac Catalyst; SPM binary target). Mac Catalyst build fixed. iOS targets for the KMP mobile package (iosArm64, iosSimulatorArm64, iosX64).
  • Bridge SDKs 0.2.0 (Flutter, React Native, Capacitor, Cordova, Unity, MAUI): feature flags, embedded placements and background geofence monitoring; depend on native pushizo-android 0.2.1 and Pushizo iOS 0.2.0. KMP mobile: inbox, preferences, flags, geofence monitoring. KMP server client: JSON escaping, timeout, retry. Rust in the dashboard SDK wizard.

Security

  • Location query parameters (lat, lng) and integration credential fields are masked in API logs; the Wallet pass link and device ID are masked in the nginx access log (ADR-0076).
  • MCP: . and .. are rejected in ID and path segments; ID fields are restricted by a pattern.
  • Endpoints that write integration, warehouse import and reverse-ETL credentials are disabled during a support session.

Changed

  • RFM segmentation, the product recommendation engine, predictive models, decision agents, the autonomous campaign agent, the report builder and path analysis are available on Growth and higher plans (ADR-0078). On Free and Starter these endpoints return 403 HS_PLAN_FEATURE_REQUIRED; existing data is not deleted, and scheduled computations stop.
  • Updating and revoking Wallet passes in the dashboard requires the campaigns.send permission (the composer role can issue passes but not update them). Public API scopes are unchanged.
  • Endpoint-specific rate limits on brand-kit/extract, report runs and path analysis endpoints.
  • /healthz and OpenAPI version 1.1.0; MCP serverInfo.version matches the package version.
  • The breaking change baseline (api/openapi.baseline.yaml) moved to the 1.1.0 contract.

[1.1.0] - 2026-11-04

Added

  • Campaign agent: scans for opportunities every day and suggests them, AI writes the copy on request, approval creates a draft campaign; it does not send (migration 0101, ADR-0075).
  • Decision engine: agents that learn the best option per person, a Smart decision step in journeys, a lift report against a control group, a dashboard page and API (migration 0100, ADR-0074).
  • Predictive models: churn risk and event likelihood, quality measurement, prediction.<name> audience field, a dashboard page and API (migration 0099, ADR-0073).
  • Apple and Google Wallet: coupons, loyalty cards and tickets; signed .pkpass, Google save link, pass updates, wallet_pass tag in messages, a dashboard page and API (migration 0098, ADR-0072).
  • Report builder: custom reports by choosing a source, metrics, breakdowns and filters; charts, CSV, saving, a dashboard page and API (migration 0097, ADR-0071).
  • User paths: paths followed after or before an event; an Analytics tab, Sankey chart, CSV and API (ADR-0070).
  • Best channel: per-user channel score, best_channel audience field and a Channel selection step in journeys; a dashboard page and API (migration 0096, ADR-0069).
  • Embedded placements: content in an area reserved by the app, Web render, Android and iOS data API (migration 0095, ADR-0068).
  • Salesforce sync: Contact and Lead transfer, extra field mapping, writing message activity as Tasks (migration 0094, ADR-0067).
  • Feature flags: percentage-based and scheduled gradual rollout, segment targeting, remote config values; dashboard, API, Web, Android and iOS SDK (migration 0093, ADR-0066).
  • Background geofence monitoring: optional, off by default; the Android and iOS SDKs monitor through the operating system, and no coordinates are sent to the server (ADR-0065).
  • Geofences: entry and exit events from the location sent while the app is open, a journey trigger, a dashboard page and API (migration 0092, ADR-0064).
  • Product recommendations: seven strategies, daily computation, {% recommendations %} in templates, a recommendation block in the email designer and API (migration 0091, ADR-0063).
  • RFM segmentation: users are scored daily by recency, frequency and monetary value and split into 11 ready-made segments; a transition report and segment builder fields (migration 0090, ADR-0062).
  • Product catalog: product upload via CSV and API, template tags and a product block in the email designer (migration 0089).
  • Global control group: a fixed percentage of users receive no marketing messages, and their conversions are compared (migration 0088).
  • Promo code pool: single-use code lists via CSV, a separate code per recipient with {% promo_code 'name' %} in templates. If codes run out, the delivery fails with PromoCodeUnavailable (migration 0087).

Fixed

  • Security: when a person is deleted, their Wallet pass values and barcode are deleted, the pass is revoked and copies are synced; a merge carries over passes and decision records.
  • Security: key rotation and cleanup cover all encrypted columns; keys:rotate --purge can no longer delete a key that is in use. Changing MASTER_KEY also migrates SSO and Shopify secrets.
  • Data: "clear data" also deletes import and export files; the access export includes Wallet, RFM, prediction, channel score, decision and recommendation data.
  • Correctness: decision rewards no longer get stuck on closed windows; the audit stream does not repeat the last record; time-ordered lists no longer skip or duplicate rows with the same millisecond.
  • Hardening: Wallet public endpoint limits, log masking, support session scope, report query time limit, catalog limit, retention jobs.
  • Admin dashboard: fixed an infinite update loop on the account and organization detail pages.
  • Dashboard dialogs: long code and text overflowed the dialog; dialogs now keep their width and scroll internally on short screens.
  • API keys: the create dialog no longer overflows, and the list switches to a card view on narrow screens.
  • Warehouse import: event-targeted imports could not write rows and the error record was also dropped (ADR-0056).
  • Documentation site: because closing code fences were generated incorrectly, everything after the first code block appeared as a single block on 42 pages.

Fixed

  • The account page overflowed horizontally on narrow screens; the sessions table now scrolls within its own area.

Changed

  • The name "Journey" became "Otomasyon / Automation" in the dashboard, the site and the docs. API paths, fields and webhook events (journeys, journey_id, journey.*) stay the same.

Added

  • ActiveCampaign integration: contacts and tags are imported as Pushizo users, and a tag removed there is removed here too (migration 0086).
  • Adobe Audience Manager integration: Adobe segments are received as aam_ tags via signed real-time transfer.
  • Integration guides: BlueConic, Median (Android only), Andromo and Retool.
  • Files can be attached to the dashboard assistant: images, PDF, CSV and Excel (.xlsx), up to 5 MB. Files are not stored; tables are limited to the first 200 rows.
  • The dashboard assistant generates multi-step journey drafts and edits the draft of the open journey. It does not publish or send; webhook, segment, template and A/B steps are not changed (ADR-0057).
  • Account display preferences: date format, time format and table density are saved to the account and stay the same on every device (migration 0085).
  • Global search (⌘K) finds settings screens by technical terms: APNs, SMTP, SSO, SCIM, DKIM and similar; it ignores accents and letter case.
  • Restore from journey version history: an old version opens as a new draft, and the published version does not change.
  • 15-minute runs for data warehouse export (migration 0084).
  • Delivery, open, click, bounce and complaint view per mailbox provider (Gmail, Outlook, Yahoo, other).
  • Android SDK 0.2.1: login(externalId, HsUserProfile) and Firebase Installation ID mode support.
  • AI skills: pushizo-audit, pushizo-critique, pushizo-inspect, pushizo-localize, pushizo-program.
  • Warehouse import gains ClickHouse, SQL Server, Trino, Amazon Athena, Elasticsearch, Apache Kafka and Google Pub/Sub; presets for AlloyDB, Cloud SQL, Greenplum, Materialize, MotherDuck, SingleStore, Azure Synapse, Starburst and Confluent Cloud; 5-minute runs for streaming sources (ADR-0056, migration 0083).
  • Kotlin Multiplatform SDK (sdk/kmp-mobile): shared API and Android target; the iOS target will come with the Objective-C bridge.
  • Admin dashboard visual and functional refresh (ADR-0054 §6): KPIs with trends, a 30-day chart, "Needs attention", recent activity; quick filters, quota bar and CSV in lists; summary strip, tabs and "Danger zone" on org/account detail; live preview in site content; status strip and queue chart in system health; collapsible menu and breadcrumbs.
  • Admin dashboard expansion II (ADR-0054, migration 0080–0081): per-org quota/feature overrides, list date filters, verification choice on email change, one-click write support session; site content managed from the dashboard (pricing table, announcement bar, legal text versions; anonymous GET /public/v1/site/*, read by the marketing site via ISR); MRR/ARR, payment history and overage forecast in the overview; backup freshness and Alertmanager alerts in system health (PROMETHEUS_URL, ALERTMANAGER_URL); grouped admin menu and ⌘K search.
  • Additional channels (ADR-0052, migration 0077): push fallback channel, time targeting, Amazon ADM, Windows WNS, Android live updates, iOS carousel, VoIP, App Clip, profile timeline, session report, SMS sender registration and dedicated IP. CLI, Kotlin Multiplatform, FlutterFlow, Rust and AMP web push helpers call the public API. The Postman collection is in the repository; the postman.com workspace requires an account.
  • App role, email volume spikes, Google Postmaster and SMS verification (ADR-0053, migration 0078). The code is not returned in the response. AI setup prompts are under docs/ai-prompts. The Node SDK also includes the reverse-etl endpoints.
  • Channel quotas and overage pricing (ADR-0036, plan 12): MAU, monthly email/SMS/WhatsApp/RCS quotas, AI credits and product quotas (data feeds, content tables, event streams, data warehouse destinations, custom domains) plus new feature gates in the plan matrix; fixed USD/TRY list prices (GET /billing/plans → prices); Starter/Growth overage rates and an overage forecast in the usage report (usage.overage, dashboard "Overage forecast" table). Migration 0059_plan_channel_quotas.
  • On the Free plan, deliveries are suppressed with quota_exceeded once a channel quota is reached; on plans with overage, sending continues (Redis channel counters hs:usage:{org}:{YYYYMM}:ch:{kanal}).
  • Brand kit (ADR-0051): colors, logo and voice are read from the site address; brand.* in templates, brand voice in AI suggestions. No new table.

Fixed

  • Marketing site: once pages moved to ISR with dashboard-managed content, runtime regeneration could not find WEB_DASHBOARD_URL/WEB_DOCS_URL and the company imprint, and sign-in/sign-up links fell back to localhost:3100. The web.Dockerfile runner layer carries build arguments as environment variables.

Changed

  • Public API import type legacy_players (POST /v1/apps/{appId}/imports). The old type name was removed; this is a breaking contract change and ships with a version tag.
  • MCP write endpoints added (/v1 mcp/template-drafts, journey-drafts, in-app-drafts, test-sends). They do not send; they are additive to the current version.
  • WhatsApp and RCS channel setup is now tied to their own plan features instead of the SMS gate; replying from the inbox is limited by the inbox gate, data warehouse by warehouse_export, custom domain by custom_domain, event streams by event_streams, and by plan quota.
  • List price Starter $99, Growth $399 (ADR-0046, migration 0071). Net margin ≥ 60% at full quota after Creem and the 1% transfer fee.
  • AppsFlyer, Adjust and RevenueCat inbound webhooks (ADR-0047, migration 0072).
  • GA4, PostHog and RudderStack outbound event destinations (ADR-0048, migration 0073).
  • Databricks and Redshift export; import from Snowflake, BigQuery, Postgres, MySQL, S3 and Google Sheets (ADR-0049, migration 0074, 0075).
  • HubSpot contact sync and timeline note (ADR-0050, migration 0076).
  • Marketing site and documentation site typeface Geist + Geist Mono.
  • Java server SDK package and Maven coordinate com.pushizo (com.pushizo:pushizo-java); not breaking, since the package has not been published yet.

Fixed

  • deploy.sh writes the deployed IMAGE_TAG to the .env.prod / .env.staging file; the next compose run no longer falls back to the old image.
  • The documentation site typeface is embedded from the geist package. The build does not connect to Google Fonts.
  • On the billing page, the useLocale hook was called after conditional returns (React rules of hooks).

[1.0.0] - 2026-10-16

First general production release (pushizo.com). All development after 0.6.0 is collected in this release; details are in the subsections below.

Highlights

  • Pushizo brand name: the product moved from HeroSignal to Pushizo; packages @pushizo/*, images ghcr.io/exec0de/pushizo-*, SDK package names and the default API root https://api.pushizo.com, error documentation https://docs.pushizo.com/errors.
  • v2 phases (15–21): enterprise identity (SAML/OIDC SSO, SCIM, JWT authentication), scale architecture (ClickHouse, Kafka, Go dispatcher, Helm), iOS Live Activities, Huawei HMS, location; drag-and-drop email editor, HTML in-app, template gallery, Data Feeds, Dynamic Content, AI content assistant; WhatsApp, RCS, two-way SMS, deliverability; Event Streams, data warehouse export, ready-made integrations and the MCP server; data residency (EU/TR), white-label and resellers.
  • Platform admin dashboard (/admin): organizations, accounts, billing, feature flags, abuse, support, incidents, app transfer approvals, system health and audit log; actions requiring a justification, MFA-protected admin access (ADMIN_MFA_REQUIRED).
  • Legacy-provider-style setup flow: "Getting started" and SDK setup pages (platform selection, step-by-step setup, the public API address in code samples).
  • Marketing site and SEO: apps/web (pushizo.com) — multilingual static pages, sitemap, robots, llms.txt, OG images, IndexNow; documentation site docs.pushizo.com.
  • Go-live: single-server Docker Compose production stack (nginx + Let's Encrypt, www → apex domain redirect), optional staging, email-first Alertmanager, off-server backup with separate credentials, rejection of weak/default secrets in production (SESSION_SECRET ≥ 32, development S3 password, local SMTP).

v2 Phase 15, 16, 17a and 17b (2026-10-15, ADR-0023…0026)

Added

  • Enterprise identity (Phase 15): SAML 2.0 and OIDC SSO (domain DNS verification, JIT, IdP group → role, test sign-in, "SSO only" and owner recovery codes), SCIM 2.0 (/scim/v2/Users, /Groups), cross-org app transfer (approval by two owners + platform admin), per-event retention period, SIEM audit stream (audit.created webhook and daily NDJSON).
  • JWT identity verification: per-app ES256 public keys (/v1/apps/:appId/identity-keys), identity_verification_mode (hmac | jwt | both); login(externalId, { jwt }) and updateUserJwt in the Web/Android/iOS/Flutter/RN/Capacitor/Cordova/MAUI/Unity SDKs; a token generation helper in the Node/PHP/Python/Go/Java/.NET/Ruby server SDKs.
  • iOS Live Activities (Phase 17a): type registration and schema validation, POST /v1/apps/:appId/live-activities/:activityType/start|update|end, SDK push-to-start/update token endpoints (proof of ownership required), APNs liveactivity payload, journey live_activity node (Liquid + schema translation), dashboard Live Activities page, iOS SDK Pushizo.LiveActivities.register and a generic type in the bridges.
  • Huawei HMS, Flutter web, Mac Catalyst, location (Phase 17b, ADR-0025): hms_push channel and Push Kit provider (OAuth, data messages, validation), Android pushizo-hms module, Flutter web (Web SDK bridge), iOS Mac Catalyst; Location.setShared/isShared/requestPermission in all SDKs (foreground only, KVKK (Turkish data protection law) consent record, deletion when turned off), a "within radius" segment condition, dashboard Huawei channel card and user location.
  • Scale architecture (Phase 16, ADR-0026): ClickHouse analytics store (outbox transfer, AnalyticsStore, dual comparison, backfill, retention/deletion mirroring), optional Kafka event ingest path (packages/ingest), Go dispatcher (services/dispatcher, shared test vectors with TS), Helm 0.2.0 (PDB, NetworkPolicy, ExternalSecrets, KEDA, blue/green, dispatcher), k6-operator load test manifests; local ClickHouse and Kafka setup (infra:install).
  • Migrations 0029_enterprise_identity, 0030_live_activities, 0031_hms_push, 0032_subscription_location, 0033_analytics_outbox; dashboard Organization → Security page, admin app transfer page, SSO at sign-in.

Phase 0–14 audit and security hardening (2026-10-15, ADR-0022)

Security

  • Path canonicalization and auth type by route pattern (API key only on /v1, session only on /internal//admin); origin + content type checks on /internal and /admin mutations; CSP on HTML responses.
  • Limited proxy trust via TRUST_PROXY (the IP allowlist/rate limit cannot be bypassed by XFF spoofing); IPv6 CIDR allowlist.
  • API key scope tied to role permissions; org-wide action and read limits for app-scoped members.
  • Atomic and fail-closed login lockout, per-account MFA limit, sessions closed when MFA changes, OAuth pre-account-takeover protection and confirmed account linking, safe next redirect.
  • SDK proof of ownership extended to email/SMS re-registration, events, in-app/inbox and preference endpoints (ADR-0016 K7–K9).
  • SSRF: allowlists for the Web Push endpoint and FCM token_uri, private address rejection and IP pinning for tenant SMTP servers; Liquid sandbox; linear email HTML processing (ReDoS); rejection of dangerous URL schemes.
  • Resend signature required (production), SNS TopicArn/freshness; log masking of hook tokens; least-privilege MinIO service user; API Explorer SRI.

Added

  • Failed queue jobs (DLQ) list and retry (admin), channel status endpoint, cursor pagination for event definitions, quota preview on campaign approval, segment/template search.
  • Migrations 0026 (preference FK), 0027 (delivery claim lease), 0028 (partition RLS).
  • npm run setup and docs/YENI_BILGISAYAR.md (one-command setup on a new computer, local passwords); .gitattributes (scripts LF).

Fixed

  • Concurrent dispatch could send the same delivery twice; the delivered status was overwritten by sent.
  • Campaign PATCH reset fields that were not sent to their defaults; approval was kept after editing.
  • Preferences were lost when merging users; deletion left merged records behind.
  • CI: ESLint out of memory (exit 134); Node 20-based action versions updated.

Phase 11–14 and audit round (2026-10-08 … 2026-10-14)

Added

  • Journeys (Phase 11, ADR-0018): engine with 13 node types (wait, condition, split, time window, send A/B, webhook, tag), entry/exit rules, goals, schedule, versioning, crash recovery; React Flow builder, run timeline, journey.* webhooks; preference category on the send node.
  • A/B and preferences (Phase 12, ADR-0019): campaign/journey/in-app A/B (deterministic assignment, holdout, z-test, automatic/manual winner; in-app winner 0024), categories and user preferences (API, all client SDKs including RN/Capacitor/Cordova/MAUI/Unity, hosted preference center), tags, template analytics, multiple frequency windows, outcome types (unique/unattributed), usage_duration segment, retention cohort, SMS HELP/STOP replies.
  • Billing and platform (Phase 13, ADR-0020): plan matrix, trial, quota and feature gates, Stripe/iyzico/mock, usage report, abuse reviews, suspension, platform admin and audit log, support session, feature flags, status page (+ email subscription 0025), OAuth sign-in and account linking, Composer role.
  • Operations (Phase 14): Docker/compose/Helm, CI/CD (release, SDK publishing, E2E, Stripe test mode, gitleaks, Dependabot, PR image builds), Prometheus/Grafana/Alertmanager, Sentry, synthetic monitoring, chaos drill, wal-g + daily base backup, runbooks, docs-site (+ deployment), legacy provider migration tool, Postman collection, GO_LIVE_CHECKLIST.md.

Security

  • The application role in production Postgres is NOSUPERUSER/NOBYPASSRLS (RLS is actually enforced); the API/worker check the role at startup.
  • RLS on billing tables (0022); OAuth sign-in CSRF protection; MFA for support sessions; mock provider in production only with explicit permission; OAuth/MFA parameters added to log masking.

Fixed

  • The Netgsm inbox re-opened the subscription on HELP.
  • A category opt-out also suppressed channels not defined in the category.
  • The trial period downgraded a higher plan assigned by an admin to Starter.
  • The queue depth metric did not count prioritized jobs (alerts/KEDA were blind).
  • The smoke test called /readyz, which is closed to the outside; signed download links with the /storage prefix could not pass SigV4 verification.
  • In A/B campaigns, the notification inbox item did not use the variant content; variant content was not validated in the readiness check.

[0.6.0] — 2026-10-07 (Phase 10: email, SMS, in-app, notification inbox)

Added

  • Email: SMTP, Amazon SES (SigV4), Resend providers; MJML/HTML body (Liquid output HTML-escaped), preheader, plain-text version; HMAC-signed open pixel and click redirect (no open redirect), RFC 8058 one-click List-Unsubscribe (/t/o, /t/c, /t/u), tr/en footer; DKIM/SPF/DMARC guide.
  • SMS: Twilio and Netgsm (encoding: TR, İYS (Turkey's commercial messaging consent registry) filter); short links (/t/s), GSM-7/UCS-2/Turkish shift segment counting (smsSegments), STOP/START (Twilio inbound messages, Netgsm inbox polling, generic webhook).
  • Inbound feedback: /hooks/email/{ses|resend|smtp|mock}/{token}, /hooks/sms/{twilio|mock}/{token} (SNS/Svix/Twilio signatures); bounce/complaint/delivery/open/click are applied to deliveries, counters and webhooks; Netgsm report polling.
  • Suppression list: digest + masked value; checked at audience time and send time; internal + public API, dashboard screen.
  • In-app messages: block-based modal/banner/full screen, triggers (session, event, screen, trigger), segment audience, frequency, statistics; Web/Android/iOS/Flutter rendering and the InAppMessages API; dashboard editor and live preview.
  • Notification inbox: add_to_inbox messages; SDK Inbox (list, read, all, archive) and endpoints; inbox on the user detail page.
  • SDK: User.addEmail/removeEmail/addSms/removeSms (linking to an anonymous user with user.subscription_id); Node hs.suppressions, PHP Suppressions; sample apps updated.
  • Dashboard: Email/SMS channel settings and webhook address card, Email and SMS tabs in the campaign/template editor (MJML editor + sandboxed preview, segment counter).
  • Migration 0015_email_sms_inapp_inbox (up/down); ADR-0015; docs/messaging.md; metrics messaging_feedback_total, suppression_entries_total; E2E messaging.spec.ts, in-app-inbox.spec.ts.

Fixed (Phase 10 gap round)

  • A push message/campaign with no channel in the target no longer goes to email/SMS subscribers with the push text: channels are inferred from the content (push → push channels, email_* → email, SMS only explicitly); missing content for a targeted channel returns 422.
  • Repeated one-click unsubscribe and complaint events no longer increment counters a second time.
  • In SES/SNS feedback, the topic region must match the channel's SES region.
  • In-app impression records are subject to the event retention period (global + organization); time-limited suppression entries are deleted when they expire.
  • A segment used in an in-app message audience cannot be deleted (409).
  • The root npm run dev with 17 persistent tasks hit turbo's default concurrency limit (10); --concurrency=32 (Playwright webServer can restart the server).

Changed

  • Email/SMS subscription tokens are normalized to canonical form on registration and CSV import (lowercase email, E.164); invalid values return 400.
  • A non-mock provider on the email/SMS channel no longer returns 501; a provider incompatible with the channel returns 400.
  • The ci:local OpenAPI check distinguishes union (oneOf/anyOf) variants: a new variant is not considered breaking, but adding a required field to an existing variant is.

[0.5.0] — 2026-10-07 (Phase 9: webhooks)

Added

  • Outbound webhooks: endpoint management (internal + public admin), 20 event types, HMAC-SHA256 signature (Pushizo-Signature), 24-hour secret rotation, custom headers (encrypted), batch mode (delivery.* in batches of 100), test sends, delivery history, single/bulk replay.
  • Delivery engine: transactional outbox + worker scan (ADR-0014), exponential retry (1 min → 24 h, dead after 7 requests), SSRF protection (https, private IP/local name rejection, IP pinning after DNS, no redirects), endpoint health (7 days failing + email, 14 days disabled), 30-day retention, webhook_deliveries_total metric.
  • SDK: Node verifyWebhookSignature / constructWebhookEvents / hs.webhooks; PHP Pushizo\Webhook.
  • Dashboard: Webhooks list and detail screens, signature verification examples; webhook deliveries in the trace.
  • Migration 0014_webhooks (up/down); docs/webhooks.md; E2E webhooks.spec.ts.

Fixed (Phase 9 gap round)

  • User deletion and app data cleanup also delete personal data in the webhook delivery history (KVKK/GDPR).
  • Webhook scan: per-endpoint quota and concurrency limit, circuit breaker, lease-protected sending (prevents double sends with multiple workers).
  • An event name filter is required for event.received subscriptions; a failed test send does not affect endpoint health; user.updated on alias/external_id change; an alias insert conflict does not break the transaction; payloads over 64 KB are truncated.
  • Problematic webhooks in the notification center; latency metrics and tests/load/webhooks-bench.mjs (p95 4.5 s).

[0.4.0] — 2026-10-07 (Phase 0–8 deep audit and gap closing)

Added

  • Data & Privacy: organization deletion (permanent cleanup after a 30-day wait), org retention period and session duration policies, org data export request, clearing app data; "remember me" sign-in.
  • API: Idempotency-Key header, filter[...] and sort parameters, export/import cursor pagination, notification history (GET /v1/notifications/{id}/history), ?kind= filter, X-HTTP-Method-Override, SDK alias and dismissed endpoints, SDK error reports, channel credential file upload, static segments (segments/{id}/refresh), notification center, user's recent messages, campaign live stream (SSE), custom date range and recent campaigns in the overview, web push prompt/SW settings in the SDK config, public organization/member/audit endpoints.
  • Delivery: FCM data-only and shared hs {dlv, msg, url, buttons} payload field, 4 KB payload limit, per-device APNs environment, iOS badge increment, per-app fair ordering and provider rate limit, deferral not counted as an attempt for rate_limited, email to the owner on credential rejection, mock:open, test device names.
  • SDKs: Android 12+ compatible notification open, update on token change, alias API (Web/Android/iOS/Flutter), Flutter foreground suppression, iOS NSE badge/category merging, web slidedown scroll trigger and categories, SW retry, SDK error reporting, Node SDK notifications.history.
  • Dashboard: ⌘K command palette, notification bell, global app picker; error states with request_id; DataTable/CodeBlock/DateRangePicker/JsonViewer/Stepper; locale number formatting and account time zone; API key expiry; send confirmation modal; personalization variable picker; web permission prompt designer; user detail editing; SDK errors log tab.
  • Tooling: npm run ci:local (OpenAPI breaking changes, npm audit, secret scanning, i18n, migration pairs), npm run openapi:baseline, k6 event ingest script.
  • Migrations 0010–0013 (up/down); ADR-0011, ADR-0012, ADR-0013.

Changed

  • Cross-tenant access always returns 404 HS_NOT_FOUND (ADR-0011); an invalid cursor returns 400 HS_VALIDATION_ERROR.
  • Analytics open/click counts are computed from timestamps on the delivery row (independent of the event retention period).
  • Storage keys are prefixed with org/{org_id}/app/{app_id}/…; request log ID prefix rlg_.

Security

  • fastify 5.11.3 → 5.12.5 (high severity, 7 GHSAs), js-yaml 5.3.0 → 5.4.3 (overrides); TOTP reuse prevention, API key revocation cache race, increasing login delay, JSON depth and body size limits, active DEK cache detecting rotation.

[0.3.0] — 2026-10-07 (Phase 8: events, analytics, conversion, export/import)

Added

  • Event processing: ingest with batched reference resolution, events queue (definition registry, user × event × day counters, last activity), conversion attribution (direct_click / influenced, campaign and message converted counters), live event stream (SSE).
  • Analytics API and screens: delivery (day/channel/campaign), subscription growth, event volume, conversion/revenue, funnel, provider health (error codes, latency p50/p95), engagement heatmap; date range, comparison with the previous period, CSV export; ECharts charts.
  • Export/Import: CSV export jobs (users/subscriptions/events/deliveries → S3-compatible storage, signed download link), Pushizo CSV and legacy provider player CSV import (error report), packages/storage SigV4 client.
  • Retention: event/delivery/delivery event/audit retention periods are enforced by dropping partitions; daily recomputation of event_definitions.count_30d.
  • Dashboard: Events, Analytics and Export/Import screens; segment event conditions sped up with user_event_counts. Migration 0009_events_analytics (up/down).

Performance

  • 1M event ingest at 11679 events/s in a single API process (target ≥ 5k); 100,000-user export in 2.0 s (18.1 MB CSV, target < 60 s); worker event processing ran concurrently during the 1M event ingest.

[0.2.0] — 2026-10-07 (Phase 7: segments, templates, campaigns)

Added

  • Segments: nested all/any/none condition AST → parametric SQL compiler (tag/property/language/device/semver/event count/message engagement/segment membership), live preview and cached estimate endpoints, dashboard segment builder.
  • Templates: versioned message templates (template_versions), rollback, Liquid render preview; template_id in POST /v1/notifications.
  • Campaigns: state machine (draft/scheduled/running/paused/completed/canceled/failed), scheduled and recurring (cron + time zone) sends, user time zone and intelligent delivery, rate limit, frequency/quiet hours exceptions, approval flow (settings.campaignApprovalRequired), duplication, statistics/rollup endpoints; dashboard 5-step campaign builder and detail screen.
  • Worker: scheduler queue (scheduled scan, recurring trigger, hourly delivery_event_rollups, campaign close-out); deferral of deliveries for paused campaigns.
  • Targeting: included_segments, excluded_segments, filters, all and delayed_option now work in the Public API (Phase 4 501 responses removed).
  • Migration 0008_campaigns (up/down), RLS policies; E2E campaign.spec.ts; the accessibility scan covers Phase 7 screens.
  • Completion round: Delivery policies screen (quiet hours, frequency cap, default TTL); campaigns that use a segment; type/channel filter and cancel in the campaign list; per-subscriber delivery table and "resend to failed" on the campaign detail page; cancel confirmation by typing the name; segment builder filter on the Users page and POST /v1/apps/{app_id}/users/search; audience snapshot (segment_snapshot); large table estimates with TABLESAMPLE; builder between/subscription.status; channel tabs in the content editor; Chrome preview frame.

[0.1.0] — 2026-10-06 (MVP: Phase 0–6)

Added

  • Infrastructure (Phase 0): npm workspaces + Turborepo monorepo; NestJS 11 + Fastify API; BullMQ worker; Next.js 16 dashboard; Drizzle + SQL migrations (up/down); pino + Prometheus metrics; OpenAPI generation and type-safe client.
  • Identity and tenancy (Phase 1): sign-up/sign-in/email verification/password reset, session management, TOTP MFA + recovery codes, login lockout; organizations/memberships/invitations, roles and app scope, API keys (scopes, revocation ≤ 60 s cache), audit log, Redis rate limiting, Postgres RLS as a second line of defense, org MFA enforcement and IP allowlist.
  • End-user identity (Phase 2): end user / alias / subscription model, anonymous → identified merge, tag/property merge-patch, identity verification (HMAC), SDK API (/sdk/v1), public Users/Subscriptions API, KVKK/GDPR deletion and data export.
  • Providers (Phase 3): envelope encryption (DEK + MASTER_KEY, rotation commands), APNs HTTP/2, FCM HTTP v1, Web Push (VAPID), mock provider, channel validation endpoints.
  • Delivery engine (Phase 4): POST /v1/notifications (idempotency), audience/dispatch workers, LiquidJS personalization, suppression (frequency cap, quiet hours), scheduled retries, counters, trace screen, test devices, queue–database reconciliation job.
  • SDKs (Phase 5): Web (@pushizo/web), Android, iOS (+ Notification Service Extension), Flutter, Node, PHP; sample apps and docs/sdk/* guides.
  • Dashboard core (Phase 6): onboarding stepper (simulation mode, live device detection, test push), Overview KPIs, SDK Setup, Test Devices, API Explorer, Logs; tr/en, dark theme, axe accessibility scan.

Security

  • Security headers (CSP, HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, X-Frame-Options) on the API and dashboard.
  • Secrets (p8, service account, VAPID private key, SDK secret) are stored only encrypted; they cannot be read back from the API.

On this page