Secure BFF and custom-object capture
The PWA first stores participation and campaign data securely in a Commerce Cloud custom object.
Success Story
From commerce contact to actionable customer knowledge
A large Austrian supermarket chain connects Salesforce Commerce Cloud with Data Cloud – now Data 360 – to create a reliable foundation for personalized customer experiences.
Customer data from the online shop, forms, campaigns, and checkout is captured securely through the BFF and transferred to Salesforce Data Cloud in a structured, batched, and traceable process. Commerce remains the system of record for transactions and shopping experiences; Data Cloud adds a 360-degree view of contacts, consent, and interactions.
Commerce and Data Cloud integration
Solution overview
Decoupled batch ingestion
A configurable job maps participation, profile, contact-point, consent, and campaign data to Data Cloud.
Business Manager reporting
The Data Cloud Query API enables campaign and participation analysis in the familiar commerce environment.
Stable identities and repeatability
Deterministic IDs, normalized email addresses, dry runs, batches, and controlled logs support idempotent operations.
Secure authentication
JWT bearer flow, token exchange, short-lived tokens, and protected configuration keep credentials out of code and browsers.
Concrete use cases
Make campaigns measurable
Participation is linked to campaign, form, contact point, consent, and profile for reliable audience analysis.
Improve consent and contact quality
Identity, contact point, and consent are kept distinct and made usable for compliant communication.
Connect commerce data with customer context
Participation, campaign, contact point, and person form an actionable path toward segments and activation.
Analyze checkout and payment abandonment
As an extension, normalized checkout and payment events can be analyzed without transferring sensitive payment data.
Technical implementation
Step 1
Commerce as trusted transaction context
PWA, API client, BFF, application service, and custom-object service form a clearly bounded server-side chain.
Step 2
Configurable integration job
Batch size, limits, object keys, dry run, verbose logging, source system, and locale control ingestion runs.
Step 3
Operational safeguards
Timeouts, circuit breakers, disabled communication logs, rate limits, and secret-free diagnostics support operations.
Step 4
Scalable foundation
The architecture can grow to product interest, coupon, loyalty, service, and later Data Cloud activation use cases.
Connect commerce and customer data more effectively?
We support integration architecture, Data Cloud contracts, secure BFF flows, and the controlled evolution of data-driven commerce processes.
Discuss this story