PWA welcome gift campaigns: SKU sourcing, reward popup behavior, and test SKU replacement

For the PWA welcome gift flow, the configured gift SKU is the source for both the reward presentation and the granted contents.

How SKU data is used

• Notification gift icon: the gift icon shown to players in the PWA install/welcome notification is pulled from the configured gift SKU.
• Reward collection popup: the contents shown in the reward collection window are also pulled from the configured gift SKU.

Can the extra reward window be skipped?

Yes. The flow can be changed so that tapping the Free button grants the reward automatically, without opening the additional reward-collection window. This is useful when the welcome gift contents are already visible in the previous screen and you want to reduce the number of steps.

If desired, a separate post-grant notification can still be shown after the reward is issued.

Using a test SKU

Yes. You can replace the gift SKU with a separate test SKU, including a test bundle with emeralds.

When changing the SKU, update it in both campaigns involved in the flow:

• the campaign that offers the gift, and
• the campaign that grants the gift.

Retesting the PWA welcome gift flow

When retesting the flow for the same player, changing player attributes alone may not be enough.

• Before retesting, delete the PWA app from the device first.
• Then reset the relevant player attributes and save them.
• After saving, refresh and confirm the new values persisted before starting the next test.

In the reported test flow, removing the PWA installation was required in addition to resetting attributes such as the notification counter, gift-issued flag, and installed-state flag.

Troubleshooting: gift marked as issued but no reward seen

If the player opens the PWA and the flow marks the gift as issued, but no reward is visible, first check whether the game server returned an error while attempting to deliver the item.

Also check whether the player still has a previous undelivered gift. A pending earlier gift can block the expected behavior for the new one. In the reviewed case, after the earlier gift was claimed in-game, the new reward delivery worked as expected.

Current behavior of the install popup/instruction step

The instruction-style popup used in earlier testing iterations was removed from the current flow. The reason given was that the flow now opens a fuller install window, so there is no longer a separate instructional step to show.

If you notice differences between a compact popup and the larger install window during testing, treat that as flow/version behavior rather than SKU-driven content.

Implementation note

If you switch to automatic granting, review whether the follow-up reward notification should remain enabled or be turned off, depending on the desired player experience.