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
  • Getting Started

Getting Started

Altcraft Platform is an omnichannel CDP platform designed for storing customer data and managing communications across multiple channels such as email, SMS, push notifications, messengers, and more.

The platform includes a wide range of features and tools, so during the first login it may not be immediately clear where to start and how different interface modules are connected. This article helps you understand the core logic of Altcraft Platform and points you to the documentation sections worth exploring next.

If you are just starting to work with the platform, we also recommend reviewing the FAQ and Glossary sections.

If you prefer learning through practical examples, this article also includes videos demonstrating basic operations: preparing a profile database and launching the first email mailing.

Profile Databases and Subscriber Profile​

Altcraft Platform is built around data. All communications, automation, and analytics are based on customer profiles and their actions. All customer data in Altcraft is stored in profile databases.

A profile database defines the data structure: which fields are used, what data types are allowed, and which resources (subscription sources) can be associated with profiles. In most cases, a single profile database corresponds to a specific product, service, or business unit. More details on data structure configuration are available in this article.

A subscriber profile is a unified digital customer profile. It combines contact details, personal information, action history, channel subscriptions, and participation in marketing activities. In the documentation, you may encounter the terms "customer", "subscriber", or "user", but in all cases they refer to the same object — the subscriber profile.

For example, a profile may initially contain only an email address, later include an SMS subscription, and then record activity from a mobile application. All this information is stored within a single subscriber profile.

A detailed description of the profile structure and its tabs is available in this article.

Resources and Subscriptions​

Altcraft uses subscription resources to manage communications.

A resource is a logical content source within which a customer receives messages. It can be viewed as a context or interaction point: a website, mobile application, service, brand, or a specific company project.

Resources allow you to separate customer subscriptions and consents. The same profile can be subscribed to multiple resources and have different subscription statuses in each of them.

A profile subscription links a customer to a specific resource and communication channel. It is the subscription that determines whether messages can be sent to particular contact details.

More information about configuring resources and subscriptions is available in this article.

How profile databases, resources, and subscriptions are created​

Below is a basic process of preparing data for communications: creating a profile database, creating a resource, and adding profiles with subscriptions. These steps form the foundation for further segmentation, mailings, and automation scenarios.

Data and Action History​

Altcraft Platform tracks all key customer actions and stores them in the subscriber profile history. This includes message sends and opens, link clicks, form submissions, website or app events, as well as order and promo code data.

Action history is used for segmentation, automation, and analytics. For example, you can send a message only to customers who opened emails in the last seven days or made a purchase.

Audience Segmentation​

Segmentation allows you to group profiles based on defined conditions.

Altcraft supports static, dynamic, and updatable segments. These segment types differ in how the audience is formed and how data is refreshed.

Static segments are used for working with fixed lists of profiles. Dynamic segments are recalculated at the time of message sending and always use up-to-date data. Updatable segments are recalculated on a defined schedule and store the result until the next update.

For example, you can create a segment of customers who placed an order in the last week or a segment of active subscribers who opened emails during the last month.

More details about segment types and selection conditions are available in this article.

Communications​

Communications in Altcraft Platform refer to sending messages to subscriber profiles through various communication channels. The platform supports email, SMS, Web Push, Mobile Push, messengers, and other channels that can be used individually or as part of omnichannel scenarios.

Each channel has its own configuration and delivery specifics, but the overall communication logic in the platform is unified. Messages are sent based on profile data and always take into account contact details, subscriptions, and consents.

Altcraft supports several main types of mailings. Broadcast mailings are used for one-time sends, such as news or promotions. Regular mailings are suitable for repeated communications based on a schedule. Trigger mailings automatically send messages in response to customer actions or specific events.

Communications can be launched for the entire profile database or for selected audience segments. Mailings are often part of more complex processes — automation scenarios or campaigns.

How to launch the first email mailing​

info

To send email messages, a configured "DKIM" is required for the sender domain. It is not issued automatically. Please contact technical support via chat to set it up.

Below is an example of the full process of creating an email mailing: from preparing a template to launching the send. The video shows how working with profiles, subscriptions, and templates comes together in a real communication process.

Notice:

In the interface shown in the video, the term "campaign" may be used to refer to a mailing.
In the current version of the platform, the terminology has changed:

Mailings are a separate tool for sending messages (Broadcast, Regular, Triggered).

Campaigns are a different tool designed for building complex marketing processes and combining communications, scenarios, and customer interaction logic.

For your first hands-on experience with message sending, we recommend starting with step-by-step channel guides, for example Your First Email mailing. A full list of tutorials is available in the mailing Creation from Scratch section.

Automation Scenarios​

Automation scenarios allow you to build communication flows based on customer actions, events, and conditions.

Scenarios are used for onboarding, welcome journeys, reactivation, reminders, and other common marketing use cases. Profiles can enter scenarios either from segments or directly from the database if they meet the entry conditions.

An overview of the automation tool is available in the Automation Scenarios section, and examples of common scenarios can be found in Classic Marketing Automation Scenarios.

Other Platform Capabilities​

Altcraft Platform is not limited to data storage, segmentation, and communications. The platform includes additional modules that support comprehensive customer lifecycle management.

Marketing activities can be managed using mailings. Learn more in the mailings section.

Working with product and order data is described in the Market section.

The loyalty module allows you to create reward programs and use promo codes. More details are available in the Loyalty section.

The web layer is used for data collection and subscription management. Learn more in the Web Layer section.

Analytics is covered in the Reports and Analytics section.

Integrations are described in the Integrations section, and technical capabilities are covered in the Developer Documentation and API: Getting Started.

Last updated on May 4, 2026
Previous
User documentation
Next
FAQ
  • Profile Databases and Subscriber Profile
  • Resources and Subscriptions
    • How profile databases, resources, and subscriptions are created
  • Data and Action History
  • Audience Segmentation
  • Communications
    • How to launch the first email mailing
  • Automation Scenarios
  • Other Platform Capabilities
© 2015 - 2026 Altcraft, LLC. All rights reserved.