Constructor's AI-powered badges help shoppers quickly identify popular, new, or trending items, making it easier to find products they'll love. These visual labels appear on item tiles and are calculated and assigned automatically, ensuring application to the right products at the right time to boost business KPIs.

With this update, badge assignments are now fully transparent in the Interact section of the dashboard. You can:

• See which items have badges: Instantly view all badged items on any search or browse page, along with their positions in the results
• Understand why: Hover over any badge to see a detailed explanation of why that item received it (e.g., "Bestseller: Top 15% of items by purchases over the last 30 days")
• Review your shopper experience: Quickly verify that badges are being applied as expected and provide feedback when they're not

This transparency helps you understand how Constructor is enhancing your product discovery experience and gives you confidence that badges are driving value for your shoppers.

How to Get Started

This feature is available now for all indexes with badges enabled. Open a search query or browse page in Interact, and look for the Badges section in the Ranking Factors area. Click the counter to see all badged items or scroll the items grid. Hover over a badge to find explanation why an item received it.

If you're interested in enabling badges or have questions about how badges work, learn more in our badges documentation or connect with your Customer Success Manager.

Launching a collection tied to a marketing campaign or limited-time drop often means a tradeoff: prepare early  and risk products showing up too soon, or wait until the last minute and scramble to launch on time.

With Scheduled Collections, you can now set start and end dates for a collection so it is only available to shoppers during the time window you choose.

This means you can:

• Prepare in advance: Build and QA your collection days or weeks ahead of launch.
• Launch on time: The collection becomes available automatically at your scheduled start date.
• End cleanly: Limited-time collections stop being available automatically after the end date (API returns 404 Not Found).

How to Get Started

In the dashboard, navigate to Collections, then create a new collection or edit an existing one. Set your start and or end date to schedule when the Collection should be available.

Note: Updates are evaluated on a short interval, so a collection may become available up to 2 minutes after the scheduled start time.

If you have questions about this release or Collections in general, please connect with your Customer Success Manager or contact us through support@constructor.io.

At Constructor, we always strive for transparent, Glass Box insight into reasoning behind our algorithms. With the latest update, we give you visibility into the impact made by Online LLM Filtering and Burying relevance models.

These models identify the true meaning behind a search query in realtime and analyze how relevant to that query is each particular item within the results. By burying or removing less relevant items, the models make search results cleaner, balancing relevancy and attractiveness and helping shoppers find what they need faster.

Until recently, these powerful AI models worked quietly in the background. Now, you have full visibility in the Interact section of the dashboard into when and how LLM models kick in to improve your search results:

• See when the model is active: LLM Filtering or Burying now appears in the Ranking Factors section of Interact.
• Understand the impact: View which specific items from your top results were removed or buried by LLM models for any search query.

How to Get Started

LLM Filtering and Burying models are available in A/B-test to all our customers. Once the feature is enabled for a particular index, simply navigate to Interact, enter a search query, and look for LLM Filtering or LLM Burying in the Ranking Factors section.

If you have questions about enabling LLM Filtering and Burying models or feedback on this feature, please connect with your Customer Success Manager or contact us through support@constructor.io.

We’ve introduced multi-layered conditions in pod rules setup. This gives merchandisers more granular control when defining the scope and application of a rule.

For example, merchandisers can set up a rule for “If Brand = Apple and Product Type = Smartphone” to boost Apple products within a pod.

Merchandisers can select up to 5 facets when setting up conditions for pod rules.

📍 Where to find it?

1. Navigate to Workspace → Recommendations → Add New → Recommendation Rule.
2. From there, select the pod(s) you want to set up rules for.
3. Select multi-layered conditions. 

If you have any questions or feedback on the updated feature, please connect with your Customer Success Manager or contact us through support@constructor.io

What’s new

With the recent launch of Audience Hub, Affinity, RFM, and Location segments are now available in Searchandising — expanding our Custom & Dynamic segments and upgrading how you target shoppers in rules and campaigns.

You can now pick segments based on:

• Affinity (what brands/categories/styles a shopper tends to prefer)
• RFM (purchase Recency, Frequency, and Monetary value)
• Location (geographic shopper segments)

