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)Stratification Violation ErrorAudience 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
  • Campaigns
  • Audience expansion

Audience expansion

Description​

Audience expansion is a mechanism that automatically adds new profiles to a campaign from the segments of activities included in it. This mechanism increases campaign reach and keeps its audience up to date without manually updating the initial segment.

Each campaign is created using a static segment that defines its target audience. However, inside a campaign, each activity can be configured for any segment, even if it does not intersect with the main one.

For example, a campaign targets the "Loyal customers" segment, but inside it you create a mailing aimed at the "New registrations" segment. Without audience expansion, these users will not receive the message because they are not part of the campaign audience. But if audience expansion is enabled for this mailing, the system will automatically add recipients from "New registrations" to the campaign and distribute them between the test group and the local control group, if LCG is enabled.

Key limitations
  • Only activities of this campaign — you cannot select a mailing or scenario from another campaign
  • Only non-completed activities — activities with the "Completed" status cannot be selected
  • Only profiles from the campaign’s Profile database — even if the activity segment contains profiles from other databases, only profiles from the campaign’s database will be added
  • Only new profiles — only profiles not yet in the campaign audience will be added

How audience expansion works​

Audience expansion enriches the campaign with new profiles directly from the audience of launched activities. Its core principles:

  • When an activity is launched, the system determines its audience (segment or entire base) and automatically adds profiles that are not yet part of the campaign;

  • New participants are immediately distributed between the test group and the control group;

  • Users outside the campaign’s profile database will not receive the message;

  • If a profile appears in the segments of several audience expansion activities within the same campaign, it is added only once. Its group assignment (test or control) is fixed at that moment, preventing accidental reassignment later;

  • Audience expansion works only for active campaigns.

caution

Audience expansion adds profiles to the static segment of the campaign (its initial audience). Any recalculation of that static segment removes all profiles added through audience expansion.
To avoid this, it is not recommended to enable "Update segment daily" for the campaign segment.

Profile addition process​

For every profile in the activity audience, the system checks:

  • Profile database match:
    The profile must belong to the same profile database as the campaign.
    Otherwise, it will not enter the campaign audience and will not receive the message.

  • Campaign participation:
    The system checks whether the profile is already in the campaign audience.

    • If yes — it receives the message (unless it's in LCG).
    • If no — it is distributed into the test or control group based on LCG settings.
      Profiles placed into the test group will receive the message; those placed into the control group will not.

Usage example​

Scenario without audience expansion

The campaign uses the CRM_Base profile database and the Loyal customers segment (100 profiles).
A broadcast is created with the segment New registrations (50 profiles). These users are not part of the campaign and do not intersect with the main segment.

When the broadcast is launched, no one receives the message because there is no overlap — these profiles are not in the campaign.

Scenario with audience expansion

If you add this broadcast to the Audience expansion list in the campaign settings, the system includes all recipients from New registrations in the campaign.
After that, profiles are automatically distributed between the test group and the local control group.

Audience expansion setup​

Audience expansion is configured in the Audience section of the campaign editor, in the Audience expansion block:

Selecting activities​

The following types of activities are available:

  • Broadcasts — one-off mass sends
  • Regular mailings — scheduled communications
  • Triggered mailings — automated event-based sends
  • A/B tests — variant comparison
  • Scenarios — multi-step automations
  • Placements — on-site content placements

tip

You can select multiple activities. Each activity independently adds new users to the campaign when it is launched.

Last updated on Mar 12, 2026
Previous
Stratification Violation Error
Next
Audience building
  • Description
  • How audience expansion works
    • Profile addition process
    • Usage example
  • Audience expansion setup
    • Selecting activities
© 2015 - 2026 Altcraft, LLC. All rights reserved.