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
  • Message templates
  • Importing a template from a third-party service

Importing a template from a third-party service

Description​

If you have ready-made message templates in other services, you can move them to Altcraft Platform. You can import both Email and SMS templates.

tip

Import is available for the following services:

  • Unisender
  • Mailchimp
  • Sendsay

To get started, go to the "Templates" section and click the "Create" button on the top panel. Next, select the creation method: import the template from a file or insert the code.

Import from file​

If you want to move an Email template to the platform, you must first export the html file with the ready-made template from a third-party service. To move an SMS template, you need a file in txt format.

In the platform, click on the upload area and select the file on your device. After uploading, you will see a table with notes on importing. All variables removed from the template will be listed here.

tip

Each service uses its own variables in message templates. In our platform, they look like this {lead.email}.
When importing a template from a third party service, Altcraft will automatically replace some variables. If there is no similar variable in the platform, it will be removed from the template.
See below for information on which variables will be saved.

Insert code​

When you create a template by inserting a code, the first thing you will be asked is to select a channel (Email or SMS).

If you choose Email, you will need to copy the template html code from the editor in a third party service. Next, paste the copied code to the "Email" text box. The text version of the letter will be generated automatically.

If necessary, you can manually add code for each version of the email:

  • Email — html version of email.
  • Text — text version of email.
  • AMP — amp version of email.

Importing a template for an SMS channel is easier. You only need to fill in one text box.

After pasting the code, run its verification by clicking the "Check and prepare" button. The import notes table will also appear at the bottom, listing all the removed variables. Click "Import".

Auto-replacement of variables in a template​

Altcraft Platform automatically replaces third-party service variables with its own variables:

Unisender​

Variable descriptionAltcraftUnisender
First name{lead._fname}{{Name}},

{{_LocalPart}},

{{LocalPart}}
Subscription email address{subscription.email}{{_Email}},

{{Email}}
Subscription phone{subscription.phone}{{_Phone}}
Email sender name{from_name}{{_ListTitle}},

{{ListTitle}}
Custom profile field{lead.custom_field}{{custom_field}}
Confirmation link<a href="#" title="Confirm your subscription" confirm-link name="link1">Confirm your subscription</a>

When importing the text version of the email, the confirmation link is replaced like this: [Confirm your subscription](# <confirm-link>). You need to replace # with the URL.
{{ConfirmUrl}}
Resource unsubscribe or global unsubscribe link{unsubscribe}{{_UnsubscribeUrl}},

{{UnsubscribeUrl}}
Link to the email web version{webversion}{{_WebLetterUrl}},

{{WebLetterUrl}}
Full date{datenow}{{SendDate}}

Sendsay​

Variable descriptionAltcraftSendsay
First name{lead._fname}[% anketa.base.firstName %]
Last name{lead._lname}[% anketa.base.lastName %]
Subscription email address{subscription.email}[% anketa.base.email %]
Email subscription domain{subscription.email_domain}[% anketa.member["confirm.host"] %]
Gender{lead._sex}[% anketa.base.gender %]
City{lead._city}[% anketa.base.city %]
Date of birth
{lead._bdate}[% anketa.base.birthDate %]
Custom profile field{lead.custom_field}[% anketa.base.custom_field %]
Condition{if lead.custom_field}{else}{end}[% IF anketa.base.custom_field %][% ELSE %][% END %]
Variable length{length(lead.custom_field)}[% size(anketa.base.custom_field) %]
Array iteration
{for $index $i = items}
   {$i}
{end}

[% FOREACH i IN items %]
   [% i %]
[% END %]

Mailchimp​

Variable descriptionAltcraftMailchimp
First name{lead._fname}*|FNAME|*
Last name{lead._lname}*|LNAME|*
Subscription email address{subscription.email}*|EMAIL|*
Subscription phone{subscription.phone}*|PHONE|*
Registration date{lead._regdate}*|OPTIN_DATE|*,

*|OPTIN_DATETIME|*
Email sender name{from_name}*|LIST:DESCRIPTION|*,

*|LIST:NAME|*
Sender's email{from_email}*|LIST:EMAIL|*,

*|ABUSE_EMAIL|*
Custom profile field{lead.custom_field}*|custom_field|*
Confirmation link<a href="#" title="Confirm your subscriptionу" confirm-link name="link1">Confirm your subscription</a>

When importing the text version of the email, the confirmation link is replaced like this: [Confirm your subscription](# <confirm-link>). You need to replace # with the URL.
*|LIST:SUBSCRIBE|*
Resource unsubscribe or global unsubscribe link{unsubscribe}*|UNSUB|*,

{{unsub}},

{{unsub "http://example.com/unsub"}}

{{unsub redirect_merge_var}}
Link to the email web version{webversion}*|ARCHIVE|*
Full date{datenow}*|DATE:d/m/y|*

{{date "Y-m-d"}}
Full year{yearlong}*|CURRENT_YEAR|*
Resource ID{resid}*|LIST:UID|*
Mailing SUBID{subid}*|CAMPAIGN_UID|*
URL of a website, form, or application from resource settings{resurl}*|LIST:URL|*
Uppercase{uppercase("your text")}{{upper "your text"}}
Upper case for first character{uppercasefirst("your text is neat")}{{title "your text is neat"}}
Condition{if lead.custom_field}{else}{end}*|IF:custom_field|*...*|ELSE:|*...*|END:IF|*
tip

If you would like to extend the variable substitution syntax, please send a request to support@altcraft.com.

Last updated on Apr 27, 2026
Previous
Importing and exporting a message template
Next
Exporting a template from Pixcraft
  • Description
  • Import from file
  • Insert code
  • Auto-replacement of variables in a template
    • Unisender
    • Sendsay
    • Mailchimp
© 2015 - 2026 Altcraft, LLC. All rights reserved.