How to integration Qualtrics EX with SuccessFactors to distribute Pulse surveys | XM Community
Skip to main content

We plan to build an EX platform with the goal of initially establishing a Pulse program. Subsequently, 360 feedbacks are also on the plan. But let's focus on Pulse Surveys first. 

The employee data should be integrated from SuccessFactors.

I've searched the community posts and documentations for answers, but unfortunately haven't found a clear process model for a project like ours - especially on the integration part. Therefore, I would like to  share my thoughts and hope for the evaluation of experienced EX colleagues. 

My main question to kick-off is: What is the best way to integrate SuccessFactors employee data to Qualtrics? 

I have found two ways to do this: 

(1) Pull approach: regular workflow (e.g. daily) to extract data via predefined SuccessFactors action.

https://www.qualtrics.com/support/de/survey-platform/actions-page/etl-workflows/data-extractor-tasks/extract-data-from-successfactors-task/?rid=cookie&prevsite=en&newsite=de&geo=&geomatch=

Combined with workflow action to store data in EX Directory

https://www.qualtrics.com/support/de/survey-platform/actions-page/etl-workflows/data-loader-tasks/load-users-into-ex-directory-task/?rid=cookie&prevsite=en&newsite=de&geo=&geomatch=

(2) Push approach: Send employee data to a Qualtrics Import Automation endpoint via web service.

https://www.qualtrics.com/support/de/employee-experience/directories/employee-directory-import-automations/?rid=cookie&prevsite=en&newsite=de&geo=&geomatch=

I tried to compare those approaches and would go for (1) just because it seems more simple, however, not sure if I missed or missunderstood something because I actually read more often about (2). Maybe one of those approaches also blocks us from usage in Pulse and/or 360 programs? 

(1) Pull (2) Push

✅ Easy-to-use pre-configured action

❌ Usage only for SuccessFactors (which is fine for us if the employee data does not have further origins)

✅ Flexibility in regards to data origin since the data could be pushed from anywhere including SuccessFactors

✅ More flexibility on the fields because you can also provide transactional data in addition to employee metadata (person and embedded data fields)

❌ Requires custom webservice calls and scheduling to push the data to the import automation

 

Actually, there would also be a (3) option to just set up some complete custom integration using the POST participants EX API, right?

https://api.qualtrics.com/fc78c0194ee54-import-participants

The structure of the Pulse program itself is already documented in detail on the subpages linked below. Therefore no questions on that so far. 

https://www.qualtrics.com/support/de/employee-pulse/creating-a-pulse/?rid=langMatch&prevsite=en&newsite=de&geo=&geomatch=

However, one thing that is not 100% clear to me is the differentiation between the EX directory and the XM directory. As I understood, the EX directory needs to contain the participants of the EX projects (such as Pulse & 360). Furthermore, the EX directory also allows you to define relationships that are relevant for the 360 program. And the EX directory is completely separated from the XM directory.

But what does the XM directory contain then?

Best
Christian

For EX project we use EX directory as it is integrated with different EX projects. So all details related to employees is stored in EX directory whereas any customer data are stored in XM directory since the mailiing lists in XM directory is used in cutomer experience.


I wanted to give an update to my question and close the topic. We decided for option 3 and went with a custom integration implemented on SAP Cloud Platform Integration. After several discussions, we decided for the custom approach due to limitations of the standard. 

We have a complex organizational setup on SAP SuccessFactors which requires custom coding in order to bring the read the org hierarchy dynamically and import it to Qualtrics contact metadata. We used below API to create contacts in the Employee Directory: 

https://api.qualtrics.com/fc78c0194ee54-import-participants

Additionally, we went with a custom iFlow to fulfill the requirements for data deletion based on GDPR requirements. 


Leave a Reply