As you select a segment, you’ll also see whether it matches the traffic volume you intend to target, so you can make confident, data-driven choices while configuring.

Why it matters

Previously, many merchandising strategies were applied too broadly (because the necessary segment wasn’t available in Searchandising or was hard to maintain), which could dilute impact and sometimes actively hurt performance when irrelevant shoppers see promoted items.

With Affinity, RFM, and Location segments:

• Target the shoppers your strategy is actually designed for, without relying on custom segment pipelines.
• Maximise incremental impact by showing promotions only where they’re likely to help.
• Avoid “segment guesswork” by checking intended traffic volume while you configure.

Example workflows

• Launch new arrivals to high-intent fans. Promote a newly arrived Nike drop only to shoppers with a strong Nike affinity, instead of pushing it to everyone.
• Run clearance with precision. Target sale campaigns to frequent buyers, or to shoppers whose recency is dropping (and may need a nudge).
• Localise merchandising. Highlight weather-appropriate or region-specific inventory to shoppers in the relevant locations.

If you have any questions or feedback on the new feature or the Constructor dashboard in general, please connect with your Customer Success Manager or contact us through support@constructor.io.

We are thrilled to announce the launch of Audience Hub, a new way within the Constructor dashboard to get a clear, centralized view of your shoppers and their characteristics at scale through segmentation.

Previously, segment data was fragmented and difficult to access, making it hard to grasp the size and opportunity each segment represented. Audience Hub solves this by bringing all your meaningful segmentation data into a single location, making it an easy starting point for understanding and further optimization.

Audience Hub Main Page

With Audience Hub, you can:

• Gain a deeper understanding of your users: See shared similarities across your users, such as affinity for specific brands (e.g., Nike) or locations (e.g., Canada). See top searches, items viewed, added to cart and purchased for each segment.
• Centralize and visualize all segments: Access a single source of truth for all user segments, including geo, device, customer provided and AI generated smart segments (such as Affinity and RFM).
• Identify high-impact opportunities: Understand the exact size and opportunity that various segments represent, making it easy to decide which ones are worth further review and action through onsite and offsite optimizations.

Segments Drawer within Audience Hub provides more segment details.

We’re excited to make this available now, and we’re just getting started with segments. Keep an eye out for more to come in this space.

If you have any questions or feedback on the new feature or the Constructor dashboard in general, please connect with your Customer Success Manager or contact us through support@constructor.io.

What’s new

Facet campaigns are here. You can now apply one set of facet rules — slotting and/or hiding facet groups and options — to many results pages at once, instead of configuring each page separately.

A single facet campaign can target a mix of:

• Search queries (e.g. “denim”, “running shoes”, “ground coffee”)
• Browse category pages (e.g. Shoes, Coffee, Skincare)
• Facet pages (e.g. “Size 7” Shoes, “Straight Leg” Denim)
• Collections (e.g. “Viral Hits”, “Kid’s Summer Shoes”)

Think of it as Searchandising Campaigns, but for facets: one place to define the order and visibility of your filters across a whole group of related pages.

Each facet campaign currently supports up to 100 queries and 100 browse/facet/collection pages (combined).

Why it matters

 Previously, keeping filters tidy and consistent meant repeating the same facet rules on every individual page:

• Hiding niche facet groups (like “Heel height”) on categories where they barely apply
• Reordering key facets (like “Brand” or “Sale”) across long trees of categories and collections
• Repeating the same updates every time your strategy changes

With facet campaigns, you:

• Configure once, reuse everywhere. Define facet ordering and visibility in a single campaign and apply it to all related pages.
• Keep filtering experiences clean. Hide facet groups and options that only matter to a tiny subset of items so shoppers aren’t scrolling through noisy filters.
• Stay consistent across parent and child PLPs. Align the filtering experience across a parent category (e.g., “Shoes”) and its children (e.g., “Boots”, “Heels”, “Sneakers”) without micromanaging each page.
• Move faster when strategy changes. Update a single campaign instead of revisiting dozens of PLPs when you change priorities (e.g. pushing “Sale” or your own brand to the top).

Example workflows

