Consumable Product ID

Consumable Product ID is a Native element that represents a priced product identifier that can be purchased by users multiple times.

It is used for in-app purchases such as currency packs, boosters, or other consumable items (for example, $3.99 for a set of boosters).

This element represents a real in-app purchase and must correspond to a product created in the app stores.

You can see an example of a created Consumable Product ID in the demo application here.

Key characteristics

• Consumable Product ID has a price defined in the Cost section (in USD).
• The product can be purchased multiple times by the same user.
• Consumable Product ID includes purchase and revenue tracking.
• Both Cost and Customs fields are required.
• Consumable Product ID must be linked to at least one In-app Product ID Context.

Consumable Product ID can be used in the following campaign types:

• In-app
• In-app LTO
• Mixed
• Mixed LTO
• A/B test campaigns for the campaign types listed above

Required fields

Name

The Name field is defined by the person configuring campaigns and must exactly match the Product ID created in the app stores (App Store / Google Play).

• Used in analytics and reports as a Product ID filter.
• Must be identical to the store product identifier.

Human-readable name

The Human-readable name is used only inside the system for convenience.

• Recommendation: use the same value as in Name.
• A more descriptive name may be used if additional clarification is needed.
• This field does not appear in analytics or reports.

Cost

The Cost field is required for Consumable Product ID.

• Defines the product price in USD.
• Must match the price configured for the product in the app stores.
• Used for purchase validation and revenue analytics.

If the Cost field is not set, the product cannot be saved.

Customs

The Customs field is required for Consumable Product ID and defines the product’s default context.

• Specifies what and in what quantity is granted to the user after purchase.
• Must be provided as a JSON object.
• The JSON structure must match the In-app Product ID Creative structure for the application.
• Only one default context is allowed per product.

{

"items": [

{

"bonus": "hint",

"count": 5

}

]

}

Customs behavior

The default context defined in Customs is used when:

• a purchase is completed using a promo code;
• a purchase is completed directly inside the application;
• the purchase flow is interrupted or cannot be resolved via a campaign context.

Consumable and Non-consumable Product IDs must not have empty Customs.

If, at the time of product creation, you do not yet know the final JSON structure, you may enable the Confirm empty option.

In this case, the product will be saved with an empty JSON in the Customs field.

In-app Product ID Context

Each Consumable Product ID must be associated with at least one In-app Product ID Context.

• Defines what and in what quantity is granted to the user for a purchase.
• A single Consumable Product ID may have multiple In-app Product ID Contexts.
• Contexts are used in campaign logic.

More details are available in the Product ID Context article.

Final step

Click Save to create the Consumable Product ID.

Once created, the Consumable Product ID can be used in In-app, In-app LTO, Mixed, and Mixed LTO campaigns, as well as A/B test campaigns for these campaign types, and will be available in analytics and reports as a Product ID filter.