A data export is a file-based way to receive your guest experience data when an API integration is not practical. We will periodically assemble the agreed data into a CSV or Excel file and place it in a secure shared location (such as SFTP) for you or your supplier to collect.
The Key Results API is our preferred method of sharing data. Exports can be made available where your teams cannot support an API call; just ask your HGEM contact.
What are the benefits?
- Data in your systems
Receive guest experience data in a structured file that you can load into the systems you already use. - Visit scores and feedback in one place
Include visit scores, recommend ratings, comments, and related fields so teams can analyse performance or support guests in your own tools. - Combine with your other data
Use the export alongside data from other sources.
There are two main export shapes:
- Visit level (one row per visit): suitable for most scenarios.
- Question level (one row per question): sometimes used for BI exports.
Field lists can be tailored. The recommended fields below are a typical starting point; other available fields can be included.
Visit level
- Visit ID
- Visit type (for example Online Feedback, Social Review)
- Visit source (for example Google, Pay at Table)
- Visit date and time (for reviews, this matches the date added)
- Date added (date/time added in HGEM)
- Branch code and branch name (your site identifiers)
- Visit score (out of 100)
- Recommend score (out of 10)
- NPS classification (Promoter, Neutral, Detractor)
- Guest ID (where supplied to HGEM)
- Marketing consent and reply consent
- Email (only where consent allows)
Additional question-level fields
- Question subject (short question label, for example Cleanliness)
- Answer (selected answer, for example Yes, 5, Satisfactory)
- Question score (out of 100; actual score and max score can be provided instead if preferred)
- Comments (against a question)
Getting started
Speak to your HGEM contact. To set up an export, we will need you to confirm:
- The data fields to include
- How often the file should be produced
- Credentials and location for where the file should be placed
If your teams can support an API integration, see Accessing your data: Key Results API — that is our preferred method.