> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getjurni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Jurni Changelog

> Customer-facing product updates from Jurni, focused on meaningful improvements to building, commerce, experimentation, analytics, and collaboration.

New ways to build, review, publish, and optimize with Jurni.

This changelog highlights meaningful customer-facing product changes. Each update links to the relevant Help Center guide when more detail is available.

<Update label="September 7, 2026" tags={["Experiments"]}>
  ## A redesigned workspace for creating and managing tests

  Experiments now have a clearer setup and reporting workflow from the first variant through ongoing analysis.

  ### What changed

  * Create a test through a guided setup for its Smart Link, variants, traffic weights, and primary metric.
  * Review live, ended, and archived tests in a more useful table with performance columns and filters.
  * See metrics over time and connected Meta ad context from the experiment workspace.

  ### Why it matters

  It is easier to launch a clean test, understand how traffic is configured, and move from topline results into the details that explain performance.

  **Learn more:** [Create an experiment](/experiments/create-experiment) · [Read experiment results](/experiments/reading-results)
</Update>

<Update label="September 7, 2026" tags={["AI","Builder"]}>
  ## More accurate AI builds from Figma and visual references

  Jurni's AI building workflow is better at translating real design references into editable, functional experiences.

  ### What changed

  * Improved how Jurni reads page structure, components, responsive layouts, and assets from Figma.
  * Improved carousel and image-gallery behavior in AI-generated pages.
  * Strengthened handling for reference fonts, media, sections, and interactive elements.

  ### Why it matters

  Teams can start with a richer design or reference and spend less time correcting structure and behavior after the first build.

  **Learn more:** [Build with AI](/build/ai-campaign-workflow) · [Build from Figma](/building-funnels/figma-file)
</Update>

<Update label="September 2, 2026" tags={["Commerce"]}>
  ## Gift quantities can now scale with qualifying products

  Gift-with-purchase campaigns can award gifts incrementally as shoppers add more qualifying products.

  ### What changed

  * Set the maximum number of gifts a shopper can receive.
  * Match gift quantity to the quantity of qualifying trigger products.
  * Keep gift quantities aligned as the shopper changes the cart.

  ### Why it matters

  You can support offers such as “buy two, receive two gifts” without relying on a fixed one-gift setup.

  **Learn more:** [Gift with purchase](/building-funnels/gift-with-purchase)
</Update>

<Update label="September 2, 2026" tags={["Analytics","Meta"]}>
  ## See cost per acquisition in Meta Ads insights

  Connected Meta Ads reporting now includes **cost per acquisition (CPA)** alongside campaign performance.

  ### Why it matters

  Teams can compare acquisition efficiency with Jurni performance without calculating CPA separately.

  **Learn more:** [Meta Ads](/integrations/meta-ads) · [Meta ad insights](/analytics-reporting/meta-ad-insights)
</Update>

<Update label="August 31, 2026" tags={["Experiments"]}>
  ## Route experiment traffic using URL and UTM rules

  Experiments can now send matching campaign traffic to a specific variant based on routing rules.

  ### What changed

  * Define rules using supported URL and campaign parameters.
  * Assign matching traffic to the intended variant.
  * Continue using the normal traffic split for visitors who do not match a rule.

  ### Why it matters

  You can keep one experiment entry point while preserving campaign-specific experiences for different audiences or creative angles.

  **Learn more:** [Experiment routing rules](/experiments/routing-rules) · [URL parameters](/reference/url-parameters)
</Update>

<Update label="August 31, 2026" tags={["Analytics","Collaboration"]}>
  ## Schedule Jurni performance reports in Slack

  Jurni can now deliver recurring performance reports to a connected Slack workspace.

  ### What changed

  * Configure daily or weekly reports.
  * Choose the Slack channel, schedule, and timezone.
  * Send a test notification before relying on the schedule.

  ### Why it matters

  Teams can keep campaign and test performance visible without requiring every stakeholder to open Jurni for each update.

  **Learn more:** [Connect Slack](/integrations/connect-slack) · [Slack performance reports](/notifications/slack-reports)
</Update>

<Update label="August 30, 2026" tags={["Collaboration"]}>
  ## Better page review and comments

  Collaboration on Jurni pages is easier to use across desktop and mobile.

  ### What changed

  * Improved comment-list and popover behavior on mobile.
  * Improved the layout and responsiveness of the review experience.
  * Continued improvements to reviewer access and shared review workflows.

  ### Why it matters

  Marketing, design, and stakeholder feedback can stay attached to the page instead of being reconstructed from screenshots and Slack threads.

  **Learn more:** [Comments in Jurni](/product-updates/jurni-comments) · [Share a page for review](/build/share-review-links)
</Update>

<Update label="August 26, 2026" tags={["Commerce"]}>
  ## Offers now display and apply the correct storefront currency

  Offer thresholds, rewards, and cart behavior now handle store currency more consistently, including supported multi-currency storefronts.

  ### Why it matters

  Shoppers see offer values in the currency used by their storefront, while teams can configure thresholds with clearer currency context.

  **Learn more:** [Offers overview](/commerce/offers-overview) · [Shopify Markets and currency](/commerce/shopify-markets-currency)
