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
  • Segmentation
  • Updatable Segments

Updatable Segments

A scheduled segment is a segment that automatically recalculates its composition based on specified conditions according to a set schedule (for example, once a day). Its list of profiles is current at the moment of the last recalculation.

info
  • Filling: The segment cannot be filled manually or via API. It is filled only based on specified conditions according to the schedule or during manual recalculation.
  • Usage: The segment can be used in the same places as a static segment (for example, in mailings, scenarios, triggers).

Creating a Segment​

To get started, go to Data → Segments → Scheduled Segments.

In the scheduled segments list, click + Create. In the form that opens, specify the Name of the segment — this is a required field. Then select the segment source (Database). Segment creation is impossible without selecting a database:

info

After selecting a source, it cannot be changed.

Configuring Conditions​

After selecting the database, the Conditions and Schedule block will open. The mechanics of configuring conditions are completely identical to dynamic and static segments. You can set the Range, which defines the portion of the database for applying conditions.

To add a rule, click the + Condition button. In the dropdown menu, the options Add Condition Group and Import Conditions are available. After configuring conditions within a group, they can be combined using must comply with each of the conditions (AND) or must comply with one of the conditions (OR) logic:

In the same block, the Delete button, which completely clears all set rules, and the Script button, which opens an editor for manually writing conditions, are available.

After configuring the conditions, you can set limitations by activating the checkbox Set a limit on the maximum number of profiles in the segment to specify a limit. This limitation is applied to the selection result after selection by range and conditions.

More about how audience limitations work

Limit on the maximum

Maximum profile count limit — the limit on the number of profiles that can be included in a segment.

This method limits the size of the final segment. You specify the maximum number of profiles that can be included. If more people match the segmentation conditions, the platform takes the first profiles from the resulting sample.

For example, if 1,000 people match the conditions and the maximum count is set to 400, the first 400 profiles will be included in the segment. This restriction applies to the sample result of the segment. If a range is also used, the range restriction is applied first, and then the profile count limit is applied to the selected portion of the database.

Range

The range determines which portion of the entire database will participate in segmentation. By default, it is set to 100%, meaning the conditions apply to all profiles. The key feature is that the range is tied to specific users: each profile in the database is assigned a numeric value, and the same range always selects the same people.

This means the selection is not random. A profile is included in the segment if its assigned value falls within the selected range. This allows you to create non-overlapping groups by setting different ranges — for example, a range from 0 to 20% and a range from 80 to 100% will never intersect.

When new users are added to the database, they are distributed according to the same rules: if a 20% range is selected, a new profile has the same probability of falling into it.

If a maximum profile count limit is also used, the range is applied first to determine the portion of the database, and then the limit takes effect within that portion.

Configuring the Schedule​

In the Conditions and Schedule block, configure the parameters for automatic updates. Specify the exact time for launch (HH:MM) and select the timezone. Then set the frequency of recalculation from the available options: daily, on a specific date, by time (days of the week, days of the month, etc.):

Optionally, you can activate the function Deactivate schedule after the specified date so that automatic updates stop on a given day.

After configuring all parameters, click Save. The first calculation will start at the nearest scheduled time.

Working with a Created Segment​

After creating and saving the segment, its page will open. Now, in the upper right corner, next to the fields for tags and access groups, additional actions for working with the current profile selection become available:

  • Copy Profiles to Profile Database;
  • Copy Profiles to Static Segment;
  • Export Profiles;
  • Bulk Edit Profiles;
  • Add Profiles to Scenario.

info

Actions with profiles will become available after the first segment update.

Managing Automatic Updates​

The Automatic Segment Update block displays the current schedule. From here, you can Stop"/"Start (depending on the current state), Reconfigure Schedule, or Launch Manual Recalculation outside the scheduled time.

caution

Manual recalculation and editing of the update schedule are unavailable during segment update execution (automatic or manual).

Below is the Show Update Conditions spoiler. When expanded, it displays all set conditions, range, and limit. They can be edited, the script can be viewed, or they can be deleted.

Analyzing Composition and History​

After the first update, the Profiles Table with the current composition will become available on the segment page:

Update History​

The Update History block is a graph visualizing changes in the number of profiles in the segment over the selected period. The period can be set using the calendar or ready-made options (today, last 7 days, this month, etc.), and data can be grouped by days, weeks, months, quarters, or years. When hovering over a point on the graph, a breakdown by profiles is displayed: added or removed automatically and manually:

Log​

The Log block is a table with detailed information for each recalculation run. For each operation, the start and end date and time, type (Manual / Automatic), initiator (user or "System"), number of added and removed profiles, and status (In Progress, Completed, Error) are indicated.

Dependent Objects​

If the segment is used in other platform entities (mailings, scenarios, loyalty programs), the Dependent Objects block will appear below the update log:

Managing Segments from the General List​

In the row of the desired scheduled segment in the general list, the following actions are available:

  • Copy Profiles from Segment: Copy the list of profiles from the current segment to another selected segment.
  • Update Profiles: Mass-modify profile data in the segment (e.g., update fields, add a subscription).
  • Export Profiles: Export data of profiles included in the segment to an external file.
  • Export Profile History: Export interaction and change history for profiles from the segment.
  • Analytics: Go to analytical reports for this segment.
  • Clone Segment: Clone the segment conditions, tags, access groups, profile database, and schedule.
  • Delete Segment: Completely delete the segment.

Last updated on Mar 27, 2026
Previous
Dynamic Segments
Next
Segmentation Conditions
  • Creating a Segment
    • Configuring Conditions
    • Configuring the Schedule
  • Working with a Created Segment
    • Managing Automatic Updates
    • Analyzing Composition and History
      • Update History
      • Log
    • Dependent Objects
  • Managing Segments from the General List
© 2015 - 2026 Altcraft, LLC. All rights reserved.