Redirecting After Purchase
This set up is intended for developers who wish to customize Redirect URL with Custom Parameters after successful purchase from the customer.
Last updated
This set up is intended for developers who wish to customize Redirect URL with Custom Parameters after successful purchase from the customer.
Last updated
This guide explains how to set up an instant redirect URL after a successful subscription purchase, including adding query parameters to provide additional information during the redirection process.
When a user successfully completes a subscription purchase, you can redirect them automatically to a specific URL. This URL can be set to a page on your website, such as a welcome or thank-you page, for example: https://example.com/subscription-success.
You also have the option to include query parameters in the redirect URL to pass important information related to the subscription, such as product IDs or order details.
Enter the Instant Redirect URL: Specify the URL where users will be redirected after they complete their subscription purchase. For instance, you can use:
This URL will act as the landing page after a successful transaction.
Access it here: - under Checkout Tab:
Select URL Parameters: You can select parameters that will be automatically added to the redirect URL from a predefined list. These parameters will be populated dynamically during the redirection process. For example, if you select fngs-product-internal-id from the available parameters, the final URL might look like this:
This allows you to pass relevant information such as the product or order ID to the destination page, which can be useful for tracking or displaying personalized messages.
Add Custom Query Parameters: You may also add your own custom query parameters directly within the URL. For custom parameters, you must make sure to manually or programmatically assign values. For example:
Combining Predefined and Custom Parameters: You can combine predefined parameters from the system and your own custom parameters to construct a more detailed redirect URL. For example:
All system-generated query parameters are prefixed with fngs to avoid conflicts with user-defined custom parameters. Below is a list of all the available system parameters that you can use:
fngs-product-id: The unique identifier of the product purchased.
fngs-order-id: The unique identifier of the order.
fngs-order-number: The human-readable order number for tracking purposes.
fngs-subscription-id: The unique identifier of the subscription.
fngs-variant-id: The identifier for the product variant purchased.
fngs-offer-id: The identifier for the offer linked to the purchase.
fngs-product-internal-id: The internal identifier used for the product.
fngs-variant-internal-id: The internal identifier for the variant.
fngs-offer-internal-id: The internal identifier for the offer.
fngs-quantity: The quantity of items purchased.
fngs-user-id: The unique identifier for the user making the purchase.
fngs-user-email: The email address of the user.
fngs-total-value: The total value of the purchase.
fngs-total-items: The total number of items in the order.
fngs-country: The country from where the purchase was made.
fngs-currency: The currency used for the transaction.
These parameters can be selected and added to your redirect URL to pass relevant details automatically, providing a richer user experience and more detailed tracking.
Enter the Redirect URL: Define where users are directed post-purchase.
Select Predefined Parameters: Choose from system-generated parameters like product or order IDs.
Add Custom Parameters: Include additional information for personalization or tracking.
Combine Parameters: Use both predefined and custom parameters to create a comprehensive redirect URL.
System Parameter Prefix: All system parameters are prefixed with fngs to avoid conflicts with custom parameters.
Here, the user and campaign parameters are added manually, allowing you to track specific user information or marketing campaign details.
Ensure that each parameter has a corresponding value, either provided by the platform or manually defined, to ensure smooth redirection without errors.
