Implementing Login Walls and Paywalls

Adding login walls and paywalls to your games can be a powerful way to monetize your content and encourage user engagement. This guide will walk you through the steps of setting up gated content with Playgent, using events and access control to restrict certain features until users log in or make a purchase.

Step 1: Choose Which Features to Gate

Start by deciding which features you want to restrict with a login wall or paywall. Common options include:

Leaderboard: Require login or payment to view rankings.
Archive: Limit access to past games or exclusive content.
Analytics or Stats: Make detailed performance stats available only to premium users.

You can manage these settings in the Admin Portal by navigating to the settings of the game you want to customize.

Step 2: Enable Gating for Selected Features

Within the Admin Portal:

Go to the Game Settings section.
Select the feature you wish to gate, like Leaderboard or Archive.
Enable the Gated option to restrict access.

With this enabled, users will trigger a request event when they attempt to access the gated feature. Instead of the feature opening immediately, Playgent will send a request to your app for permission, giving you the control to allow or deny access based on login or subscription status.

Step 3: Listen for Request Events in Your Application

When a user tries to access a gated feature, a request event (e.g., PLAYGEN_REQUEST_LEADERBOARD or PLAYGEN_REQUEST_ARCHIVE) will be sent from Playgent to your application. You need to set up an event listener to capture and respond to these events.

Example Event Listener

Add the following code to your application to listen for gated feature requests:

window.addEventListener("message", (event) => {
  if (event.origin !== "https://play.Playgent") return;

  const { event_name } = event.data;

  if (
    event_name === "PLAYGEN_REQUEST_LEADERBOARD" ||
    event_name === "PLAYGEN_REQUEST_ARCHIVE"
  ) {
    handleAccessRequest(event_name);
  }
});

This code checks for events that indicate a request for a gated feature, then triggers your custom logic in the handleAccessRequest function.

Step 4: Implement Access Logic

Now, decide when to grant or deny access. You can use login status or subscription details to control this logic. For example:

Login Wall: Check if the user is logged in. If they are, grant access. If not, prompt them to log in.
Paywall: Check if the user has a subscription. If they do, grant access. If not, prompt them to subscribe.

In your handleAccessRequest function, define the rules for each case.

Example Logic

function handleAccessRequest(eventName) {
  const isUserLoggedIn = checkUserLoginStatus(); // Custom function
  const hasUserSubscribed = checkUserSubscription(); // Custom function

  let grantAccess = false;

  if (eventName === "PLAYGEN_REQUEST_LEADERBOARD") {
    grantAccess = isUserLoggedIn && hasUserSubscribed;
  } else if (eventName === "PLAYGEN_REQUEST_ARCHIVE") {
    grantAccess = hasUserSubscribed;
  }

  sendAccessResponse(eventName, grantAccess);
}

This example checks if a user is logged in and subscribed before granting access to gated content.

Step 5: Send a Resolver Event to Grant or Deny Access

Once you’ve decided to grant or deny access, send a PLAYGEN_RESOLVER event back to the game with your decision.

Example Resolver Event

function sendAccessResponse(eventName, grantAccess) {
  const responseEvent = {
    event_name: "PLAYGEN_RESOLVER",
    resolver_type: eventName,
    resolved: grantAccess,
  };

  window.parent.postMessage(responseEvent, "https://play.Playgent");
}

This code sends an event to either open the gated feature or deny access, depending on the value of grantAccess.

Step 6: Test in the Playground

Use the Playground in the Playgent Admin Portal to test and debug your implementation. The Playground allows you to view events in real-time, making it easy to verify that your login walls and paywalls are functioning correctly.

Open the Playground section in the Admin Portal.
Trigger the gated feature requests to see if your access logic is working as expected.
Adjust your code if needed based on test results.

Additional Tips

Display Custom Messages: Use custom prompts or modals to inform users why they need to log in or subscribe.
Analytics and A/B Testing: Track the effectiveness of login walls and paywalls by monitoring user behavior with analytics tools.
Clear Communication: Make it clear to users what they’ll gain by logging in or subscribing, improving conversion rates.

By implementing login walls and paywalls, you can create more engaging experiences and unlock monetization opportunities. For more advanced customizations or assistance, feel free to reach out to Playgent support.

Implementing Login Walls and Paywalls

On this page