• Tidy up irrelevant facets at scale. A retailer only wants to show Heel height on women’s boots and heels—not on sneakers, kids’ sandals, or men’s trainers. They create a facet campaign, attach Shoes, Athletic Shoes, and Kid’s Summer Shoes pages and collections, and hide “Heel height” once. All included pages inherit the same tidy filter set.
• Promote own brand across a family of pages. A beauty retailer wants their own brand to appear first in the Brand facet on search results, “Makeup” categories, and “Viral Hits” collections. They add these contexts into a single facet campaign and slot their brand option to position #1—no need to repeat the rule per page.
• Align parent and child categories. A fashion retailer wants a consistent set of filters across Denim, Denim > Straight Leg, and Denim > Wide Leg, but with fewer facets on the narrower children pages. They build a facet campaign for all denim-related pages, then hide niche facet groups from specific sub-pages while keeping core filters aligned.
• Seasonal or promo-focused filtering. During peak season, a merchandiser wants the Sale, New in, and Sustainability facets to rank higher across key search queries, categories, and promo collections. They create a campaign, slot those facets near the top across all relevant contexts, and adjust positions from a single configuration when the season changes.

Learn more

• Create a facet campaign
• Configure facet rules

Introducing a major update to API tokens that gives your engineering and admin teams precise, "least-privilege" control over API access.

The Challenge: The "All-or-Nothing" API Key

Previously, API tokens (now referred to as Legacy tokens) were company-wide, granting full read and write access to all Constructor endpoints across all your indexes. While powerful, this created potential risks. A leaked token technically, could expose all your data, and a simple misconfiguration in a script could accidentally apply changes to the wrong environment.

The Solution: API tokens with Custom Level of Access

Now, you can build API tokens with a specific, limited scope. When creating a new token, you can define:

• Indexes: Specify which indexes the token can access. This is perfect for isolating your Production, Staging, and Dev environments or managing different websites.
• Scopes: Select which API endpoints the token can use (e.g., searchandising.refined_queries, searchabilities,  synonyms).
• Permission: Define the permission level for those scopes: Read & Write, Read, or Write.
• Expiration Date: Set an optional expiration date. We recommend renewing API tokens regularly.

By limiting access to what is really needed, you reduce security risks if a token gets compromised and rule out the possibility of applying changes to the wrong environment.

Putting API Tokens into Practice

This new control allows you to securely manage complex, multi-team workflows:

• For Integration Scripts: Create an API token that has access only to scopes within the dev_index to test things before applying changes in production.
• For Regional Teams: Give your EU engineering team an API token that can Read & Write to all scopes only on the eu_site index, preventing accidental changes to the US site.

Better Together: API Tokens + Customizable User Roles

This update works hand-in-hand with our recent Customizable User Roles feature. Only users assigned with a role that has Manage API tokens permissions can set up API tokens. Users' ability to create API tokens is limited by their role permissions. An administrator can create tokens for any scope, but a user with a specific role (e.g., "US Merchandiser") can only create API tokens for the indexes and features they are already permitted to access. 

This ensures your permission model is consistent, from the dashboard UI right down to the API.

A Note on Legacy API Tokens

Your existing tokens (now labeled Legacy tokens in the dashboard) will continue to work without interruption. However, you can no longer create new tokens of this type. We highly recommend you audit your existing integrations and begin migrating to the new, more secure API tokens as part of your team's security best practices.

How to Get Started

This feature is now live for all customers. Administrators and users with the appropriate permissions can create new tokens by navigating to Integration > API Tokens in the dashboard.

For a complete, step-by-step guide, please visit our updated documentation: Generate and manage API tokens.

If you have any questions or feedback on the new feature or the Constructor dashboard in general, please connect with your Customer Success Manager or contact us through support@constructor.io.

What's new

You can now target customer-defined user segments across most searchandising rules—not just Boost & Bury. That means you can adjust ranking, recall, content, and slotting for specific audiences (e.g., "US App Users", "Loyalty Tier Gold", "Clicked Meta Ad A") without rebuilding pages or bluntly applying rules to everyone.

You can now

