2
Gainsight Admin Cert JO questions with accurate answers || || || || || || ||
JO Email Attachment limit - ✔✔2MB
|| || || || ||
4 program models - ✔✔NPS® Survey
|| || || || ||
Customer Satisfaction Survey || ||
Generic Survey ||
Email Chain ||
What are the JO Permissions? - ✔✔1. Design
|| || || || || || ||
2. Distribute
||
3. Analyze
||
4. Admin
||
Design - ✔✔Will have access to Properties, Design
|| || || || || || ||
Distribute - ✔✔Will have access to Sync/run Power lists, Manual run/schedule Outreaches,
|| || || || || || || || || || || ||
and Publish/Schedule the programs
|| || ||
Analyze - ✔✔Will have access to view Outreach Analytics, Individual program analytics
|| || || || || || || || || || || ||
from program page and Program Analytics (J360).
|| || || || || ||
Admin - ✔✔By default, the users of "Admin" type will have Journey Orchestrator Module
|| || || || || || || || || || || || || ||
Admin enabled with Delete permissions (along with Design, Distribute and Analyze
|| || || || || || || || || || ||
permissions).
, 2
Events Framework - ✔✔Gainsight Events Framework allows you to create events, which
|| || || || || || || || || || || ||
can be used in Programs and Rules Engine.
|| || || || || || || ||
Events can be defined as triggers that are a result of some other activity.
|| || || || || || || || || || || || ||
Publisher - ✔✔Publisher=App Sender of the event
|| || || || || || ||
For example: In the CSAT Survey model for Programs, Zendesk or Salesforce can be the
|| || || || || || || || || || || || || || || ||
publisher of the case closure event for every case that is closed.
|| || || || || || || || || || ||
Subscriber - ✔✔Subscribers= Programs and Rules|| || || || ||
Subscribers are the processing entities/applications that decide which action should be
|| || || || || || || || || || ||
taken when an event occurs. Gainsight controls which applications can act as available
|| || || || || || || || || || || || ||
subscribers to the events sent by the publishers. Programs and Rules are the available
|| || || || || || || || || || || || || ||
subscribers.
Topic and Event; limit - ✔✔Topic vs. Event:
|| || || || || || || ||
Topics can be defined as a logical separation between similar events.
|| || || || || || || || || || ||
Events are defined within a Topic and represent a specific occurrence.
|| || || || || || || || || || ||
Topic = Zendesk Tickets
|| || ||
Events = Tick Closed; Ticket Reopened
|| || || || ||
Topic Max = 20 || || ||
Gainsight Admin Cert JO questions with accurate answers || || || || || || ||
JO Email Attachment limit - ✔✔2MB
|| || || || ||
4 program models - ✔✔NPS® Survey
|| || || || ||
Customer Satisfaction Survey || ||
Generic Survey ||
Email Chain ||
What are the JO Permissions? - ✔✔1. Design
|| || || || || || ||
2. Distribute
||
3. Analyze
||
4. Admin
||
Design - ✔✔Will have access to Properties, Design
|| || || || || || ||
Distribute - ✔✔Will have access to Sync/run Power lists, Manual run/schedule Outreaches,
|| || || || || || || || || || || ||
and Publish/Schedule the programs
|| || ||
Analyze - ✔✔Will have access to view Outreach Analytics, Individual program analytics
|| || || || || || || || || || || ||
from program page and Program Analytics (J360).
|| || || || || ||
Admin - ✔✔By default, the users of "Admin" type will have Journey Orchestrator Module
|| || || || || || || || || || || || || ||
Admin enabled with Delete permissions (along with Design, Distribute and Analyze
|| || || || || || || || || || ||
permissions).
, 2
Events Framework - ✔✔Gainsight Events Framework allows you to create events, which
|| || || || || || || || || || || ||
can be used in Programs and Rules Engine.
|| || || || || || || ||
Events can be defined as triggers that are a result of some other activity.
|| || || || || || || || || || || || ||
Publisher - ✔✔Publisher=App Sender of the event
|| || || || || || ||
For example: In the CSAT Survey model for Programs, Zendesk or Salesforce can be the
|| || || || || || || || || || || || || || || ||
publisher of the case closure event for every case that is closed.
|| || || || || || || || || || ||
Subscriber - ✔✔Subscribers= Programs and Rules|| || || || ||
Subscribers are the processing entities/applications that decide which action should be
|| || || || || || || || || || ||
taken when an event occurs. Gainsight controls which applications can act as available
|| || || || || || || || || || || || ||
subscribers to the events sent by the publishers. Programs and Rules are the available
|| || || || || || || || || || || || || ||
subscribers.
Topic and Event; limit - ✔✔Topic vs. Event:
|| || || || || || || ||
Topics can be defined as a logical separation between similar events.
|| || || || || || || || || || ||
Events are defined within a Topic and represent a specific occurrence.
|| || || || || || || || || || ||
Topic = Zendesk Tickets
|| || ||
Events = Tick Closed; Ticket Reopened
|| || || || ||
Topic Max = 20 || || ||
