This article is going to cover how you can take your existing Netigate surveys and pull their responses into Lumoa. This assumes you already have a Netigate account and a survey created.
Creating your Netigate API token
The first thing we will need is to create a Netigate API token. This is the identifier that tells Lumoa what company in Netigate you want to pull surveys from. Each Netigate company should have its own unique API token, but multiple Netigate companies can be associated with one Lumoa account.
To create your Netigate API token, go to the Netpanel in Netigate and then use the option for "API Token":
Be sure to copy the token to your clipboard as it will not be visible again!
Putting your API token into Lumoa
Once you have a token generated, log in to Lumoa by going to: https://act.lumoa.me/authorization (maybe bookmark the page, while you are at it 👀).
NOTE: The company you land on when you log in to Lumoa is most likely NOT the one that you want to use the API token for. You will probably have to impersonate into the correct company. Please consult our guide on impersonation for more info.
Assuming you have impersonated into the correct company, go to your Surveys Hub (1) -> Netigate Surveys (2) -> Put in your API Token (3) and then select Set Token:
Connecting to a Survey
Assuming you put in a valid API Token, the page should reload and display all surveys that are associated with your Netigate account. In order to pull data, you need to select an Active survey. Note that you cannot edit a survey or its status from Lumoa - if there is a survey you want to edit or change status for, that would need to be done through Netigate.
Once you have your active survey, click the three dots and then "Connect":
Defining the Survey Fields
When connecting the survey, you will have to choose which fields map over to Lumoa. Note that Lumoa cannot support every survey and question combination that Netigate offers. If there are questions in your survey that Lumoa cannot support, Lumoa will tell you that some questions will be skipped.
Collection | To start, define the collection that you want to bring data to. Please refer to "What is a collection" for more information.
NOTE: Your collection needs to match the metric type that your survey has for best results - dont pull a CSAT survey to an NPS collection |
Main Score | This will determine what question in the Netigate survey Lumoa should use as the main score. The main score is the score that Lumoa will use in its calculation for your overall KPI, Topic Impacts, Insights, and other things. |
Open Ended Question | This is the open text that Lumoa will pull in and analyze for Sentiment, Topics, translations, and more. In general, we recommend the open ended question be related to your main score. If your main score is NPS, then the "open ended question" field should be the customers comment on the NPS score. |
Note that you can pull over multiple open ended questions at the same time, but you will have to specify which collection the response should go to each time. You can use the + button to define additional open ended questions.
Below is an example of the filled out connection screen (without tag mapping):
Tag mapping
Tag mapping allows you to match questions and fields within your survey to existing tags that are already in Lumoa. If you do not currently have any data in the collection you are connecting your Feedback survey to, you can skip this step.
To start tag mapping, select the question or field in your survey that you want to map. In the example below we are selecting "What country are you from?".
Then, select the existing Lumoa value that you want to map to. In the example below, we are going to map all answers to "What country are you from?" to the existing "Region" filter we already have in our collection.
What this will do is make it so that all responses to the question "What country are you from?" will now come in to Lumoa associated with our existing "Region" filter, preventing us from having two different Region tags.
If you select "Import History Data" then Lumoa will pull all responses that have previously been submitted to this survey. If you choose to not pull historic data, Lumoa will only pull future responses that are completed after this integration is finalized.
Once you are done, hit Save and a job will be triggered to pull any existing data and define the flow of your feedback. Depending on the amount of historic data you are pulling, this could take a few hours. You can view the status of the job from the jobs page in Lumoa. All future data will flow into the Lumoa collection you defined, in (mostly) real time.
Get in touch
📧 Do you have any questions or comments about using Lumoa? Please don't hesitate to email us at [email protected].