</Update>

<Update label="August 24, 2026" tags={["Commerce"]}>
  ## Better product search for non-Shopify catalogues

  Product search now works more reliably for supported non-Shopify and Medusa-backed catalogues.

  ### What changed

  Search can match connected products using product title, handle, description, and relevant variant information such as title, SKU, and options.

  ### Why it matters

  Teams using a connected non-Shopify catalogue can find the intended product more easily instead of browsing through the full product list.

  **Learn more:** [Supported commerce platforms](/getting-started/choose-your-setup) · [Products and variants](/building-funnels/products-and-variants)
</Update>

<Update label="August 20, 2026" tags={["Integrations"]}>
  ## Connect Northbeam from Data integrations

  Northbeam is now available as a Jurni data integration.

  ### Why it matters

  Teams using Northbeam can configure it alongside their other measurement tools and keep attribution setup organized in Jurni.

  **Learn more:** [Northbeam integration](/integrations/northbeam)
</Update>

<Update label="August 19, 2026" tags={["Builder","Media"]}>
  ## Upload SVGs and add media directly from a URL

  The media workflow now supports SVG uploads and a more reliable path for importing images or videos from supported URLs.

  ### What changed

  * Upload SVG assets to the media library.
  * Paste a supported media URL to import it into Jurni.
  * See consistent upload progress and errors across local files and URL imports.

  ### Why it matters

  Teams can bring logos, icons, and campaign assets into Jurni with less manual file preparation.

  **Learn more:** [Assets library](/build/assets-library) · [Edit images and video](/build/edit-content-media)
</Update>

<Update label="August 17, 2026" tags={["Builder"]}>
  ## Restore a previous version of an experience

  Version history now lets you restore an earlier saved version directly in the editor.

  ### Why it matters

  Teams can confidently explore larger changes and return to a known-good version without rebuilding previous work manually.

  **Learn more:** [Version history](/build/version-history)
</Update>

<Update label="August 13, 2026" tags={["Builder","Advanced"]}>
  ## Code mode is available across supported sections

  Supported accounts can inspect and edit the underlying JSX, logic, and props for more sections in the Jurni editor.

  ### Why it matters

  Advanced builders can make precise implementation changes while keeping the work inside Jurni's editing workflow.

  **Learn more:** [Code mode](/build/code-mode)
</Update>

<Update label="August 4, 2026" tags={["Builder"]}>
  ## Sticky sections can pin to the top or bottom

  Sticky page sections are more flexible for campaign CTAs and persistent messages.

  ### What changed

  * Sticky position can be set to **Top** or **Bottom**.
  * Jurni added sticky banner starting layouts for common campaign use cases.
  * Page and preview rendering support the updated sticky positioning behavior.

  ### Why it matters

  You can keep a campaign CTA or important message accessible as shoppers move through a long page without building a separate one-off sticky implementation.

  **Learn more:** [Sticky CTAs](/building-funnels/sticky-cta-banner)
</Update>

<Update label="August 2, 2026" tags={["Builder"]}>
  ## Reposition and crop images directly in the editor

  Jurni added non-destructive image cropping to the editing workflow.

  ### What changed

  You can adjust how an image is framed inside its existing area without creating a new exported asset for every crop.

  ### Why it matters

  This is especially useful when the same source image needs a different focus on a campaign page or responsive layout.

  **Learn more:** [Image repositioning](/product-updates/image-repositioning) · [Edit text, images, and video](/build/edit-content-media)
</Update>

<Update label="April 15, 2026" tags={["AI","Builder"]}>
  ## A new AI-first page-building workflow

  Jurni introduced a redesigned AI chat experience for creating and refining landing experiences.

  ### What changed

  The AI workflow brought campaign context and page creation together with support for richer attachments and references, including product context, media, Figma links, and other campaign inputs available in the Jurni AI experience.

  The experience also added a page preview alongside the conversation so teams can move from the initial AI build into editing more naturally.

  ### Why it matters

  Instead of starting from an empty canvas, teams can begin with the campaign inputs they already have and use Jurni AI as the first step in the build process.

  **Learn more:** [Build with AI](/build/ai-campaign-workflow) · [Academy: Prompting 101](/academy/prompting-101) · [Prompt Library](/academy/prompt-library)
</Update>

## About this changelog

We publish updates when they materially change what a Jurni customer can build, launch, analyze, or collaborate on. Small fixes and internal infrastructure changes are omitted unless they change the customer workflow.

For practical workflows and campaign examples, visit [Jurni Guides](/guides). For exact setup steps, use the Help Center navigation or search.


## Related topics

- [Attribution in Jurni](/analytics-reporting/attribution-overview.md)
- [Jurni Guides](/guides.md)
- [Learn with Jurni](/learn.md)
- [What is Jurni?](/getting-started/welcome.md)
- [Comments in Jurni](/product-updates/jurni-comments.md)