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 glossaryPlatform limits
      Profiles and databasesarrow
    • Subscription resourcesManaging databasesSubscriber profileProfiles import and data updateCommon Errors When Importing ProfilesScheduled customer data importManaging Data TablesAutomatic 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 practices
          First mailingarrow
        • Quick StartEmail
        Email: sending domain configurationEmail: setting up and using postmastersHow email tracking works
        Push Channelarrow
        • Mobile Pusharrow
        • First Mobile Push Mailing
            Mobile Push Providersarrow
          • Firebase Cloud MessagingApple Push Notification ServiceHuawei Mobile ServicesRuStoreYandex.AppMetrica
          Integrate your app with Altcraft
            Deprecated: Manual Push Setuparrow
          • Deprecated: Setup and ConnectionProcessing and adding a subscriptionEvent registrationProviders: push message structure
          Web Pusharrow
        • First Web Push MailingResource and Website Setup
            Web Push Providersarrow
          • Firebase Cloud messagingApple SafariMozilla Services
          Transferring Data to the PlatformWeb Push SDK MethodsPWA and Push Notifications
            Migration and Subscription Transferarrow
          • Migrating push subscriptions from third-party servicesHow to transfer push subscriptions configured for Safari?Migration from OneSignal
        Push token deactivation
        SMS channelarrow
      • SMS
        In-Apparrow
      • First In-App PlacementSDK Setup and Integration
      WhatsAppViber*™
        Telegramarrow
      • Telegram BotTelegram Group
        Maxarrow
      • MAX BotMAX Group
      NotifyCommunication Channels WorkflowРуководство: SMS-рассылка через VK NotifyРуководство: SMS-рассылка через УТШРуководство: push-рассылка через сервис от "Согласие"
      Segmentationarrow
    • Static SegmentsDynamic SegmentsUpdatable Segments
        Segmentation Conditionsarrow
      • Segmentation by Profile dataSegmentation by Interactions with EntitiesSegmentation by Activity of the channel
          Segmentation by external dataarrow
        • Segmentation by external dataSegmentation by external SQL tablesRecommendations for segmentation by external data
        Segmentation 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 templateTemplate for In-AppMAX templateTelegram templateWhatsApp templateViber templateNotify template
        Visual editor for email-templatearrow
      • Visual editor interfaceAdding blocksElements and their settingsCustom blocksElement stylesLayer 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
    • Broadcast mailingsTrigger mailingRegular mailingMultivariate testingMailing testingMailing schedulePlacementsMailings calendarMailing log — errors and troubleshootingManaging the Sender Queue
      Automation scenariosarrow
    • Managing scenariosScenario NodesClassic marketing scenariosStep-by-step welcome scenario guideScenario for automatic notification of the managerAbandoned cart scenarioCycle Handling in Automation ScenariosHigh-priority scenarios
      Campaignsarrow
    • Working with CampaignsLocal control groups (LCG)Stratification violation error when limit is reachedAudience expansion in campaignsAudience building
      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 systemsCreating a loyalty program from scratchBasic 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
      Weblayersarrow
      • Formsarrow
        • Create a formarrow
        • General settingsForm customization with custom codeForm constructorAppearanceActions and form publicationConditional logic in forms and surveys
        Data analyticsBinding data channel and formsNPS 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 typesVariable typesLinking a pixel and the Tag manager
      Settingsarrow
    • Account settingsCustom linksVirtual sendersSending policiesAudit journalTags FAQ
        Connectionsarrow
      • Connection to Facebook AdsConnection to Google AdsConnecting to Yandex.Audience™Connection to 360dialogConnection to EdnaConnection to Devino TelecomConnection to SMSTrafficConnection to VK Ads™Connection to MTS OmniChannelConnection via OAuth 2.0Basic Authentication connectionToken Authentication connectionCustom Authentication ConnectionConnecting to MAXConnection to NotifyConnection to Rapporto
        Users, groups and accessarrow
      • Password and login securityTwo-Factor Authentication (2FA)
      Attribute settings
      Integrationsarrow
    • Facebook Ads Manager
        Yandexarrow
      • Yandex AppMetricaYandex.Audience™
      Google Ads AudiencesWhatsAppStatic segment synchronizationViberVK AdsNotifyMAX
        Action hooksarrow
      • Lpgenerator™Tilda™Altcraft Action HooksAction hooks event typesEvent Capture Message StructuresJSON 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 up a trigger mailingEvent registrationGoogle Sheets and Altcraft integration AmoCRM and Altcraft integration
        Additional Informationarrow
      • Integration scopeData Transmitted During Synchronization
      API requests: where to startarrow
    • Import or update a profileTrigger mailing launchEngage profile in scenario
      Changelogarrow
    • v2026.3.79v2026.3.78v2026.2.77v2026.1.76v2025.4.75v2025.4.74v2025.3.73v2025.2.72v2025.1.71v2024.4.70v2024.3.69v2024.2.68.2v2024.1.68
    Documentation archiveEmail Marketer's Library
  • Mailings
  • Placements

Placements

Placements are a tool for placing content for subscribers on a specific resource with the ability to cancel later. When launched, it sends content to each subscriber in the data source (in the case of a scheduled start) or to a specific lead who initiated a certain event (in the case of a trigger start condition). If the channel supports mailing cancellation, the placed content can be removed from the resource manually or upon reaching a specific date and time.

To create a new mailing, select Mailings → Placements in the main menu and click the+ Create button.

General Settings​

In the general settings, specify the name and description of the new mailing. If needed, set an access group, tags, and attributes for additional grouping. In the upper right corner is a toggle that activates the mailing:

