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.

We’re excited to introduce the Continuous Optimization Report in your Constructor dashboard. This report gives you full visibility into how Constructor’s tailored Continuous Optimization Plan drives measurable revenue impact for your business.

💡 What is the benefit?

Constructor has always taken a unique approach to delivering value – not through one-size-fits-all algorithms, but by tailoring search and discovery variants to each customer’s goals and shopper behavior. Until now, these results were shared mainly in your touchpoints with our Customer Success and Data Science teams. With the Continuous Optimization Report, you can now track how experiments are generating value to your business directly in your dashboard, ensuring transparency and confidence in the ROI Constructor delivers.

📍 Where to find it?

You can access the Continuous Optimization Report in your dashboard by selecting Optimization from the side menu. There you’ll see the combined annualized revenue lift from completed experiments, a list of experiments with details like revenue lift, annualized projections, and important context about each experiment's hypothesis. Click any experiment to see its setup, metrics, and outcomes – all in one place!

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.

Constructor now supports Directed Acyclic Graphs (DAGs) for category hierarchies—making it easier to model real-world structures where a single category belongs to multiple sections.

Instead of duplicating categories like “Wireless Headphones” to appear in both "Electronics" and "Gifts," you can now assign multiple parent paths and control which one is shown based on where the shopper is navigating from.

Benefits include:

• Cleaner catalog setup with no duplication of categories
• Flexible hierarchy modeling that reflects real-world relationships
• Better navigation control using query-time path selection

This enhancement also introduces a new groups_path parameter that lets you specify which path to render during browse requests. This results in more precise breadcrumbs and a better contextual experience for shoppers.

🔧 Example Use Case
 A single category, like Wireless Headphones, can appear under:

• Electronics > Audio > Headphones > Wireless Headphones
• Gifts > Tech Gifts > Audio > Wireless Headphones

If no groups_path is passed during a browse request, Constructor automatically uses the first parent path ingested for that category - so you’re always covered by default.

How to Structure Parent Categories

To incorporate multiple parent categories, you’ll need to update your catalog format:

✅ Do this:

• Replace parent_id: "xyz" → with parent_ids: ["xyz"]
• For multiple parents: parent_ids: ["xyz", "abc"]

⚠️ Important:

• Only include parent_ids - do not include both parent_id and parent_ids
• Even a single parent must be wrapped in an array
• Ensure all parent categories are defined before ingestion

• You can send catalogs with multiple parents in either:

  • CSV format via item_groups.csv
  • JSON format via the /v2/item_groups endpoint

You decide which path to show based on the user’s journey - with full validation and fallback behavior built in.

DAG-based category hierarchies are already available in production to all our customers. 

Related docs: Retrieve item groups, Create or replace item groups, Update item groups, Retrieve item group, JSON / JSONL feed format - item groups (categories), CSV feed format - item groups (categories) 

We're beyond excited to unveil a powerful new capability in the Constructor dashboard: Customizable User Roles with View/Edit permissions, now available in beta!

With this release, companies can tailor access like never before. Empower your teams with precisely the tools they need, whether it's managing indexes, merchandising, or launching A/B tests. It's flexible, secure, and built to scale with your company.

Why this matters

Companies tend to have multiple teams working within the Constructor dashboard. From Merchant Teams responsible for all things merchandising, Marketing Teams that use Collections for email campaigns, and Dev Teams in charge of integrations, every group uses the dashboard differently. With Customizable User Roles, you can assign access and permissions that align with each team's responsibilities without compromising control or security.

What you can do

With this release, you can now create custom roles that:

• Control access to company-level settings, such as API tokens and user management
• Allow access to specific indexes (perfect for teams that manage different regions or websites!)
• Grant edit access to individual features, such as Searchandising, Global Facet Configuration, Recommendations, and more.

You can even create a view-only role to invite more stakeholders from different departments who might benefit from the information in the Constructor dashboard, such as reporting and analytics. 

How to get started

All roles start with view-only access permission across all indexes. From there, you can assign edit access to any index and specific features within those indexes. This can be done via the Constructor dashboard. 

For more information, please visit the documentation guide.

With custom user roles, your teams will benefit from tools and information available in the Constructor dashboard without the risk of accidental actions.

We are currently rolling out Customizable User Roles with View/Edit permissions in beta. Please, connect with your Customer Success Manager or contact us through support@constructor.io to get early access.

What’s new:

We’ve upgraded Variation Slicing to give merchandisers more precision than ever.

With the new Variation Slicing Conditions, you can choose exactly which product variations to surface — without slicing all possible variants for every item.

You can now:

• Highlight only the variations you want — e.g., new styles, sale items, or seasonal colors.
• Filter variations with powerful conditions such as Item ID, color, size, or other attributes.
• Mix and match conditions to target exactly the right subset of product variations.
• Visually merchandise your PLPs by promoting only the variations that matter for your campaign.
• Use a drag-and-drop preview to instantly tailor the shopper experience.

Why it matters:

Before, merchandisers had to make a tough choice:

• Slice all variations for an attribute (risking cluttered or irrelevant product listings), or
• Avoid variation slicing altogether — missing opportunities to spotlight specific variations.

Now, you can surgically control variation visibility to align perfectly with your strategy.

 For example:

• Launch a PLP for Valentine’s Day featuring only red dresses.
• Promote only the 12-pack size of a soft drink that’s on sale.
• Push new color drops for a top-selling shoe to the top of the page.

This means more relevant merchandising, more engaging shopping experiences, and more revenue potential — without sacrificing the integrity of your PLP layout.

Learn more in the documentation.