Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.omneo.io/llms.txt

Use this file to discover all available pages before exploring further.

Testing your Omneo configuration thoroughly before launch prevents customer-facing issues with incentive balances, redemptions, and comms.

​
Use your staging environment

Omneo provisions a staging environment for each tenant. Your staging URL follows this pattern:
  • CX Manager staging: {tenant}-stg.manager.getomneo.com
  • Clienteling staging: {tenant}-stg.clienteling.omneo.io
  • API staging: https://api.{tenant}-stg.getomneo.com/api/v3
Always test new configurations on staging before applying them to production.

​
Create test profiles

Create dedicated test profiles in your staging environment for each test scenario. Use clearly identifiable email addresses (e.g., test-gold-tier@yourbrand.com, test-new-member@yourbrand.com). Avoid using real customer email addresses for testing — this can trigger real comms sends.

​
End-to-end test checklist

​
Profile and identity

  • Profile created via POS integration
  • Profile created via eCommerce checkout
  • Profile identity linked (Shopify, POS, etc.)
  • Profile search returns correct results

​
Transactions

  • Transaction created at POS and visible in CX Manager
  • eCommerce order creates Omneo transaction on completion
  • Transaction aggregations updated after transaction (allow for delay)

​
Incentives

  • Points awarded correctly after transaction
  • Tier progression calculated correctly
  • Reward issued manually and visible on profile
  • Reward redeemed at POS — redemption recorded, transaction linked
  • Benefit issued and redeemed at POS and online

​
Reactions

  • Test each configured reaction by triggering the relevant event
  • Verify actions executed (points awarded, benefit issued, target sent)
  • Verify filter conditions gate correctly (non-matching profiles do not receive action)

​
Comms

  • Welcome email triggers and delivers
  • Balance notification email renders correctly
  • Expiry reminder fires at the correct time

​
Testing reactions

The safest way to test a reaction is to:
  1. Create a test profile in staging
  2. Trigger the relevant event (e.g., create a transaction, manually assign a tier)
  3. Check the profile in CX Manager to verify the expected outcome
For target-based reactions, use a tool like Pipedream or webhook.site to inspect the payload before connecting your real endpoint.