What to know
Apple describes promotional text as a way to tell App Store visitors about current features without requiring an updated submission. It appears above the description and cannot be longer than 170 characters.
Use the field for a real, timely message: a new feature, seasonal event, or important improvement. Lead with the user benefit. Do not fill it with repeated keywords, permanent claims, or promises the app cannot support.
Give promotional text a different job from the description. The description explains the product in a durable way. Promotional text can point to what is new, current, or timely. If the event ends, replace the message or remove the stale urgency.
Do not treat a promotional-text update as proof of a ranking change. Use it to improve the page story for visitors who see it, then measure the storefront signals you actually have. Keep search claims tied to Apple’s current documentation, not a vendor promise.
Write the benefit first and cut filler. A short message can name a new workflow, a current event, or a meaningful improvement. Avoid “best,” “number one,” or a result claim unless the team has evidence it can support.
Review each locale and timing separately. The same event may use different words or dates in another market. Save the final text, byte or character count, locale, source note, owner, and replacement date.
A durable description might say that an app tracks shared expenses. Promotional text can say, “Split this weekend’s group costs with the new receipt scan.” The first explains the product. The second gives a current reason to look closer. When the receipt feature changes or the event ends, update the short message instead of letting it become stale.
Use a small approval check before publishing: is the message tied to a real current feature, does the first phrase state a user benefit, can the build prove it, and is there a replacement date? Save the previous version so the team can explain what changed and why.
Give every timely message an owner and an expiry decision. The owner checks whether the feature, event, or improvement is still current. The expiry decision is to replace it, remove it, or keep it with a new reason. This avoids leaving seasonal language on the page after the moment has passed.
Keep a short evidence note beside the draft: the build or release that supports it, the locale, the date checked, and the reason the message is timely. If the message mentions a result or comparison, either attach support or rewrite it as a factual description of the feature.
Read the field beside the description and first screenshot before approval. Promotional text should add a current reason to look closer, not introduce a promise the rest of the page cannot prove. Save the old and new versions so a later test has a clear starting point.
Keep a timed-message register with the text, locale, feature or event, supporting build or release, publish date, owner, expiry decision, and replacement plan. If no one can name the next review date, the message is not ready for a live page.
Run a stale-message check after the event or release window. Compare the short text with the current build, description, screenshots, pricing, and supported regions, then replace, remove, or reapprove it. Do not preserve urgency merely because the field still fits its limit.
Reopen the message when the feature flag, release scope, locale, audience, or product promise changes. Keep the previous version and reason for replacement so a future editor can see which claim was time-bound and which evidence supported it.
ASOgenic can help draft options and check the limit. Your team should approve the current feature, the timing, and the truth of the claim before the text changes on a live product page.