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 documentation
    Getting Started
    FAQ
    Altcraft glossary
      Profiles and databasesarrow
    • Subscription resources
      Managing databases
      Subscriber profile
      Profiles import and data update
      Scheduled customer data import
      Automatic data collection
      Bulk customers profiles update
      Double opt-in subscription
      Suppression lists
      Profile relations
      Profile history export
      Profile export
      Creating a static segment based on import results
      How to open a CSV file
      Matching
      Types of fields in the database
      Global control groups
      Subscription Manager
      Communication channelsarrow
      • Email channelarrow
      • Email: ISP interactions best practices
        Email: sending domain configuration
        Email: setting up and using postmasters
        Быстрый старт
        Push channelarrow
        • Mobile Pusharrow
        • Settings & implementation
            Integrate your app with Altcraftarrow
          • Providers: push message structure
            Processing and adding a subscription
            Event registration
          Web pusharrow
        • Preliminary Settings
            Web browser push configurationarrow
          • Firebase Cloud messaging
            Apple Safari
            Mozilla Services
          Connecting Web Push to a Website
          Transferring Data to the Platform
          Web Push SDK Methods
            Import of subscriptions from third-party push servicesarrow
          • Migrating push subscriptions from third-party services
            How to transfer push subscriptions configured for Safari?
            Migration from OneSignal
      SMS channel
        Creating mailing from scratcharrow
      • Email
        SMS
        Web Push
        Mobile Push
        WhatsApp
        Viber*™
        Руководство: SMS-рассылка через VK Notify
        MAX Bot
        MAX Group
        Notify
        Telegram Bot
        Telegram Group
      Communication Channels Workflow
      Руководство: SMS-рассылка через УТШ
      Руководство: push-рассылка через сервис от "Согласие"
      Segmentationarrow
    • Static Segments
      Dynamic Segments
      Updatable Segments
        Segmentation Conditionsarrow
      • Segmentation by Profile data
        Segmentation by Interactions with Entities
        Segmentation by Activity of the channel
        Segmentation by external data
        Segmentation by external SQL tables
        Segmentation 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 editor
        Email-template
        SMS template
        Push template
        MAX template
        Telegram template
        WhatsApp template
        Viber™ template
        Notify template
        Visual editor for email-templatearrow
      • Visual editor interface
        Adding blocks
        Elements and their settings
        Custom blocks
        Style manager
        Layer manager
      Template fragments
      Image gallery
      Content personalization
      Creating tables based on array elements
      Block editor for email template
        Altcraft Variables and Functionsarrow
      • Logical expressions in messages
        Loops in messages
        Market variables in templates
        Using the JSONPath functionality
        Dynamic content in messagesarrow
      • Dynamic HTML content
        Dynamic JSON content
        Content from SQL database in templates
        Dynamic API content
      Importing and exporting a message template
      Importing a template from a third-party service
      Exporting a template from Pixcraft
      Mailingsarrow
    • Mailings calendar
      Broadcast mailings
      Regular mailing
      Trigger mailing
      Multivariate testing
      Mailing testing
      Mailing schedule
      Placement mailing
      Campaignsarrow
    • Working with Campaigns
      Local control groups (LCG)
      Audience expansion
      Audience building
      Automation scenariosarrow
    • Managing scenarios
      Nodes of the scenario
      Classic marketing scenarios
      Step-by-step welcome scenario guide
      Scenario for automatic notification of the manager
      Abandoned cart scenario
      Marketarrow
    • Market settings
        Productsarrow
      • How to create a product manually
        How to import a product from a file
        Scheduled product import
        Product and SKU Segments
        Preparing the YML file
      Orders
      Market variables in message template
      Guide: how to send an order confirmation email
      Loyalty programsarrow
    • Loyalty programs
      Loyalty integration with external systems
      Быстрый старт
      Basic loyalty program use cases
      Order Segments
      Promotion codes
      Reports and analyticsarrow
    • Channel report
      Traffic report
        Summary reportarrow
      • Summary report metrics
      Cohorts report
      Lifetime report
      Funnels report
      Goals report
      Audience growth report
      Click map report
      Loyalty programs report
      Bounces report
      Undeliveries report
      Report on global control groups
      Integrationsarrow
      • Action hooksarrow
      • Altcraft Action Hooks
        Action hooks event types
        Action Hook Message Structure
        JSON batch request (HTTP POST action hook)
        Message to RabbitMQ broker
        Message to RabbitMQ exchanger
        Message to Kafka broker
        Test event
        Integration of third-party services using Albatoarrow
      • Connecting Altcraft to Albato
        Launching the welcome scenario using Albato
        Transmitting event data
        Setting app a trigger mailing
        Event registration
        Google Sheets and Altcraft integration
        AmoCRM and Altcraft integration
      Facebook Ads Manager™
      Google Ads Audiences
      MAX
      Yandex.Audience™
      VK Ads™
      Static segment synchronization
      Yandex AppMetrica™
      Tilda™
      Lpgenerator™
      WhatsApp
      Viber*™ integration
      Integration scope
      Data Transmitted During Synchronization
      Notify
      Weblayersarrow
      • Formsarrow
      • Create a form
        Form constructor
        Appearance
        Actions after form activation
        Data analytics
        Binding data channel and forms
        Conditional logic in forms and surveys
        NPS testing
        Pixelsarrow
      • Goal customer actions and scoring
        Pop-upsarrow
      • Creating and publishing a pop-up
        Setting up a popup in the code editor
        Managing pop-ups manually via script
        Popup analytics
        Guide: pop-up for push subscriptions
        Case: Creating a pop-up with the "Wheel of Fortune" widget
        Basic cases of placing a popup via the Tag Manager
        Tag Managerarrow
      • Configuring and installing Tag Manager
        Trigger types
        Variables types
        Linking a pixel and the Tag manager
      Settingsarrow
    • Account settings
      Custom links
      Virtual senders
      Sending policies
      Audit journal
      Tags FAQ
        Users, groups and accessarrow
      • Two-Factor Authentication (2FA)
        Connectionsarrow
      • Connection to Facebook Ads Manager
        Connection to Google Ads
        Connecting to Yandex.Audience™
        Connection to 360dialog
        Connection to Edna
        Connection to Devino Telecom
        Connection to SMSTraffic
        Connection to VK Ads™
        Connection to MTS OmniChannel
        Custom Authentication Connection
        OAuth2 connection
        Basic Authentication connection
        Token Authentication connection
        Connection to Rapporto
        MAX connection
        Connection to Notify
      Attribute settings
      API requests: where to startarrow
    • Import or update a profile
      Trigger mailing launch
      Engage profile in scenario
      Changelogarrow
    • v2026.1.76
      v2025.4.75
      v2025.4.74
      v2025.3.73
      v2025.2.72
      v2025.1.71
      v2024.4.70
      v2024.3.69
      v2024.2.68.2
      v2024.1.68
    Documentation archive
    library
  • 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.