Qmatic Data Connect Lite
Qmatic Data Connect provides insights into customer journey data.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | AGENT_DEVICE_CONTROLLER_STATUS, AGENT_DEVICE_STATUS, APPOINTMENT, APPOINTMENT_ARRIVAL_STATUS, APPOINTMENT_CREATED_TIME, APPOINTMENT_CUSTOMER, APPOINTMENT_END_TIME, APPOINTMENT_SERVICE, APPOINTMENT_START_TIME, APPOINTMENT_STATUS, BRANCH, CALL_TIME, DAEMON_EVENT_TYPE, DAEMON_STATUS, DAEMON_VERSION, DELIVERED_SERVICE, DELIVERED_SERVICE_TIME, DEVICE_CONTROLLER_EVENT_TYPE, DEVICE_CONTROLLER_STATUS, DEVICE_CONTROLLER_TIME, DEVICE_EVENT_TYPE, DEVICE_STATUS, DEVICE_TIME, DIM_DEVICE_TYPE, DIM_UNIT_TYPE, END_TIME, ENTERED_QUEUE_TIME, ENTRY_POINT, FACT_AGENT_JIQL_EVENT, FEEDBACK_ANSWER, FEEDBACK_RESULT, FEEDBACK_TIME, JIQL_EVENT_TYPE, JIQL_STATUS, JIQL_VERSION, MARK, MARK_TRANSACTION, MARK_TRANSACTION_TIME, MARK_TYPE, QUESTION_TYPE, QUEUE, QUEUE_TYPE, RESOURCE, SERVICE, SERVICE_DELIVERED, SERVICE_POINT, STAFF, STAFF_SESSION, STAFF_SESSION_END_TIME, STAFF_SESSION_OUTCOME, STAFF_SESSION_START_TIME, TIME, VISIT_CALL_TYPE, VISIT_CUSTOMER, and VISIT_TRANSACTION_OUTCOME tables. |
| History mode | ||
| Custom data | ||
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | check | AGENT, AGENT_DAEMON_EVENT, APPOINTMENT_CANCELLED_DATE, APPOINTMENT_CREATED_DATE, DATE, DEVICE, DEVICE_CONTROLLER, DEVICE_CONTROLLER_EVENT, DEVICE_EVENT, FEEDBACK_DATE, MARK_TRANSACTION_DATE, OUTCOME, UNIT, VISIT, VISIT_TRANSACTION, and WORK_PROFILE tables. |
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Supported deployment models
We support the SaaS and Hybrid deployment models for the connector.
NOTE: You must have an Enterprise or Business Critical plan to use the Hybrid Deployment model.
Setup guide
Follow our step-by-step Qmatic Data Connect setup guide to connect Qmatic Data Connect with your destination using Fivetran connectors.
Sync overview
To capture new records, we incrementally sync the following tables and their child tables:
AGENTAGENT_DAEMON_EVENTAPPOINTMENT_CANCELLED_DATEAPPOINTMENT_CREATED_DATEDATEDEVICEDEVICE_CONTROLLERDEVICE_CONTROLLER_EVENTDEVICE_EVENTFEEDBACK_DATEFEEDBACK_QUESTIONMARK_TRANSACTION_DATEOUTCOMEUNITVISITVISIT_TRANSACTIONWORK_PROFILE
To capture updates and deletes, we re-import the following tables in every sync.
AGENT_DEVICE_CONTROLLER_STATUSAGENT_DEVICE_STATUSAPPOINTMENTAPPOINTMENT_ARRIVAL_STATUSAPPOINTMENT_CREATED_TIMEAPPOINTMENT_CUSTOMERAPPOINTMENT_END_TIMEAPPOINTMENT_SERVICEAPPOINTMENT_START_TIMEAPPOINTMENT_STATUSBRANCHCALL_TIMEDAEMON_EVENT_TYPEDAEMON_STATUSDAEMON_VERSIONDELIVERED_SERVICEDELIVERED_SERVICE_TIMEDEVICE_CONTROLLER_EVENT_TYPEDEVICE_CONTROLLER_STATUSDEVICE_CONTROLLER_TIMEDEVICE_EVENT_TYPEDEVICE_STATUSDEVICE_TIMEDIM_DEVICE_TYPEDIM_UNIT_TYPEEND_TIMEENTERED_QUEUE_TIMEENTRY_POINTFACT_AGENT_JIQL_EVENTFEEDBACK_ANSWERFEEDBACK_RESULTFEEDBACK_TIMEJIQL_EVENT_TYPEJIQL_STATUSJIQL_VERSIONMARKMARK_TRANSACTIONMARK_TRANSACTION_TIMEMARK_TYPEQUESTION_TYPEQUEUEQUEUE_TYPERESOURCESERVICESERVICE_DELIVEREDSERVICE_POINTSTAFFSTAFF_SESSIONSTAFF_SESSION_END_TIMESTAFF_SESSION_OUTCOMESTAFF_SESSION_START_TIMETIMEVISIT_CALL_TYPEVISIT_CUSTOMERVISIT_TRANSACTION_OUTCOME
Schema information
This schema applies to all Qmatic Data Connect connectors.
Explore Qmatic Data Connect schema ERD