How to configure Offer Management in Chargebee Retention without a billing integration (non Stripe, Recurly & Chargebee users)?
How to process offers via dynamic URL redirect in Chargebee Retention?
How to process Offers via webhook in Chargebee Retention?
How to process Offers via email in Chargebee Retention?
If you do not use one of the Chargebee Retention-supported billing Integrations (Stripe, Recurly, or Chargebee) to manage your offers, we have a few options for you. You can choose one of the following to help manage your offers from Settings > Alerts in Chargebee Retention.
Processing offers via dynamic URL redirect
Note: If you are unfamiliar with how Chargebee Retention precancel requests work, check out our brief tutorial, Installing Chargebee Retention.js
Note: We've already placed the save_return_url as the nevermind buttons and back buttons in confirmation modals. Using the above expression can apply a unique URL for your canceller to follow that will come across to your endpoint as a GET request. When the user clicks Nevermind they will be redirected to the endpoint you have defined in the precancel request. In this way, you can dynamically append query parameters to your endpoint and trigger follow-up actions in your billing or other systems
Dynamic URL example
Note: In this example, [INTERNAL_USER_ID], represents the dynamic variable to be passed along with each precancel request you can pass as many query parameters as are necessary to process your internal automation
"save_return_url" : "https://www.example.com/brightback?save=true&id=[INTERNAL_USER_ID]"
"promo_code_url" : "https://www.example.com/brightback?id=[INTERNAL_USER_ID]&promo_code="
Note that you can't enter any spaces or illegal characters in the URL editor.
Processing offers via webhook
Note: The "offer" key holds the information you can use to trigger your follow-up automation. We'll include a unique name created when the offer was created which is immutable, the display name from the offer editor and the immutable "name" key which is generated when the offer is created.
"display_name": "100 dollar discount",
HTTP response codes:
By default we consider responses in the 200's to be a success. In the event you receive an event and do not wish to process it, please respond with code 422.
e.g. If you are filtering out certain offers by parsing the payload. Send a 422 response code if you received it but do not wish to perform any downstream processing.
Processing offers via email
Note: All Chargebee notification emails come from firstname.lastname@example.org. Ensure that you have whitelisted that email address in your helpdesk