Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guideDeveloper guideAdmin guide
Company siteHelp center
English
  • Русский
  • English
v72
  • v74
  • v73
  • v72
Login
  • User API documentation
  • API interaction
  • Matching
  • Profiles
  • Databases
  • Resources
  • Segments
  • Static segments
  • Suppression lists
  • Templates and fragments
  • Campaigns
    • Activate campaign
    • Deactivate campaign
    • Get campaign list
    • Get campaign information
    • Get campaign log
    • Clone campaign
    • Delete campaign
    • Get campaign status
    • Broadcast campaigns
    • Regular campaigns
    • Trigger campaigns
      • Get trigger campaigns list
      • Get trigger campaign information
      • Create trigger campaign
      • Update trigger campaign
      • Trigger launch (API call)
      • Profile import + trigger campaign launch
      • Task for bulk trigger launch
      • Task for bulk profiles import + trigger launch
      • Bulk trigger launch
      • Bulk profiles import + trigger campaign launch
      • Clone a trigger campaign
      • Data array
  • Automation scenarios
  • Promo codes
  • Goals
  • Application push notifications
  • Market
  • Analytic reports
  • SendersDevv71
  • External datatables queries
  • Objects
  • Miscellaneous
  • Importing the API collection in Postman
  • List of API endpoints
  • SDK
This is documentation for Altcraft Platform v72. This documentation is no longer maintained.
The information for up-to-date platform version at this page is available (v74).
  • Campaigns
  • Trigger campaigns
  • Data array
Documentation for version v72

Data array

Description​

The data array is used in the following queries:

  • Task for bulk trigger launch
  • Task for bulk profiles import + trigger launch
  • Bulk trigger launch
  • Bulk profiles import + trigger campaign launch

The array consists of objects, each of which contains information about a separate profile. As the key and value of the object, you must specify the data by which the profile will be searched in the database.

Parameters​

ParameterTypeExampleRequiredDescription
emailstring"john@example.com""matching":"email" - by profile and subscriptions

"matching":"email_profile" - only by profile

"matching":"email_sub" - only for subscriptions
Email address
phonestring"+79000000000""matching":"phone" - by phone number from profile and subscriptions

"matching":"phone_sub" - by phone number from subscriptions
Phone number
profile_idstring"abcdefghijklmnqrstuvwxyz""matching":"profile_id"Profile ID
field_valueint/string"12345""matching":"custom"Field value for search
custom_requestJSON object
{
"email": {
"$in": [
"asd@dsfsd.com",
"zxcv@sdfsd.com"
]
}
}
When no matching
specified
Custom MongoDB database query

Examples​

email​

  • JSON
  • XML
 "data": [
{"email": "profile1@example.com"},
{"email": "profile2@example.com"}
]
<data>
<email>profile1@example.com</email>
</data>
<data>
<email>profile2@example.com</email>
</data>

phone​

  • JSON
  • XML
 "data": [
{"phone": "+79000000000"},
{"phone": "+79000000001"}
]
<data>
<phone>+79000000000</phone>
</data>
<data>
<phone>+79000000001</phone>
</data>

profile_id​

  • JSON
  • XML
 "data": [
{"profile_id": "60ae529b3f62fcdebdb159bb"},
{"profile_id": "843vfdkisfh934hfe834rhkk"}
]
<data>
<profile_id>+79000000000</profile_id>
</data>
<data>
<profile_id>+79000000001</profile_id>
</data>

custom​

  • JSON
  • XML
"data": [
{"field_value": "001"},
{"field_value": "002"}
]
<data>
<field_value>001</field_value>
</data>
<data>
<field_value>002</field_value>
</data>
Last updated on Aug 20, 2024
Previous
Clone a trigger campaign
Next
Automation scenarios
  • Description
  • Parameters
  • Examples
    • email
    • phone
    • profile_id
    • custom
© 2015 - 2025 Altcraft, LLC. All rights reserved.