Kameleoon vs June
Side-by-side trajectory, velocity, and editorial themes.
Kameleoon refines its prompt-driven personalization editor with widget, targeting, and PBX upgrades.
Kameleoon is iterating on the new Personalization editor and the prompt-based workflow that sits inside it. Recent changes: a simpler two-step widget event creation flow that ties directly to Kameleoon goals, the ability to reorder personalization targeting rules from the new editor, and PBX prompt-area improvements (resizable prompt area, image paste as input). Survey widgets get a configurable response-recording trigger.
The product is settling into the new editor as the default surface and accumulating the small ergonomics wins teams expect from a mature personalization tool — fewer clicks, fewer manual IDs, more control over evaluation order. The PBX prompt updates suggest AI-assisted variant creation is becoming a more prominent workflow, with multimodal input now supported.
Expect the editor's PBX surface to keep gaining capability — likely brand-context awareness, reusable prompts, and broader image-driven generation. Targeting and goal flows will continue to consolidate so users don't need to reach for IDs or admin pages.
June's last visible push was a tight May 2025 B2B sprint — Custom Objects, SQL traits, PostHog integration.
June is product analytics for B2B SaaS, and the only visible release activity in the input is a concentrated four-week sprint in May 2025: SQL computed traits, PostHog as a data source, increased computed-trait limits, and the GA of Custom Objects after a two-month rollout. Each release is paired with small fixes (Slack alerts, HubSpot reverse sync) suggesting a stable maintenance cadence around the headline launches.
The May 2025 batch is internally consistent: every release widens what June can model (Custom Objects), how flexibly customers can compute on it (SQL traits), or how easily it slots into existing data plumbing (PostHog source). All three target the B2B-SaaS persona that wants more than user/account analytics. After this burst the changelog goes quiet in the input — it's not clear from the entries alone whether the product moved to a slower cadence, switched publishing channels, or paused.
The entries don't support a confident prediction about what comes next. If publishing resumes from the same direction, the obvious extensions are deeper integrations with reverse-ETL or warehouse-native sources and richer pre-built health-score templates on top of SQL computed traits.
See more alternatives to Kameleoon →
See more alternatives to June →