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
  • Loyalty programs
  • Loyalty integration with external systems

Integrating loyalty programs with an external order system

A loyalty program in Altcraft Platform can be used in two ways, depending on whether product and order data is transferred to the platform via the Market module.

Market allows you to transfer product and order data to the platform and use it in customer communications. Data can be transferred automatically — via API or product feed, or manually — by uploading a file.

The availability of data in Market determines which loyalty mechanisms are available to you:

  • Without Market, you cannot automatically calculate discounts, accrue or redeem points during checkout. Point accrual and redemption operations are only available through trigger promotions and the Loyalty API.
  • With Market, in addition to basic operations via trigger promotions, discount and points promotions become available. These allow you to automatically accrue and redeem points during checkout, apply discounts, and calculate all applied benefits according to the configured arbitration. The partner products functionality also becomes available — for individual products, you can configure special terms, such as increased cashback or an exclusive discount for program participants. Partner products are taken into account when calculating an order via preorder/preorder_commit just like regular promotions.

Loyalty with Market integration​

This option is suitable for automatically accruing and redeeming points during checkout, as well as applying discounts through points and discount promotions. To make this work, you need to:

  • Upload product data to Market. Data can be uploaded via API, product feed, or from a file.
  • Create discount and points promotions — these will be automatically applied when calculating an order.

Order processing with calculation of applied benefits occurs through a two-stage API:

  • At the first stage, the preorder method is called — it performs a preliminary calculation when the customer is building a cart. The request includes the order composition and participant data (email, phone, profile_id). The platform returns the final price with discounts, the amount of points accrued and redeemed, and a list of triggered promotions. The order is not created at this stage — it's just a calculation.
  • At the second stage, after the order is placed or confirmed, the preorder_commit method is called. The platform creates the order, credits points to the participant's account, deducts used points, and records all applied promotions.
Please note

Automatic point accrual and redemption during checkout works only when using the two-stage API (preorder — preorder_commit).

If an order is created in any other way (for example, via import, direct addition in the interface, or custom logic), the loyalty mechanisms do not trigger. In such cases, point management must be implemented separately — through scenarios with trigger promotions or direct calls to the accrual and redemption API.

Loyalty without Market integration​

In this scenario, points are accrued and redeemed for user actions: filling out forms, installing apps, achievements. Discount and points promotions and related functions (testing, benefit application calculation within arbitration) are unavailable.

Point management is based on using trigger promotions — they set the rules for accrual and redemption but are not tied to orders. The moment a promotion is executed is determined either in automation scenarios (via the "Loyalty points management" node) or through direct calls to the Loyalty API (accrual, redemption, member registration). The preorder and preorder_commit methods are not used in this scenario — they are only available when working with Market.

Examples of implementing this approach — accruing points for app installation, form submission, and notifying about point expiration — can be found in the article Basic loyalty program use cases.

Last updated on Mar 12, 2026
Previous
Loyalty programs
Next
Быстрый старт
  • Loyalty with Market integration
  • Loyalty without Market integration
© 2015 - 2026 Altcraft, LLC. All rights reserved.