Skip to content

Latest commit

 

History

History
34 lines (29 loc) · 1.8 KB

best-practices-for-store-segmentation.md

File metadata and controls

34 lines (29 loc) · 1.8 KB
title author description ms.author ms.date ms.topic ms.service keywords ms.localizationpriority
Best Practices for Store Segmentation in Economy (Legacy)
cybtachyon
Lists the Best Practices for configuring and using Store Segmentation with Economy (Legacy).
derekreese
10/29/2018
article
playfab
playfab, commerce, economy, stores
medium

Best practices for store segmentation (Legacy Economy)

[!INCLUDE notice]

  • Store segmentation is public information.

    • There are many ways for players to gain information about alternate stores.
    • Players naturally transition between segments, and see those changes when they transition.
    • Players discuss content on forums, community sites, wikis, etc.
    • In the PlayFab API, store information is public, unless you disable those APIs with our API Access Policy.
    • You should assume that players will be aware of other stores and their details.
  • Provide varying content, not varying pricing.

    • Players will feel cheated if:
      • Prices go up or down when they transition segments.
      • Prices described on wikis are different than their own.
    • The only exception to the pricing rule would be first time purchases.
      • You must secure the Client API methods with our API Access Policy to prevent multiple purchases, or make repurchasing less meaningful through game design.
  • Content should be relevant to the segment.

    • Whales are willing to spend large amounts of real money, and are therefore likely to buy more expensive bundles, if the value is worthwhile.
    • First time buyers may be given a good deal, but can only be (usefully) obtained once.
    • End game players may only be interested in specific items.