Italy iOS entry card: verify product names across the acquisition journey

The Italy card treats product naming as a measurable launch dependency. A reward shown in an Italian ad, named differently on the store listing and described a third way in the game can make a functioning checkout difficult to understand. That is a hypothesis to test with reviewers, not an asserted national preference.

What the official record establishes

Apple’s service-availability record includes the App Store in its Italy section. Its payment-method record lists TIM and WINDTRE mobile billing. These examples are not an exhaustive list: the live source’s eligibility notes still apply, and the page says methods can change. Storefront availability does not establish that your particular game is approved, distributed or purchasable there.

The first test to run

Create a three-column terminology record for ad, listing and game. Mark each shared item with its product identifier where possible. The purchase test should confirm which configured item is delivered, preserving the distinction between copy consistency and backend entitlement correctness.

Localise the observed journey

Ask an Italian reviewer to inspect singular and plural reward labels, limited-duration wording and support instructions. Reuse approved terms only after checking their surrounding context. A glossary is useful evidence of consistency, but it is not a substitute for seeing the strings in the actual layout.

Keep the decision tied to evidence

Use the editable launch checklist and CSV evidence matrix to keep documented availability separate from actual tests. Both include explicit untested states. The country card supplies no CPI, ROAS, payer-share estimate or legal clearance. Local expert review, game-specific distribution checks and real account observations remain outstanding.

Before a paid test, define the campaign identifiers, install cohort, offer event and purchase outcome you intend to reconcile. Inspect a permitted test transaction end to end, then preserve the raw event references. A successful walkthrough establishes implementation evidence for that case; it cannot establish campaign incrementality or expected acquisition economics.

Background in the existing archive: A Creative Brief Template That Playable Teams Actually Use and Text-free playable design for global campaigns. These are contextual links, not a certification of every archived claim.

Research checked 19 September 2026. Local-market verification remains required. No observed campaign or purchase results are claimed.