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
  • Yandex AppMetrica™

Yandex AppMetrica™

Description​

Yandex AppMetrica™ is an analytics platform for mobile applications. It also manages mobile push notifications using Google Firebase SDK.

Web-site: AppMetrica: https://appmetrica.yandex.ru

Altcraft MP captures AppMetrica™ installations and events information from Logs API, that can be used for:

  • goals and their values registration

  • profiles import and update

To start using AppMetrica data in Altcraft, go to Integrations in the main menu.

Accessing AppMetrica API​

Create a new integration. In General settings give it a custom Name and select AppMetrica events from Integration source dropdown. You can activate or stop the integration by a special button in this section:

In Integration settings enter your application AppMetrica credentials:

  • Application ID — unique application ID in AppMetrica.

  • AppMetrica API token — data access token. You can retrieve it in AppMetrica application settings.

After that you can add hooks for 2 types of AppMetrica™ events:

  • Events — captures all events in installed applications.

  • Installations — captures new installations of your application.

You can filter events to be captured by adding rules based on system or custom event data. In filters, you can use a search template * (wildcard). For instance, *@gmail.com will capture all profiles with a google mailbox:

Yandex AppMetrica data​

Integration supports all data fields from AppMetrica Logs API. Field structure is available in AppMetrica documentation:

  • Events — https://appmetrica.yandex.ru/docs/mobile-api/logs/ref/events.html
  • Installations — https://appmetrica.yandex.ru/docs/mobile-api/logs/ref/installations.html
info

Business data can be retrieved from your Application in the event_json parameter in AppMetrica. To use custom data in Altcraft integration enter the FieldName manually, providing path to the data you need. For example:

  • event_json.email - if your customer's email is sent to AppMetrica as a root property in "event_json":

    "event_json" :
    {"email" : "example@example.com"}
  • event_json.contacts.email - if the email is a part of "contacts" object:

    "event_json" :
    {"contacts":
    {"email" : "example@example.com",
    "phone" : "+12345678910"}
    }

When using AppMetrica user interface you can configure up to 5 levels of event_json object nesting, when using AppMetrica API- 10. Altcraft supports the maximum value you set.

Custom event data in AppMetrica documentation: https://appmetrica.yandex.ru/docs/mobile-events/concepts/events.html

Goal registration​

An event, captured by AppMetrica can record a goal and its value.

Goals are organized by Altcraft Pixels. Recording the same goals for different pixels will allow you to compare two or more UI variants or customer stories. Select the pixel you need from a dropdown.

Both goal and value data can be taken from AppMetrica data or entered manually.

  • Custom goals and values are static and recorded as is at the moment the event is captured.

  • AppMetrica data is dynamically changed from profile to profile.

Each goal can be recorded to a known and existing customer profile or to an anonymous profile (by Cookie data)/

  • Anonymous goals are used in goals reports to measure common effectiveness.
  • Profile goals and values can be used in reports, for RFM and LTV segmentation and scoring. Goals reaching is recorded in profile action history.

To record the goal for a specific profile, activate option Attach profile, select a database and a matching mode to search the profile:

  • By email from profile — email field from main profile data.

  • By email, from profile or subscriptions — main profile email or any email from profile subscriptions.

  • By AppMetrica ID — appmetrica_device_id property. When profiles are imported from AppMerica, this data is recorded automatically. For other imports — add this field manually to search profiles.

  • By custom field — by a value of database custom field. Select the field from a dropdown and specify the corresponding property in AppMetrica data.

Profile import​

The second feature of AppMetrica integration - allows to import and update Altcraft customer profiles. Select the corresponding Action type in Main settings. There are 3 import modes:

  • Add new leads and update existing ones
  • Add new leads, do not update existing ones
  • Update only

Profile matching​

Select a database and a matching mode to search the profile. If a record is found - the profile will be updated, if not - a new customer record will be created.

  • By email from profile — email field from main profile data.

  • By email, from profile or subscriptions — main profile email or any email from profile subscriptions.

  • By AppMetrica ID — appmetrica_device_id property. When profiles are imported from AppMerica, this data is recorded automatically. For other imports - add this field manually to search profiles.

  • By custom field — by a value of database custom field. Select the field from a dropdown and specify the corresponding property in AppMetrica data.

caution

By AppMetrica ID is recommended if you have customers with multiple devices running your app. Do not use it along with email matching modes if you want no duplicated client profiles!

Auto-subscription​

While importing or updating customer profiles you can automatically subscribe them to Email, SMS or Push. Before you start make sure:

  1. You have at least one resource with a communication channel configured.
  2. Database you selected is added to the resources you subscribe profiles to.

After these prerequisites are made, Add subscription button will be available in the integration form**:**

For every subscription record specify subscription source — this can be any of AppMetrica data fields, most commonly data from event_json. AppMetrica Push subscriptions use standard data fields:

Push providerEvent field
Yandex AppMetrica with device idappmetrica_device_id
Yandex AppMetrica with iOS IFAios_ifa
Yandex AppMetrica with Google AIDgoogle_aid

For other communication channels, you would like to send contact data as custom information. Custom event data in AppMetrica documentation: https://appmetrica.yandex.ru/docs/mobile-events/concepts/events.html

You can also set the status for every subscription you add or modify:

  • When importing new profiles using Double Opt-in, set status Unconfirmed
  • When updating profile details you can change status based on customer actions. For example, if a customer wants to Suspend a subscription or Unsubscribe.

Column mapping​

For any new profile, a unique ID will be assigned. If matching is set to a custom valueand a value is not found - it will be recorded for a new profile. If email is used for matching - appmetrica_device_id will be nevertheless recorded as a system parameter.

Set column mapping for Altcraft database default and custom fields based on AppMetrica events data. Custom AppMetrica data is provided within event_json object.

caution

Ignore empty option will skip empty values, importing profiles with missing data. If the field is mandatory for import (email for default) and this option is not enabled - an import error will occur.

Last updated on Feb 3, 2022
Previous
Static segment synchronization
Next
Tilda™
  • Description
  • Accessing AppMetrica API
    • Yandex AppMetrica data
  • Goal registration
  • Profile import
    • Profile matching
    • Auto-subscription
    • Column mapping
© 2015 - 2026 Altcraft, LLC. All rights reserved.