User Journey across products

*Following - we have this use case (PX in our product, community and academy) on our Q4/Q1 roadmap as well.

Hey ​@Alistair FIeld! Since you're using SSO across all three, your IdP (Okta or Azure AD) is actually the key here. It's the one system that sees every user regardless of which product they're logging into, so it's the right place to handle the bridging.

The approach that works well:

Use email as your canonical cross-product identifier. It's already present in all three systems, so it becomes your join key. When you make the PX Identity call, use email as the id field consistently across CC, Skilljar, and your product.

Let the IdP pass additional attributes at login. You can configure it to send something like internalUserId alongside email whenever a user logs into any of the three products. This way PX can pick up a consistent identifier without you needing to do any custom middleware work or rely on Salesforce (which, as you noted, won't have full coverage anyway).

For Skilljar specifically: create a Signup Field that matches the IdP attribute name exactly, including casing. Skilljar will then auto-populate that field on every SSO login automatically, no manual steps needed. One thing to watch: if the field label doesn't match the IdP attribute name precisely (case-sensitive), it won't populate at login.

This approach keeps things clean: email is the join key, PX gets a consistent identifier across all three surfaces, and the IdP handles the attribute bridging natively.

Hope this helps! 😊

I don’t see email in inSidedData.user. How do you pass user.email in the Identify call from CC?

Great question ​@rschlette!

As the answer can vary depending on your specific CC setup and SSO configuration, I'd recommend raising a ticket with Support so the team can take a look at your environment and give you accurate guidance on passing the right attributes through the Identity call 😊