Thanks to the Nexus Support-a-Creator API, it’s easier than ever to quickly implement “creator codes” in your live service game, incentivizing content creators to promote your game’s in-app purchases. Bloons TD 6 is a “gold star” example of this, as Ninja Kiwi has not only implemented the system to make it uniquely their own, but they’ve also made several quality-of-life adjustments along the way.
Based on the way users prefer to interact with Support-a-Creator systems as well as on Ninja Kiwi’s implementation, we have compiled the following best practices for developers who are in the process of implementing the Nexus Support-A-Creator API.
Make codes persistent
Fans want to support the creators that they follow–just as they want to support the game developers that they love. But they’re human, and like the humans who may be reading this, they’re tired, so there are only so many additional steps they will take before abandoning the effort entirely. For this reason, we strongly encourage making the creator code redemption process as simple and painless as possible.
One way to guarantee a painless process is to make creator codes persistent — meaning that when a user enters a creator code, that code will remain there as a saved entry, instead of requiring the user to re-enter the code each time. It doesn’t cost them anything extra to support a creator at checkout, so it shouldn’t cost them additional time and keystrokes, either.
This change also simplifies the job of the influencer. No longer does the goal have to be “maintain code usage.” Instead, the content creator focuses on introducing their creator code to as many new fans as possible.
Make codes apply to all cash-valued items
Many in-game cash shops offer a plethora of boosts, buffs, and bling–all of which can be redeemed with in-game currency, which players can purchase with real-world currency.
This in-game currency is just one of the handful of items that generate real-world revenue, as most microtransaction marketplaces also offer products like battle passes, expansion content, premium subscriptions, and value bundles. In short, if it is sold for cash, it can be marketed by influencers, so we recommend giving them the opportunity to do so.
Bloons players like Tewtiy have done an excellent job of promoting the use of their creator codes for general shopping purchases, but in the event that your team is launching a new season pass or unique premium item, you won’t want your influencers to have to explain multiple steps of support. If creator codes are applicable across the board, influencers can promote these interesting additions while simply reminding fans to use their creator code at checkout.
Name YOUR creator code system
Nexus is extremely proud to provide these tools, but remember: they are still YOUR tools to use! It’s your creator system, so it should be presented to users in a way that aligns with your presentation, influencer strategy, and marketing vernacular.
Consider the following: Who are your fans? How do they identify their love of your game? What do they want out of each session of play? What excites them? By acknowledging these concepts, you can effectively build creator support into your game as a natural extension of the existing presentation. Maybe it’s a “Creator Boost,” clearly indicating its function and generous intent. It’s up to you! No one knows your brand better.
Keep the Code Entry UI Simple
When implementing something new, it’s easy for old insecurities to creep in. “Do we stick to common conventions, or break free and take the path less traveled?” But, in this case, there’s no need to reinvent the wheel, and the path less traveled is just a great way to get lost.
Think of other scenarios in which you’ve entered any sort of promotional code. Where was the box? When did it appear? Was the code case-sensitive? The shortest distance to your solution, in this case, is a straight line. The box should be clear and visible just before checkout. There should be an obvious confirmation of code entry, a simple means of removing/resetting the code, and no one should ever have to question whether or not their code worked. If a user enters a code incorrectly, they should know about it. Finally, they will want to know that a portion of the sale is going to the correct influencer of their choice.
Take a look at some examples
If you’re still unsure of what your Support-a-Creator implementation should look like, go no further than Bloons TD 6. In Bloons, the creator code entry can be accessed at any time via the settings menu, where the last used code is saved for future purchases. Once input, the button emblazoned with the Nexus logo will display a checkmark, indicating to the user that their purchases are currently supporting the creator of their choice. At any time, they can change the creator they’re supporting, or remove that support entirely.
However, if a user inputs a code incorrectly, there is a clear and obvious indication of the failure. The checkmark does not appear, and the window is closed–requiring the user to click again in order to make another attempt at the correct code. Finally, code entry is case-insensitive, so influencers don’t have to scrutinize their instructions, or troubleshoot with their fans when their codes are entered incorrectly.
