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
  • Settings
  • Virtual senders

Virtual senders

Overview​

A virtual sender is a set of rules for real senders and a powerful tool for fine messaging tuning.

Your delivery rate can greatly depend on it — especially with large amounts of messages to be sent.

These rules specify real sender usage proportions and custom From and Reply-to email fields for messages sent.

note

Virtual senders can be created and managed only by a master user or an Altcraft platform administrator.

If you need to manage the virtual senders of your account, in the main menu, select Settings —> Virtual senders. Click + New to add a sender.

You can enable virtual senders for mailings if Smart settings are available for your account. If Smart settings are not available, the first valid virtual sender will be used.

General settings​

First of all, you need to enter a unique name for each sender:

You can set groups in the bottom of the page. These groups will get access to the virtual sender.

Sending rules for different communication channels​

Rules for email senders

The rules for email senders determine which real senders and in what proportions will be used under certain conditions. To add a rule, click + Add Rule.

Select the appropriate condition from the drop-down menu When the rule is applied:

  • Match by group — the rule will be applied to mailings within a group specified for matching.

  • Match by "From domain" — the rule is applied when sending from a specific domain.

  • Match by "To domain" — the rule is applied when sending to specific email domains.

  • Match by "From email" — the rule is applied when sending from a specific email address.

  • Default (match all) — no conditions are required for this rule to be activated. It will be applied by default whenever a current virtual sender is set for a mailing.

You can create multiple rules and sender options. The priority of applying rules is set by their position on the page: from top to bottom. The Default rule (match all) must be the last one in the list. The priority of other rules is set using the Move Up and Move Down buttons.

caution

The Default rule (match all) is not possible to delete or move up in priority, since it handles all cases that do not fall under the other rules.

Using the Add sender and Remove rule buttons, you can add and remove senders within the sending rule. The following fields are configured for each sender:

  • Selected sender — select a real sender for sending.

  • Percent — set for the sender the percentage of messages sent within the rule.

  • Override "From Email" — override the "From email value" for outgoing messages.

  • Override "Reply-to Email" — override the "Reply-to email" value for outgoing messages.

note

For one rule the sum of senders usage percent must be 100.

Rules for SMS senders

The rules for SMS senders determine which real senders and in what proportions will be used under certain conditions. To add a rule, click + Add Rule.

Select the appropriate condition from the dropdown menu with rules:

  • Match by group — the rule will be applied to mailings within a group specified for matching.

  • Default (match all) — no conditions are required for this rule to be activated. It will be applied by default whenever a current virtual sender is set for a mailing.

You can create multiple rules and sender options. The priority of applying rules is set by their position on the page: from top to bottom. The Default rule (match all) must be the last one in the list. The priority of other rules is set using the Move Up and Move Down buttons.

caution

The Default rule (match all) is not possible to delete or move up in priority, since it handles all cases that do not fall under the other rules.

Using the Add sender and Remove rule buttons, you can add and remove senders within the sending rule. The following fields are configured for each sender:

  • Selected sender — select a real sender for sending.

  • Percent — set for the sender the percentage of messages sent within the rule.

  • Override "From name" — override the "Caller_ID" value for outgoing messages.

note

For one rule the sum of senders usage percent must be 100.

Rules for push senders

The rules for SMS senders determine which real senders and in what proportions will be used under certain conditions. To add a rule, click + Add Rule.

Select the appropriate condition from the dropdown menu with rules:

  • Match by group — the rule will be applied to mailings within a group specified for matching.

  • Default (match all) — no conditions are required for this rule to be activated. It will be applied by default whenever a current virtual sender is set for a mailing.

You can create multiple rules and sender options. The priority of applying rules is set by their position on the page: from top to bottom. The Default rule (match all) must be the last one in the list. The priority of other rules is set using the Move Up and Move Down buttons.

caution

The Default rule (match all) is not possible to delete or move up in priority, since it handles all cases that do not fall under the other rules.

Using the Add sender and Remove rule buttons, you can add and remove senders within the sending rule. The following fields are configured for each sender:

  • Selected sender — select a real sender for sending.

  • Percent — set for the sender the percentage of messages sent within the rule.

  • Override "From name" — override the "From name" value for outgoing messages.

note

For one rule the sum of senders usage percent must be 100.

Last updated on Mar 12, 2026
Previous
Custom links
Next
Sending policies
  • Overview
  • General settings
  • Sending rules for different communication channels
© 2015 - 2026 Altcraft, LLC. All rights reserved.