Skip to main content

Add a new version of AI Paywall node

Zuora

  • 日本語のコンテンツは機械翻訳されており、補助的な参照を目的としています。機械翻訳の精度は保証できません。英語版が正となります。また、現時点では検索機能は日本語での検索をサポートしていません。翻訳に関するフィードバックについては、docs@zuora.comに送信してください。

Add a new version of AI Paywall node

  1. Last updated
    Mar 10, 2025
  2. Save as PDF

Before you can add an AI Paywall node, you must configure the node so that it appears in the rule builder node palette for use when setting up rules.

  1. Navigate to Settings > AI Paywall > Add a New Version.
  2. (Optional) Enter a description for the new version in the Description field.
  3. Configure the following fields in the Decision Limits section:
    1. Page View Limits: The AI module determines the appropriate number of page views each user can access. Once a user reaches their limit, they will be blocked from viewing additional pages. Enter the required values in the Minimum Page View and Maximum Page View fields.
      1. The Minimum Page View defines the starting point for decision-making. For example, setting this to 2 ensures that all users can access up to page 2 without any restrictions, and no blocks will occur on page 1.
      2. The Maximum Page View defines the highest page count eligible for a block decision. For example, setting this to 6 means all users will be blocked upon reaching a total page count of 6. Note that the maximum limit is inclusive; if set to 6, blocks may apply as soon as users reach page 6.
    2. All Traffic Block Period: When a block decision is returned, you can specify the number of days a user will be blocked. This also applies to any users that have reached the maximum page view limit. Enter the duration in the Block Period (Days) field.
    3. Click Done.
  4. Define routes with clear and descriptive names, as these names will be used by the AI model to map to the correct outcome. For example, you might name a route "3-month offer," which would then link to the corresponding 3-month offer outcome. It’s crucial to maintain the association between the route and its purpose, such as the 3-month offer, across future versions. While it’s acceptable to update the route name, ensuring it remains tied to the 3-month offer is essential.
Setting the route label in the AI Paywall Node is very important. The route label must remain consistent, as it defines the model’s decision path. For example, if the first decision block represents a 1-month offer, it should always correspond to that offer. Changing its location alters how the model interprets outcomes associated with that label. However, you can update the outcome of an existing route. For instance, you may modify the 1-month offer by adding a discount or adjusting the price—the model will adapt based on user responses.
Do not assign a 1-month offer outcome to a 3-month offer route (or vice versa). This disrupts the link between user data and the offer, breaking the model’s understanding of what was presented.
  1. Configure if a route should be set as the Default route. The default route will determine whether, in the very rare event of a failure to fetch an AI decision, the feature will fail open (allow) or fail closed (specific block offer).
  2. Click Save Draft to save changes without activating, or Save & Activate to apply the changes immediately.
  3. Once you have saved and activated you must drag the newly created node into the Rules Builder and connect the node’s routes to the desired outcomes.
    If there is an existing rule with a prior node, and the new node gets activated but is not used in the rules, the prior node will continue to function in the live rules. Any responses from the model that do not match the prior node will be directed to the Default route of the prior node. In this case, the prior node will then be archived.