SAP Customer Data Cloud
SAP SE · SAP (Gigya acquisition closed 2017, $350M)
Last verified 2026-04-07 · Reviewed by guptadeepak
Editorial verdict
SAP Customer Data Cloud (formerly Gigya) is the right CIAM choice for existing SAP Commerce Cloud or SAP Customer Experience customers, where the customer-data-unification heritage and SAP integration depth justify the platform. Twenty years of B2C consent management and preference center expertise are uncommon outside this product. Outside SAP shops, the DX gap and very high pricing make it the wrong choice for greenfield evaluation.
Last verified by @guptadeepak on 2026-04-07.
At a glance
- Best for
- Existing SAP Commerce Cloud or SAP Customer Experience customers
- Pricing
- enterprise-quote
- Free tier
- None
- Deployment
- cloud-saas
- SOC 2 Type II
- Yes
- Passkeys
- Native
- Self-host
- No
- Open source
- No
Funding & business
- Funding model
- Platform division
- Total raised
- None
- Latest round
- Acquired · $350M · 2017
- Years in business
- 20 yrs
- Round led by
- SAP
- Profitable
- Not disclosed
Built on Gigya, which SAP (NYSE: SAP) acquired for ~$350M in 2017.
Funding data from primary source. See also the CIAM investor landscape.
Strengths
- Twenty years of B2C CIAM experience (Gigya since 2006) with deep consent management, preference center, and progressive profiling.
- Tight integration with SAP Commerce Cloud and broader SAP Customer Experience portfolio.
- Comprehensive consent and privacy capabilities, purpose-specific consent, audit trails, regulatory alignment.
- Strong B2C customer data unification, the former Gigya CDP heritage shows.
Limitations
- Enterprise-only commercial structure with very high entry pricing.
- DX is dated; the SAP integration overlay adds complexity for non-SAP teams.
- Outside SAP ecosystem the integration story does not justify the cost.
- Sprawling SAP product naming creates evaluation complexity.
Capability matrix
Every vendor scored on the same axes. See the methodology for criteria.
| Password authentication | Yes |
|---|---|
| Social login | Yes |
| Magic links | Yes |
| SMS OTP | Yes |
| Email OTP | Yes |
| TOTP (authenticator app) | Yes |
| Push MFA | No |
| WebAuthn / passkeys | Yes |
| Biometric | Yes |
| Hardware security keys | Yes |
| SAML SSO | Yes |
| OIDC SSO | Yes |
| OAuth 2.0 SSO | Yes |
| Enterprise federation | Yes |
| Passwordless-only flows | Yes |
| Adaptive MFA | Yes |
| Step-up auth | Yes |
| RBAC | Yes |
|---|---|
| ABAC | Partial |
| ReBAC | No |
| FGA engine | No |
| API authorization | Yes |
| Fine-grained permissions | Yes |
| Self-service registration | Yes |
|---|---|
| Progressive profiling | Yes |
| Self-service account | Yes |
| Bulk user import | Yes |
| Admin user search | Yes |
| Custom user metadata | Yes |
| Organizations / tenants | Partial |
| Multi-tenancy | Yes |
| SCIM provisioning | Partial |
| REST API | Yes |
|---|---|
| GraphQL API | No |
| SDKs | js, node, ios, swift, android, kotlin, dotnet, java |
| CLI | No |
| Terraform provider | No |
| Local emulator | No |
| Extension model | WebSDK + Site Extensions (proprietary JS) + Webhooks |
| Bot detection | Yes |
|---|---|
| Breached password detection | Yes |
| Brute-force protection | Yes |
| Anomaly detection | Yes |
| Log streams | Yes |
| Audit logs | Yes |
| GDPR data export | Yes |
| PII minimization | Yes |
| Post-quantum roadmap | No |
| MCP support | No |
|---|---|
| OAuth 2.1 | Partial |
| Dynamic client registration | No |
| Agent vs human token separation | No |
| Web Bot Auth | No |
| SOC 2 Type II | Yes |
|---|---|
| ISO 27001 | Yes |
| ISO 27018 | Yes |
| HIPAA | Yes |
| PCI DSS | No |
| GDPR | Yes |
| CCPA | Yes |
| FedRAMP | No |
| EU data residency | Yes |
| Consent management | Yes |
|---|---|
| Preference center | Yes |
| Purpose-specific consent | Yes |
| Integrates with CMPs | OneTrust, TrustArc |
| Multi-region deployment | Yes |
|---|---|
| Data residency control | Yes |
| Proven at high scale (1M+ MAU) | Yes |
| Password-hash import | Yes |
|---|---|
| Lazy / just-in-time migration | Yes |
| Account linking & dedup | Yes |
| Custom domains per brand | Yes |
| Per-brand theming of all flows | Yes |
| Per-brand consent partitioning | Yes |
| Deletion webhooks / cascade | Yes |
| Event streaming / webhooks | Yes |
| Documented rate limits | Yes |
Developer experience & lock-in
Editorial 1–5 scores and migration effort, scored on the same axes for every vendor. See the methodology for how these are graded.
Developer experience
- Community
- Medium
Migration & lock-in
High lock-inEffort to adopt this platform
Effort to leave later (your exit cost)
Higher exit effort means more switching cost. Ask about bulk user export (including password hashes) before you commit.
Enterprise readiness
Enterprise-ready · 86/100A computed read of how ready this vendor is to sell into the enterprise, derived from the capability matrix. See the enterprise-ready pillars.
- 100
Enterprise SSO
SAML SSO · OIDC SSO · Enterprise federation
- 50
Directory sync (SCIM)
SCIM provisioning (partial) · Organizations (partial)
- 70
Organizations & tenancy
Multi-tenancy · Organizations (partial)
- 85
RBAC & custom roles
RBAC · Fine-grained permissions · ABAC / ReBAC / FGA (partial)
- 100
Audit logs & streaming
Audit logs · Log streaming
- 100
Compliance certifications
SOC 2 Type II · ISO 27001 · HIPAA / FedRAMP
- 100
Security posture
Anomaly detection · Brute-force protection · Breached-password checks · Adaptive / step-up auth
Scored from our capability review; confirm the exact plan tier and SCIM scope with the vendor before you commit.
Pricing
| 10,000 MAU | Quote required |
|---|---|
| 100,000 MAU | $8,500/mo |
| 500,000 MAU | $26,000/mo |
| 1,000,000 MAU | $45,000/mo |
- SAP enterprise sales engagement; quote-based pricing
- Strong fit for existing SAP Commerce Cloud / SAP Customer Experience deployments
- Pricing typically among the highest in the index, six-figure annual minimums standard
Estimates use the standard assumptions in our methodology. Always confirm with the vendor.
Best for
- Existing SAP Commerce Cloud or SAP Customer Experience customers
- Large-enterprise B2C deployments with deep consent management requirements
- Regulated industries needing customer data unification plus CIAM
Not for
- Mid-market or startup deployments
- Greenfield projects without SAP ecosystem context
- Teams prioritizing developer velocity over SAP integration depth
Solves for
Enterprise pain points this vendor covers on the mapped capabilities. See all pain points.
- B2B multi-tenancy: the edge cases bolted-on models miss
- Identity unification and deduplication as a program
- Integration sprawl and the single customer view that wasn't scoped
- Lifecycle management: dormancy, deletion, and the cascade
- Migrating millions of users without losing them
- Multi-brand rollout: the scenario that breaks architectures
- Pricing opacity: the SSO tax and the MAU trap
- Scaling the user directory itself
- The build-vs-buy trap: identity is bigger than it looks
- The friction-versus-security dial that never stops moving
Featured in
Where SAP Customer Data Cloud appears across CIAM Compass analysis.
FAQ
- What was Gigya?
- Gigya was a B2C CIAM and customer data platform founded in 2006, acquired by SAP in 2017 for $350M, and rebranded as SAP Customer Data Cloud. The original product had strong social login, registration-as-a-service, and consent management; SAP retained the engineering and integrated it into the SAP Customer Experience portfolio.
- Does SAP Customer Data Cloud work outside SAP ecosystems?
- Yes technically, protocols are standard. But the integration story and value proposition are materially stronger for existing SAP Commerce Cloud / SAP CX customers. Greenfield non-SAP projects evaluating against Auth0 or Stytch will usually find those alternatives more practical.
- What does SAP Customer Data Cloud cost?
- Enterprise quote-based via SAP sales; typically among the highest pricing in the CIAM index, with six-figure annual minimums standard. For mid-market evaluation, the entry threshold is disqualifying.
Sources
- SAP Customer Data Cloud product pageaccessed 2026-04-22
- SAP Customer Data Cloud documentationaccessed 2026-04-22
Where to next
What SAP Customer Data Cloud is
SAP Customer Data Cloud is the customer identity platform within SAP's Customer Experience portfolio, originating as Gigya (founded 2006, acquired by SAP in 2017 for $350M). The product covers B2C CIAM, customer data unification (the former Gigya CDP heritage), consent management, preference center, and progressive profiling, sold primarily into existing SAP Commerce Cloud and SAP CX customers.
Where SAP Customer Data Cloud wins
Twenty years of B2C CIAM experience, uncommon depth on consent management, preference center, and customer data unification. Tight integration with SAP Commerce Cloud and the broader SAP Customer Experience portfolio. Comprehensive consent capabilities including purpose-specific consent and audit trails align with regulated-industry compliance.
Where SAP Customer Data Cloud hurts
Enterprise-only commercial structure with very high entry pricing. DX is dated and the SAP integration overlay adds complexity for non-SAP teams. Outside SAP ecosystem the integration story does not justify the cost.
How SAP Customer Data Cloud compares
The closest comparisons are Auth0 vs SAP Customer Data Cloud for the modernization-vs-legacy-enterprise call. For other legacy enterprise CIAM, Ping Identity, ForgeRock, Oracle IDCS, and Akamai Identity Cloud are peers.
Editorial changelog (1 entry)
Routine profile review: capabilities, pricing, and editorial verdict re-verified.