Subscription Product ID

Subscription Product ID is a Native element that represents a priced product identifier used to offer subscriptions in the application.

A subscription grants users access to features or content for a specific period of time and may automatically renew based on store configuration.

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

Key characteristics

• Subscription Product ID must have a price.
• Used for subscription-based products.
• The default context (Customs) is optional and may be left empty.
• In some cases (by agreement with development), values such as trial or non-trial may be required in the default context.
• Subscription Product ID must be linked to a Subscription Product ID Context.
• It can be used in the following campaign types:
  • Subscription
  • Subscription LTO
  • Mixed
  • Mixed LTO
  • A/B test campaigns for the campaign types listed above

How to create a Subscription Product ID

1. Go to Configuration > Native elements > Create new.
2. In the creation form:
   • select the Application;
   • enter Name;
   • enter Human-readable name;
   • set the Cost;
   • choose Native element type > Subscription Product ID;
   • configure the Subscription Product ID Context (and default context if required).

Naming rules

Name

The Name field is defined by the person configuring campaigns.

• The value does not affect application behavior.
• Used only in analytics and reports as a Product ID filter.
• It is recommended to follow the same naming style as other Product IDs (e.g. Consumable Product ID).

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 needed.
• This field does not appear in analytics or reports.

Cost

The Cost field is required for Subscription Product ID.

• Defines the subscription price in USD.
• Must match the price configured in the app stores.
• Used for:
  • displaying the price in campaigns and creatives;
  • subscription validation;
  • revenue analytics.

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

Product ID Context

Each Subscription Product ID must be associated with a Subscription Product ID Context.

• The context is used in creatives and subscription campaign logic.
• It defines subscription behavior and related parameters.
• A default context may be left empty, unless required by application or SDK logic.

More details will be available in the Product ID Context article.

Customs behavior

The default context defined in Customs is used when:

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

For Subscription Product ID, the Customs field is optional and may be left empty.

If, at the time of product creation, the final JSON structure is not yet known, you may enable the Confirm empty option. In this case, the product will be saved with an empty JSON in the Customs field.

Final step

Click Save to create the Subscription Product ID.

Once created, the Subscription Product ID can be used in Subscription, Subscription LTO, Mixed, and Mixed LTO campaigns, including their A/B test variants, and will be available in analytics as a Product ID filter.