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
  • Integrations
  • Tilda™

Tilda™

Tilda profile import integration​

In Altcraft Platform, you can transfer the data of a user who filled out a form on your website designed on Tilda. To do this, you need to use the Webhooks tool. You can read more about Tilda Webhooks in this article.

note

Please note that integration with Tilda allows you to integrate only user subscriptions to email and SMS resources.

For this integration you will need the following data.

  • Altcraft service instance URL. For example, https://ru.altcraft.com.
  • API token: tokens are created by platform master users.
  • Database ID and Resource ID. If there is no need to subscribe to a resource, you need only the database ID.

Step 1: Create a Tilda webhook​

Go to the section: Dashboard —> Your project —> Site settings —> Forms. At the very bottom you will find Other —> Webhook.

Fill in the WEBHOOK URL field as follows:

<your.domain>/api/integrations/tilda/profile_import/?token=<api_token>

Here you need to replace <your.domain> with the URL of the Altcraft platform service instance and <api_token> with the token provided to you:

Click "Add". After that, you will be prompted to assign this data collection service to all forms on the website. Skip this step by clicking the "Close" button. So, Webhook is created.

Step 2. Set up a Tilda form​

Open the site page editing window and find the form from which you want to transfer data to Altcraft. Then open the "Content" tab:

Find the "FORM DATA RECEIVER" section and enable your Webhook:

There are two types of form in Tilda:

  • a simple form with a button,
  • form with multiple fields.

The settings for each of them are slightly different.

Forms with one input​

For a single input field form you will need block "Options" to set variable names.

FieldDescription
Variable nameIf you want this field to get into Altcraft, then its name must correspond to the same field in the database. The variable name must be email or phone.

The name is not case sensitive, for example, if the Altcraft database has an "email" field, and Tilda's field is called "EMAIL", the data from the form will be submitted successfully.
Variable name for a hidden fieldName it to_ids
Variable value for a hidden fieldEnter a colon-separated database ID and resource ID. If you do not need to subscribe to the resource, then you need only the database ID. In the screenshot below, in the example, 4 is the database ID, 19 is the resource ID.

Form with several inputs​

If you are working with a form that contains multiple fields, you need to open the "Content" tab. There, expand the "INPUT FIELDS" tab.

Pay attention to the names of all the variables that the form contains. If you want a field to get into Altcraft, its name must correspond to the same field in the database.

The contact data fields should be named email or phones.The variable name is case insensitive, e.g. EMAIL will also work.

After setting up the visible form fields, add another field. Type is hidden. Name it to_ids . Enter a colon-separated database ID and resource ID. If you do not want to subscribe to the resource, enter only the database ID.

In the example in the screenshot below, 7 is the database identifier, 17 is the resource identifier.

Integration with Tilda allows not only importing new profiles into Altcraft databases, but also immediately start a trigger event. For example, you can run a trigger mailing right after importing a new profile to send them a welcome email, or add the profile to a welcome scenario.

To do this, you need to add additional hidden fields in the form:

Action after importVariable nameValue
Launch a trigger mailingtrigger_idTrigger mailing ID
Add a profile to a scenarioworkflow_idScenario ID

Passing a subscription status​

When you import a profile from a multi-field form, you can pass a specific subscription status to the resource. It is this status that will be displayed in the digital profile of the subscriber in Altcraft Platform.

To pass profile status, you need to add one more hidden field in your form settings. You must specify status_sub as the variable name, and choose one of the statuses reserved by Altcraft Platform as the value.

Available statuses:

StatusStatus_sub value
Subscribed0
Unsubscribed1
Complaint2
Hardbounced3
Unconfirmed4
Suspended5
Invalid6

Step 3. Test a form​

After you set up the fields for the form, publish the page. Then test the page by submitting test data to the form.

tip

Tilda won't update the form right away, so it's best to test it a couple of minutes after posting.

Next, open Your project —> Leads.

The screenshot shows an example of a successfully sent application. If you see an error, you need to check the following points:

  • The URL in the Webhook is correct and contains the correct API Key
  • The database exists and it is selected in the resource you are using to subscribe.

  • The form has an email or phone field

Extra options​

You can set different variable parameters as hidden form fields:

  • Profile matching mode by any of available. Default matching is Email.
  • You can use db_id and resource_id instead of to_ids variable
  • You can set a custom value for _vendor variable. By default it will send form ID.
  • When updating a profile field with the "tags" type in the database, the field is completely overwritten. To add new values to existing ones, add the -add to the variable name when setting up a field in Tilda. For example, to update a tag_field, use the variable name tag_field-add.

Last updated on Mar 12, 2026
Previous
Yandex AppMetrica™
Next
Lpgenerator™
  • Tilda profile import integration
  • Step 1: Create a Tilda webhook
  • Step 2. Set up a Tilda form
    • Forms with one input
    • Form with several inputs
  • Passing a subscription status
  • Step 3. Test a form
  • Extra options
© 2015 - 2026 Altcraft, LLC. All rights reserved.