Push Packs

What push packs are, how scheduled and event-based packs work, drafts and system packs

Push Packs are structured sets of push notifications with multi-language support. They let you build a complete communication strategy: define what and when a user receives after installing an application or performing an action.

Push Pack Structure

A pack is organized hierarchically:

Push Pack
└── Language package (en)
│   ├── Scheduled push (Mon 10:00)
│   ├── Scheduled push (Wed 18:00)
│   └── Event push (install + 5 min)
└── Language package (ru)
    ├── Scheduled push (Mon 10:00)
    └── Event push (reg + 60 min)

The system selects the language package automatically by the recipient's device language. If no matching language is found — the default language is used.

Two Types of Pushes in a Pack

Scheduled

Sent on the specified day of the week and time. Settings are similar to weekly schedulers.

Example: push every Monday at 10:00 with a promotion reminder.

When creating a scheduled push you set:

Day of week (one or several).
Send time.
Title, body, link and icon.
Variants for A/B testing (up to 4 variants).

Event-Based

Fires when a postback with the specified event is received, with a given delay in minutes.

Example: 5 minutes after the install event — a welcome push. 1440 minutes (24 hours) after reg — a reminder.

When creating an event-based push you set:

Event (e.g., install, reg, dep or custom).
Delay in minutes.
Title, body, link and icon.
Variants for A/B testing.

More about events — in the Custom Events section.

How to Use a Push Pack

Create a pack: Push Packs → "Create" → enter a name.
Add languages: click "Add language" → select the language code.
In each language, fill in pushes (scheduled and/or event-based).
Publish the pack (move from draft to published status).
Attach the pack to an application: open Applications → select the application → "Push Packs" section → add the pack.

After attaching, the system automatically sends pushes on schedule or when an event occurs, selecting the language by device.

Pack Constructor

The Pack Constructor is a four-step wizard for creating and editing push packs. Open it via Push Packs → Create (wizard button).

Step	What to do
1. Basics	Enter pack name and default language. Optionally select a system template.
2. Content	Add scheduled and event pushes for each language.
3. Preview	Check how pushes appear on iOS, Android, and Web.
4. Apps	Attach the pack to applications.

The pack is created at step 1. Changes are saved progressively — you can close the browser and continue from the same step by reopening the pack in edit mode.

Creating from a Template

On step 1, up to 8 published system packs are shown as templates. Click Use template to create a full copy — with all languages and pushes already filled in. The copy is yours to edit freely; the original system pack is not affected.

URL Autofill

When editing a push at step 2, you can fill the title, body, and image URL automatically from any web page:

Paste (Ctrl+V) a URL into the URL field — fields fill automatically.
Or enter a URL and click Fetch.

Field	Priority chain
Title	`og:title` → `twitter:title` → page `<title>`
Body	`og:description` → `meta description` → `twitter:description`
Image URL	`og:image:secure_url` → `og:image` → `twitter:image:src` → `twitter:image` → `itemprop:image`

If the page has no Open Graph or Twitter Card meta tags, the fields remain empty.

Copying Pushes Between Languages

Each push at step 2 has a Copy to language button. Select the target language — the push (title, body, link, image URL) is duplicated there. Translate the text for the target language independently after copying.

Push Preview

Step 3 displays every push in the pack as it would appear on three platforms:

iOS — iOS notification style
Android — Android / Chrome notification style
Web — desktop browser notification

Macros are replaced with sample values in the preview.

Pack Statuses: Draft and Published

Status	Description
Draft	Pack is in development. Not sent, not visible to other projects via API keys.
Published	Pack is active. Sent according to schedule or events.

This lets you prepare a new strategy as a draft, test it, and then launch to production with a single action.

System pack content is hidden — displayed as *** in the interface.
The administrator can publish and unpublish system packs.
System packs are visible to all API keys regardless of project_id.

System packs are convenient for platform templates that should be available to all clients without the ability to view implementation details.

API

Manage push packs via API:

Method	URL	Description
`GET`	`/api/v3/push-packs`	List push packs
`POST`	`/api/v3/push-packs`	Create a pack
`GET`	`/api/v3/push-packs/:pack_id/events/:event_id/variants`	A/B test variants
`POST`	`/api/v3/push-packs/:pack_id/events/:event_id/variants`	Add a variant