Firebase Analytics:
Presently we cannot identify an analytics stream for a coach and for our scale of support and operations, this is a significant loss of value.
CoachID's are salesforce ID's and do not include any identifiable information outside salesforce, so it is safe to use this method of event identification and segmentation.
FIREBASE/APP REQUIREMENTS:
Sessions in Analytics associate with the correct CoachID
Major events include the CoachID for more flexible reporting
Salesforce Reporting:
Presently all metadata related to Coach App and other "external" apps are identified as "Salesforce Integration User."
We would like to:
SALESFORCE SYSTEM REQUIREMENTS:
replace identifiers, where possible, with the Salesforce ContactID of the Coach/user
add, if necessary, metadata to store the ContactID of the Coach/user in a way that allows for reporting on this ID
ACCEPTANCE CRITERIA:
Demonstrate a report in the above systems showing:
App activity, by Coach (in Google Analytics)
Attendance, Contact, Enrollment, Session record activity (in Salesforce)
Firebase Analytics: Presently we cannot identify an analytics stream for a coach and for our scale of support and operations, this is a significant loss of value. CoachID's are salesforce ID's and do not include any identifiable information outside salesforce, so it is safe to use this method of event identification and segmentation. FIREBASE/APP REQUIREMENTS:
Salesforce Reporting: Presently all metadata related to Coach App and other "external" apps are identified as "Salesforce Integration User." We would like to:
SALESFORCE SYSTEM REQUIREMENTS:
ACCEPTANCE CRITERIA: Demonstrate a report in the above systems showing: