Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guide iconUser guide
Developer guide iconDeveloper guide
Admin guide iconAdmin guide
English
  • Русский
  • English
Login
    User documentationGetting StartedFAQAltcraft glossary
      Profiles and databasesarrow
    • Subscription resourcesManaging databasesSubscriber profileProfiles import and data updateScheduled customer data importAutomatic data collectionBulk customers profiles updateDouble opt-in subscriptionSuppression listsProfile relationsProfile history exportProfile exportCreating a static segment based on import resultsHow to open a CSV fileMatchingTypes of fields in the databaseGlobal control groupsSubscription Manager
      Communication channelsarrow
      • Email channelarrow
      • Email: ISP interactions best practicesEmail: sending domain configurationEmail: setting up and using postmastersБыстрый старт
        Push channelarrow
        • Mobile Pusharrow
        • Settings & implementation
            Integrate your app with Altcraftarrow
          • Providers: push message structureProcessing and adding a subscriptionEvent registration
          Web pusharrow
        • Preliminary Settings
            Web browser push configurationarrow
          • Firebase Cloud messagingApple SafariMozilla Services
          Connecting Web Push to a WebsiteTransferring Data to the PlatformWeb Push SDK Methods
            Import of subscriptions from third-party push servicesarrow
          • Migrating push subscriptions from third-party servicesHow to transfer push subscriptions configured for Safari?Migration from OneSignal
      SMS channel
        Creating mailing from scratcharrow
      • EmailSMSWeb PushMobile PushWhatsAppViber*™Руководство: SMS-рассылка через VK NotifyMAX BotMAX GroupNotifyTelegram BotTelegram Group
      Communication Channels WorkflowРуководство: SMS-рассылка через УТШРуководство: push-рассылка через сервис от "Согласие"
      Segmentationarrow
    • Static SegmentsDynamic SegmentsUpdatable Segments
        Segmentation Conditionsarrow
      • Segmentation by Profile dataSegmentation by Interactions with EntitiesSegmentation by Activity of the channelSegmentation by external dataSegmentation by external SQL tablesSegmentation by Profile structure
      Best Send Time (BST)Logical operators "AND" and "OR"Recommendations for working with segments
      Message templatesarrow
      • Working with message templatesarrow
      • Working in the editorEmail-templateSMS templatePush templateMAX templateTelegram templateWhatsApp templateViber™ templateNotify template
        Visual editor for email-templatearrow
      • Visual editor interfaceAdding blocksElements and their settingsCustom blocksStyle managerLayer manager
      Template fragmentsImage galleryContent personalizationCreating tables based on array elementsBlock editor for email template
        Altcraft Variables and Functionsarrow
      • Logical expressions in messagesLoops in messagesMarket variables in templatesUsing the JSONPath functionality
        Dynamic content in messagesarrow
      • Dynamic HTML contentDynamic JSON contentContent from SQL database in templatesDynamic API content
      Importing and exporting a message templateImporting a template from a third-party serviceExporting a template from Pixcraft
      Mailingsarrow
    • Mailings calendarBroadcast mailingsRegular mailingTrigger mailingMultivariate testingMailing testingMailing schedulePlacement mailing
      Campaignsarrow
    • Working with CampaignsLocal control groups (LCG)Audience expansionAudience building
      Automation scenariosarrow
    • Managing scenariosNodes of the scenarioClassic marketing scenariosStep-by-step welcome scenario guideScenario for automatic notification of the managerAbandoned cart scenario
      Marketarrow
    • Market settings
        Productsarrow
      • How to create a product manuallyHow to import a product from a fileScheduled product importProduct and SKU SegmentsPreparing the YML file
      OrdersMarket variables in message templateGuide: how to send an order confirmation email
      Loyalty programsarrow
    • Loyalty programsLoyalty integration with external systemsБыстрый стартBasic loyalty program use casesOrder SegmentsPromotion codes
      Reports and analyticsarrow
    • Channel reportTraffic report
        Summary reportarrow
      • Summary report metrics
      Cohorts reportLifetime reportFunnels reportGoals reportAudience growth reportClick map reportLoyalty programs reportBounces reportUndeliveries reportReport on global control groups
      Integrationsarrow
      • Action hooksarrow
      • Altcraft Action HooksAction hooks event typesAction Hook Message StructureJSON batch request (HTTP POST action hook)Message to RabbitMQ brokerMessage to RabbitMQ exchangerMessage to Kafka brokerTest event
        Integration of third-party services using Albatoarrow
      • Connecting Altcraft to Albato Launching the welcome scenario using AlbatoTransmitting event dataSetting app a trigger mailingEvent registrationGoogle Sheets and Altcraft integration AmoCRM and Altcraft integration
      Facebook Ads Manager™Google Ads AudiencesMAXYandex.Audience™VK Ads™Static segment synchronizationYandex AppMetrica™Tilda™Lpgenerator™WhatsAppViber*™ integrationIntegration scopeData Transmitted During SynchronizationNotify
      Weblayersarrow
      • Formsarrow
      • Create a formForm constructorAppearanceActions after form activationData analyticsBinding data channel and formsConditional logic in forms and surveysNPS testing
        Pixelsarrow
      • Goal customer actions and scoring
        Pop-upsarrow
      • Creating and publishing a pop-upSetting up a popup in the code editorManaging pop-ups manually via scriptPopup analyticsGuide: pop-up for push subscriptionsCase: Creating a pop-up with the "Wheel of Fortune" widgetBasic cases of placing a popup via the Tag Manager
        Tag Managerarrow
      • Configuring and installing Tag ManagerTrigger typesVariables typesLinking a pixel and the Tag manager
      Settingsarrow
    • Account settingsCustom linksVirtual sendersSending policiesAudit journalTags FAQ
        Users, groups and accessarrow
      • Two-Factor Authentication (2FA)
        Connectionsarrow
      • Connection to Facebook Ads ManagerConnection to Google AdsConnecting to Yandex.Audience™Connection to 360dialogConnection to EdnaConnection to Devino TelecomConnection to SMSTrafficConnection to VK Ads™Connection to MTS OmniChannelCustom Authentication ConnectionOAuth2 connectionBasic Authentication connectionToken Authentication connectionConnection to RapportoMAX connectionConnection to Notify
      Attribute settings
      API requests: where to startarrow
    • Import or update a profileTrigger mailing launchEngage profile in scenario
      Changelogarrow
    • v2026.1.76v2025.4.75v2025.4.74v2025.3.73v2025.2.72v2025.1.71v2024.4.70v2024.3.69v2024.2.68.2v2024.1.68
    Documentation archivelibrary
  • Market
  • Products
  • Product and SKU Segments

Product and SKU Segments

Segmentation in Altcraft

Product and SKU segmentation works the same way as profile segmentation in the platform. More details about the condition builder and segmentation logic are available in this section.

Description​

Product and SKU segments are sets of products and their modifiers (SKUs) grouped by a specific criterion. A finished segment can be exported and used for sales data analysis. There are two types of segments: static and updatable.

Updatable Segments​

Updatable segments are product and SKU sets that are recalculated on a schedule based on defined conditions. Such a segment can also be recalculated manually outside the schedule.

To create an updatable segment, go to Market — Updatable segments:



Click "Create". Specify a name, description, and select entities for segmentation — products or SKU. After selection, the segment type cannot be changed:

Then the "Conditions and schedule" block opens. Select conditions or condition groups and set a schedule for automatic updates. Conditions inside a group can be combined using "match all conditions" (AND) or "match any condition" (OR). These settings remain editable later.

Conditions are divided into three groups:

  • Core fields — filtering by name, region, category, product quantity, expiration date, price, delivery, warranty, availability, manufacturer, and tags.
  • System fields — filtering by identifier, additional (string) identifier, creation date, and update date.
  • Custom fields — filtering by user-defined fields.

The same block contains the "Script" button, which opens an editor for manual condition writing. After setting conditions, you can define a product count limit. This limit applies to the selection result after condition filtering.

A segment can be updated daily or on specific days. Update time and time zone are set by the user:

You can also configure automatic segment deactivation after a specified date.

After calculation, the segment view displays a table with all products included in the segment. It shows the fields "Name", "Identifier", "Price", "Quantity", and a button to open product editing:

Available actions for this table:

  • Search : find a specific product.
  • Export products : export the displayed list to an external file.
  • Configure displayed fields : add or remove table columns by dragging a Field from the "Add field" sidebar to "Displayed fields" or back.

Below the product table are the segment update schedule and conditions. Here you can edit them or recalculate the segment outside the schedule:

Below is the "Update history" block. It visually shows changes in the total number of products in the segment for the selected period. You can specify a date range and group data by days or weeks.

Below the update history is the "Log". It contains a detailed record of all operations affecting the segment composition. For each operation, the following is shown:

  • Start date: time when the segmentation process started (adding/removing by conditions).
  • End date: time when the process finished.
  • Initiator: name of the user who initiated the operation.
  • Added: number of products added as a result of the operation.
  • Removed: number of products removed as a result of the operation.
  • Status: current operation state (for example, "Completed", "In progress", "Error").

Segment actions

At the top of the screen, a quick actions menu is available, where you can assign tags, configure access groups, and copy products to another segment.

Static Segments​

Static product segments are sets of products and their modifiers (SKU) grouped via API or manually using selection conditions.

To create a static segment, go to Market — Static segments:



Click "Create". Specify a name, description, and select entities for segmentation — products or SKU. After selection, the segment type cannot be changed:



The segment is created. To add products, click "Add" — the "Conditions" block opens.

To add a rule, click "+ Condition". The dropdown menu contains the "Add condition group" option. Conditions inside a group can be combined using "match all conditions" (AND) or "match any condition" (OR):

Conditions are divided into three groups:

  • Core fields — filtering by name, region, category, product quantity, expiration date, price, delivery, warranty, availability, manufacturer, and tags;
  • System fields — filtering by identifier, additional (string) identifier, creation date, and update date;
  • Custom fields — filtering by user-defined fields.

The same block contains the "Clear" button, which fully removes all defined rules, and the "Script" button, which opens an editor for manual condition writing. After setting conditions, you can define a product count limit. This limit applies to the selection result after condition filtering.

After clicking "Add", products matching the selection rules appear in the segment. To remove products from the segment, click "Remove". The removal function works the same way as adding products.

After calculation, the static segment view displays a table with all products included in the segment. It shows the fields "Name", "Identifier", "Price", "Quantity", as well as a quick actions menu for removal or opening product editing:

Available actions for this table:

  • Search : find a specific product.
  • Export products : export the displayed list to an external file.
  • Configure displayed fields : add or remove table columns by dragging a Field from the "Add field" sidebar to "Displayed fields" or back.

Below is the "Update history" block. It shows changes in the total number of products in the segment for the selected period. You can specify a date range and group data by days or weeks.

Below the update history is the "Manual changes log". It contains a detailed record of all operations that affected the segment composition. For each operation, the following is shown:

  • Start date: time when the segmentation process started (adding/removing by conditions).
  • End date: time when the process finished.
  • Initiator: name of the user who initiated the operation.
  • Added: number of products added as a result of the operation.
  • Removed: number of products removed as a result of the operation.
  • Status: current operation state (for example, "Completed", "In progress", "Error").

Segment actions

At the top of the screen, a quick actions menu is available, where you can assign tags, configure access groups, and copy products to another segment.

Conditions​

Conditions for selecting products and SKUs are divided into three groups: Main Fields, System Fields, and Additional Fields. The available set of operators depends on the type of selected field.

Main Fields​

Main fields include standard product or SKU fields: name, category, price, quantity, and others.

Product Name

A string field containing the product name.

  • is equal to / is not equal to
  • contains / does not contain
  • begins with
  • is in list / is not in list
  • is in data table / is not in data table
  • is in file in column / is not in file in column
  • is in a field of post url response / is not in a field of post url response

