Skip to main content

​
In-Game Marketing Integration

In-Game Marketing is used when store purchases must be delivered to connected game servers. VIP packages, crate keys, in-game currency, permissions, cosmetics, and command-based rewards are common examples. This workflow is more than a product card. The product also defines where the delivery happens, which command or reward is sent, how long it lasts, and which server receives it.

​
How It Works

A user buys a product from the store. When the purchase succeeds, Zonely checks the product’s delivery settings and prepares the server-side action. Delivery may happen through a command, role, timed package, or in-game balance. The selected server and product settings control what the user receives.
Always test command-based products before using them on a live server. A wrong command can grant the wrong permission, amount, or package.

​
Preparation

Before creating products, confirm that:
  • The game server is connected and reachable
  • Delivery commands work on the server
  • Product categories are ready
  • Duration, stock, and pricing rules are defined
  • Username or player identity is collected correctly during checkout
If you run multiple servers, explain exactly where each product is valid.

​
Create A Category

  1. Open Store Management > Product Categories.
  2. Create a category for in-game products.
  3. Add a clear name, description, and image.
  4. Check the category order in the store.
Good category names help buyers understand the product type quickly, such as VIP, Keys, Currency, or cosmetic items.

​
Create The Product

  1. Open Store Management > Products.
  2. Create a new product.
  3. Select the product type for in-game delivery.
  4. Enter the name, price, category, and description.
  5. Fill in server and delivery settings.
  6. Review commands or reward fields carefully.
  7. Run a test purchase and confirm delivery in-game.

​
Form Fields

FieldPurpose
Product NameName shown in the store.
CategoryControls where the product is listed.
ServerSelects the game server that receives the delivery.
PriceProduct sale price.
DurationUsed for timed packages or permissions.
StockOptional limited-sale quantity.
CommandsServer commands executed after purchase.
Command DescriptionExplains what the command gives to the buyer.
Product IconIcon shown on the product card.
GalleryProduct images or in-game previews.
Comparison ValuesOptional values used in package comparison tables.

​
Command Notes

Use the variables supported by the panel. If the form shows ready variables for username, player name, or product data, use those instead of writing custom placeholders. When preparing commands:
  • Start with a low-risk test command
  • Confirm the command only runs on the selected server
  • Explain expiration for timed packages
  • Test what happens when the same product is purchased twice

​
Before Publishing

Is the server connection active?
Do commands apply to the correct player?
Does the product description explain delivery timing?
Did a test purchase deliver the product in-game?

​
Common Issues

The product is purchased but not delivered in-game.
Check the server connection, commands, and player name mapping. Delivery happens on the wrong server.
Review the selected server and multi-server settings. The command does not run.
Try the command manually in the game server console. Permissions or command format may differ. Users do not understand duration.
For timed products, add the validity period and renewal behavior to the product description.