Choose Your Integration Path
Start with the experience you need and the supplied setup. These guides are for the team placing Returning.AI inside an existing website.
I need a personalized widget
Use the Widget SDK with a token from your trusted backend. Keep your existing frontend, backend and login. This is the recommended path for new rewards, quests and store integrations.
Open the widget quickstartPublic bannerI can only paste HTML
If a public campaign banner meets your goal, request a configured open banner. It does not replace a personalized rewards widget. Your CMS must allow the supplied JavaScript; ask your setup contact which path is approved if you need user-specific content.
Read the banner guideSetup approval requiredMy supplied setup approves a legacy embed
Use the legacy instructions only when Returning.AI explicitly approves that authentication method for your supplied setup. No backend access alone is not approval. Your team must still supply correct identity and session wiring.
Read the legacy embed guideBefore you choose
- A build tool is not a backend
- Plain HTML can use server-authenticated widgets too. React, Next.js, Vue and Angular guides are separate from the Node.js, PHP and Python backend examples.
- Identity still needs an owner
- For personalized content, your engineering team connects the signed-in user. A copied template does not establish identity, enrollment or permission to use legacy authentication.
- Confirm the supplied experience
- Ask your Returning.AI setup contact for the configured widget or banner, its environment and any access restrictions. A public banner is a different experience from quests, rewards or the store.
Maintaining an older installation? Start with the migration and cutover checks. Record unresolved setup questions and their owners in the existing handover sheet.