Enriching Adobe Analytics from Medallia Experience Cloud
Because not all data is exposed to the property or available in real time, a backend integration with Experience Cloud can be set up, depending on what data needs to be sent to Adobe Analytics.
| On-site integration | Backend integration | |
|---|---|---|
| Number of eVars | Depends on tracked real-time questions | 1 (see Limitations) |
| Metadata (e.g., Feedback UUID, Form Type) | Yes | Yes |
| Scale questions | Yes | Yes |
| Non-scale questions | No | Yes |
| Verbatims/ raw comments | No | Yes |
| Text Analytics data | No | Yes |
| Calculated data | No | Yes |
Solution design
Limitations
The following limitations exist regardless of the selected integration method:
An eVar can contain up to 30 properties that will sync in data points from Experience Cloud. In cases when more than 30 data points are required to be synched, an additional eVar will be required.
Events are detected in real time on the property, but data will only show in reporting when Adobe Analytics has finished processing it. The duration can vary depending on what method is used as well as a large range of other factors.
Only high-level fields can be set easily (i.e., eVars, props, list vars, and events). This makes real-time tracking of scores either very resource intensive (i.e., one field per question) or reliant on parsing rules (i.e., data concatenated into one field with a parsing rule to redistribute values in sub-fields in Analytics). In that sense, backend integrations are more efficient to send survey data when real-time actions are not required. Only the UUIDs are required for on-site integrations.
When a customer selects a '0 value, that value is transformed into 'zero' for Adobe Launch and Analytics. This mitigates support challenges related to '0' values.
