Skip to main content

Test your Cleverbridge setup and integrations

How to test your setup

Use your Cleverbridge account for both real purchases and test scenarios. This way you can validate your setup, confirm integrations work as expected, and verify end-to-end workflows—without the risk of human errors caused by duplicated accounts.

Testing recommendations

Use controlled payment tests, check product, design, and messaging updates before you go live.

Conduct test purchases with your test credit card

Test orders help you ensure correct delivery of the products, check email delivery, and make sure that notifications are properly generated, processed and parsed into your CRMs correctly. You can also use test orders to preview a customer’s path after an unsuccessful payment.

To place a test order, request a test credit card number from your Cleverbridge contact (card format is T20..........04T). Enter this number at checkout, choose any expiry date and any three-digit CVV to complete the purchase.

Internally, the system flags these purchases as Successful Test Order, making it easy to distinguish them from real orders.

For more details, see How to generate a test Purchase Order and Customer email types

Validate your setups with dedicated test products

To avoid impacting your live environment, you can create dedicated items (such as products, promotions, or recommendations) in your production account for testing purposes only.

It is up to you to set up new items or copy existing ones. The configuration process is the same as for regular items, but we recommend using a clear naming convention (for example, prefixing with TEST) to identify their test purposes. Since you won’t publish links to these items on your website, they won’t be available for purchase of visible to the customers.

Validate design changes before launching them

Any design changes should be tested before launch to ensure they are working as expected and meet your needs.

Cleverbridge will send you a link to the staging configuration, which is a clone of your production setup. You can open it in a browser, apply and review the changes without affecting your live environment and ensuring proper testing. Only after you approve the updates, we will publish them to production.

Production testing guardrails

Follow these guardrails when testing in production to avoid impacting real customers, data, or performance.

  • Use dedicated test setups and data - Always use designated products, configurations, and data for testing.

    • Never use real customer information for testing.
    • To additionally flag the purchase as a test order, we recommend to include “Test” in one of the address fields during a test purchase.
  • Limit testing volume - Excessive testing in production cam trigger account locks. To avoid system overload and ensure stable performance, keep all test activity within these limits:

    • Do not create more than 200 test orders consecutively.

    • Do not exceed 1,000 active test subscriptions at any time.

      important

      Never run automated or stress testing in production - Performance, load, and stress testing should never be conducted in a production environment.

  • Maintain Data Integrity and Compliance - Keep test activities isolated from real customers and adhere to data-protection obligations.

    • Avoid triggering real customer emails, notifications, or transactions during testing.
    • Ensure all testing activities comply with data protection regulations and do not impact live operations.

Did you find this doc useful?