Cross Platform Resume (CPR)
Overview
This guide provides a comprehensive overview of Cross-Platform Resume (CPR) and CPR Authentication (CPR Auth), which helps in seamless resuming across devices and platforms while maintaining security and user data protection.
CPR reduces user drop-offs by allowing them to resume their journey without restarting, improving conversion rates and enhancing the overall onboarding experience.
What does this guide cover?
- Cross Platform Resume Overview (CPR): How CPR enables users to resume journey across different devices and platforms.
- CPR Auth: How CPR Authentication ensures that only authorized users can access their saved progress, preventing unauthorized access to PII.
- Integration Steps: APIs, SDK configurations, and best practices for implementing CPR and CPR Auth.
- FAQs and Debugging Guide: Common questions, troubleshooting steps, and solutions for potential integration issues.
Who is this guide for?
- Solutions/Support team integrating CPR and CPR Auth into client's applications.
- Anyone who wants to understand how CPR works.
When should this be used?
- Client Integrations: When a client requires CPR to be integrated in user onboarding flows.
- Debugging: For identifying and resolving common integration issues related to CPR and CPR Auth.
- For understanding how CPR works.
Demo Video
Video: CPR Demo Video View on Google Drive
Prerequisites
- Knowledge on SDKs and their integrations.
- Workflows and Workflow Builder
Deep-Dive
Explore each area of CPR in detail:
- CPR Purpose & Use Case — Why CPR exists and what problems it solves
- CPR Functions — Core functions like State, UniqueId, Auth, expiresAfter, resumeFrom, and more
- CPR API Reference — API endpoints for auth token generation and state management
- CPR Client Integration Guide — Step-by-step guide for integrating CPR
- CPR FAQs — Frequently asked questions
- CPR Debugging Guide — Troubleshooting common issues