• Apply segments to key rules and surfaces
  • Boost & Bury — Search, Browse, Campaigns, Recommendations, Global
  • Item Slotting (incl. CSV & faceted browse) — Search, Browse, Campaigns, Recommendations
  • Attribute-based Slotting — Search, Browse, Campaigns, Recommendations
  • Allowlist / Blocklist — Search, Browse, Campaigns, Recommendations (Blocklist also on Global)
  • Content Rules — Search, Browse, Campaigns
• Preview as a segment when creating Campaigns: Impersonate a selected segment to see exactly what that audience will experience before you ship.

Why it matters

Previously, segments were available for Boost & Bury only. Teams either ignored insights or applied broad rules to all shoppers, diluting performance. With segments available across your core rule types, you can:

• Tune the same PLP differently per audience (locale, device, lifecycle stage).
• Move faster from marketing signal to on-site personalisation without duplicating pages.
• Protect performance by narrowing rules to only the shoppers they're meant for.

Example workflows

• Campaign continuity: For users who clicked a specific ad or email, slot the exact products that match the message they saw, right on arrival.
• Locale nuance: Slot a colorway or size range for only a particular country/segment without touching other markets.
• Compliance fast-track: Blocklist prohibited items for a single region while keeping them live elsewhere.
• Channel-aware content: Show different banners/copy to app users vs web visitors on the same PLP.

Who benefits

• Merchandisers partnering with Marketing: align landing experiences to campaign promises.
• Region/brand owners: tailor assortment and messaging by locale without forking your catalog.
• Compliance & ops teams: react quickly to region-specific restrictions.

Coming soon

• AI-generated segments
• Segments in Content Rules (Global)
• Segments in Variation Slicing
• Impersonation for Search, Browse, and Global

Learn more

• Configure searchandising rules
• Create a searchandising campaign

To learn more, please contact your Customer Success Manager or support team.

We are excited to announce the general availability of Customizable User Roles with View/Edit permissions. This powerful new capability is now live in the Constructor dashboard for all customers. 

This feature allows enterprise e-commerce companies to provide every member of their team with tailored access, ensuring they have exactly the tools they need to excel—without compromising security or control.

The Challenge: Scaling Operations Securely

As an e-commerce business scales, more teams rely on a central platform for daily tasks. The Merchandising team fine-tunes results across the product discover journey, the Marketing team builds campaign-specific collections, and the Development team manages integrations and indexes. Each team has a unique focus, and providing one-size-fits-all access can create bottlenecks and introduce the risk of accidental changes to critical settings.

The Solution: Granular Control, Tailored for Your Business

Customizable User Roles solve this challenge by providing precise control over what each user can do. This functionality allows you to:

• Safeguard Critical Settings: Protect company-level information, such as API tokens and user management, by restricting access to only designated administrators. 
• Isolate Access by Index: Assign users to specific indexes, making it perfect for managing different regions, websites, or environments (e.g., Staging vs. Production) without overlap. 
• Assign Feature-Specific Permissions: Grant Edit permissions for individual features. Empower your merchandisers to manage Searchandising and Facets while restricting access to A/B Testing or Recommendations for designated roles. 
• Promote Data-Driven Decisions with View-Only Access: Create view-only roles for executives, analysts, and other stakeholders. This allows them to access valuable performance reports and analytics without the ability to make changes. 

Putting Roles into Practice 

With this level of control, you can create highly specific roles that map directly to your operational structure: 

• The Digital Merchandiser (B2B): Gets Edit access to Searchandising, Facets , Collections, A/B Testing, and Global Facet Configuration for the B2B website index, but has View access everywhere else. 
• The Marketing Specialist: Can only Edit the Collections feature to prepare for an upcoming email campaign. 
• The Regional Manager (EU): Has View access to global indexes but can only Edit merchandising rules for the eu_site index. 
• The Developer: Is given Edit access to the staging_index to test a new integration but has only View access to the production environment.

How to Get Started

This feature is now available in your dashboard. Administrators can begin creating and assigning roles today by clicking on their name in the bottom left corner, then Team Members, then switch to the User Roles tab. For a detailed walkthrough on creating roles and assigning permissions, please visit our documentation guide.

If you have any questions or feedback on the new feature or the Constructor dashboard in general, please connect with your Customer Success Manager or contact us through support@constructor.io.