Region

A field for specifying the sales region or product availability.

  • exists / does not exist
  • is equal to / is not equal to
  • is in list / is not in list

Category

A field containing one or more categories to which the product belongs.

  • exists / does not exist
  • contains at least one value from the list
  • does not contain any values from the list
  • contains all values from the list
  • does not contain all values from the list at the same time

Product Number

An integer reflecting the remaining stock or available quantity.

  • is empty / is not empty
  • is equal to / is not equal to
  • is greater than / is less than
  • is greater than or equal to / is less than or equal to
  • in the range

Expiration Date

A date type field indicating the product's expiration date.

  • is equal to / is not equal to
  • is greater than / is less than
  • is greater than or equal to / is less than or equal to
  • exists / does not exist
  • in the range

Price

A numeric field with the current product price.

  • exists / does not exist
  • is equal to / is not equal to
  • is greater than / is less than
  • is greater than or equal to / is less than or equal to
  • is in list / is not in list
  • in the range

Old Price

A numeric field with the price before discount (if applicable).

  • exists / does not exist
  • is equal to / is not equal to
  • is greater than / is less than
  • is greater than or equal to / is less than or equal to
  • is in list / is not in list
  • in the range

Delivery

A boolean field (true/false) indicating whether delivery is required for the product or available.

  • true
  • false

Guarantee

A boolean field (true/false) indicating whether the product has a warranty.

  • true
  • false

Accessibility

A switch field reflecting the product's availability status.

  • available
  • not available

Manufacturer

A string field with the manufacturer's company name.

  • exists / does not exist
  • is equal to / is not equal to
  • contains / does not contain
  • is in list / is not in list
  • is in data table / is not in data table
  • is in file in column / is not in file in column
  • is in a field of post url response / is not in a field of post url response

Tags

A list field used for flexible product tagging.

  • exists / does not exist
  • contains at least one value from the list
  • does not contain any values from the list
  • contains all values from the list
  • does not contain all values from the list at the same time

System Fields​

Fields automatically filled by the platform or used for internal identification.

Identifier

A unique numeric product ID in the system.

  • is equal to / is not equal to
  • is in list / is not in list
  • is in data table / is not in data table
  • is in file in column / is not in file in column
  • is in a field of post url response / is not in a field of post url response

Additional Identifier

A string field for storing an external ID (e.g., SKU from 1C or product code).

  • is equal to / is not equal to
  • is in list / is not in list
  • is in data table / is not in data table
  • is in file in column / is not in file in column
  • is in a field of post url response / is not in a field of post url response

Product/SKU Creation Date

A date type field recording the moment the record was created in the platform.

  • is equal to / is not equal to
  • is greater than / is less than
  • is greater than or equal to / is less than or equal to
  • month is / month is not
  • month is the same as today
  • month day is / is not / is greater than / is less than / is the same as current
  • day and month are / are not / are greater than / are less than / are the same as current
  • is in list / is not in list
  • is in a date range
  • date relative to current date — selection based on a moment in the past or future (e.g., "created in the last 7 days")

Product/SKU Update Date

A date type field recording the moment the record was last modified.

  • is equal to / is not equal to
  • is greater than / is less than
  • is greater than or equal to / is less than or equal to
  • month is / month is not
  • month is the same as today
  • month day is / is not / is greater than / is less than / is the same as current
  • day and month are / are not / are greater than / are less than / are the same as current
  • is in list / is not in list
  • is in a date range
  • date relative to current date

Custom Fields​

You can create your own fields in the catalog structure to store specific product information. For segmentation, operators corresponding to the created field type (string, numeric, date, boolean, etc.) are available.

Last updated on Mar 12, 2026
Previous
Scheduled product import
Next
Preparing the YML file
  • Description
  • Updatable Segments
  • Static Segments
  • Conditions
    • Main Fields
    • System Fields
    • Custom Fields
© 2015 - 2026 Altcraft, LLC. All rights reserved.