Channel​

Select the sending channel for which this mailing type is available from the drop-down menu.

Subscribers​

Select the recipients of the mailing. Mailings in Altcraft are sent within a specific resource: this can be a separate website, product, promotion, or another direction of your communications with customers. Select a resource and a subscriber source. Placement recipients can be a profile database or a segment consisting of profiles from one or more databases.

If you are using a placement to send messages through a custom channel, the mailing settings may vary depending on the channel configuration. For example, some channels may require selecting only the resource without specifying the subscriber source:

tip

When sending messages, the mailing uses client subscriptions to the selected resource. Make sure the recipients in your data source are subscribed to it!

Templates​

At this step, select the content you want to use in the placement.

Click the Add Content button and select a prepared template. Any mailing type supports up to 8 message templates. The mailing will send each recipient one message from the selected ones at random — in equal proportions.

Clicking on a template thumbnail opens a message preview.

Placement​

Setting Up Start and Stop​

A placement can be launched in two ways:

  • on a specific date and time for all subscribers in the source
  • by event for one subscriber

Start at a Specific Date and Time​

The mailing will run once at the specified time. After that, the mailing will not be available for restart.

Start by Event​

The setup is similar to a triggered mailing. Content will be sent to each subscriber captured by the trigger:

Direct Communication and Trigger-Based Placement Launch

Event-based launch is available only for placements in direct channels. Telegram Group and MAX Group are indirect channels, so trigger-based launch is not available for them.

For more information on the differences between direct and indirect channels, see here.

Cancellation of Placement​

Placement cancellation is only available for channels where it is configured. If mailing cancellation was not provided by the administrator when configuring the channel, this option will not be available for editing in the mailing.

There are two types of cancellation:

  • on a specific date and time
  • manually

Both options will cancel placements for all subscribers to whom the content was sent. It does not depend on the start type. If the start was set to a trigger, the trigger will be deactivated before cancellation.

A placement mailing can be canceled manually only if its status is "Deployed".

Instant Mailing Launch (in Addition to Schedule)​

To launch the mailing immediately after creation, enable the corresponding option at the bottom of the page:

Smart Settings​

The Smart Settings block combines the following additional mailing settings:

  • Virtual sender — lets you select a virtual sender for the mailing (a set of rules for sending messages from the platform's real senders).
  • Custom tracking domains — tracks message interactions using additional tracking servers. Specify each domain on a separate line.
  • BCC email list — BCC recipients for outgoing messages. Specify each address on a separate line.
  • Do not check contact data for uniqueness — disables uniqueness validation of mailing recipients based on subscription data.
caution

If you are unsure which settings to select, consult with the platform administrator in your organization or with Altcraft support specialists.

Mailing Watchers​

Additionally, you can set mailing watchers in Smart Settings. Watchers receive the same messages as mailing recipients. To do this, you need a watchers database. It is created the same way as a regular database, but you must enable the corresponding option in General Settings.

In Smart Settings, select the Watchers DB and set the message sending limit for each mailing launch:

In-App Placement​

Prerequisites

To communicate via In-App, you need to perform the following actions in advance:

  • Create a resource with the In-App channel activated.

  • Make sure the application is integrated with Altcraft mSDK and profiles are subscribed to In-App.

  • Create an In-App template.

In-App content is only launched through placements. The creation and setup process differs slightly from setting up placements in Telegram and MAX.

To create an In-App placement, go to Mailings — Placements. Select the In-App channel:

Selecting the In-App channel

Fill in the basic information: placement name and description, subscription resource, recipient audience, application versions, as well as screens on which the content will be displayed:

Basic placement information

Select the template created in the previous step and click Next:

Template selection

You can select up to 8 templates. If multiple templates are selected, recipients will be divided in equal proportions and receive a random message.

For example, if you add 4 templates to the placement, 25% of the audience will see the first template, another 25% will see the second, the next 25% will see the third template, and the remaining 25% will receive the fourth template. These groups are formed randomly among the entire audience.

Configure the display conditions:

  • Trigger event — the action after which the user will be shown the In-App. This can be application start, transition to a screen specified in the resource, or a user action from the application.

  • Display the message immediately or after X seconds after the trigger fires

  • Schedule availability — the placement can be available continuously, on specific dates and times, or with a specified frequency

  • Display frequency — whether there is a limit on the number of displays within a certain period. To set a limit, you need to create a sending policy.

  • Placement priority — determines which In-App message will be displayed if multiple placements are sent to the same screen simultaneously. The lower the value, the higher the priority. A value of 0 corresponds to the highest priority.

  • Display limit — a limit on the number of In-App displays for one user.

Display conditions

After configuring the placement, click Create. After creating the placement, you will be taken to the management screen:

Placement management

To activate the placement, click the start button and specify the start date and end date:

Start and end dates

If you activated the placement immediately, the status will change to Sending:

Status — sending

If you selected a future date, the mailing will have the status Scheduled. You can launch it right now by clicking the corresponding button :

Status — scheduled
info

For more information on In-App channel setup, see the "First In-App Placement" article.

Last updated on Sep 28, 2026
Previous
Mailing schedule
Next
Mailings calendar
  • General Settings
    • Channel
    • Subscribers
    • Templates
    • Placement
      • Setting Up Start and Stop
      • Start at a Specific Date and Time
      • Start by Event
      • Cancellation of Placement
      • Instant Mailing Launch (in Addition to Schedule)
  • Smart Settings
    • Mailing Watchers
  • In-App Placement
© 2015 - 2026 Altcraft, LLC. All rights reserved.