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.

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!

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 👀).

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:

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" or "AutoConnect":

Connect is the way that we recommend you create integrations for Feedback. Its a bit more complicated, but the steps are outlined in the guide below. Using the normal Connect allows you to create a more customized way of bringing in the data, that likely closer aligns with the customers needs and wants.

AutoConnect is the way we are going to be creating accounts for Netigate Results customers. The idea is that these accounts require no additional input. Using AutoConnect will:

When connecting the survey, you will have to choose which fields map over to Lumoa. Note that Lumoa should be able to support every question type in Feedback. If there are questions in your survey that Lumoa cannot support, Lumoa will tell you that some questions will be skipped. In which case, please contact Netigate Support so we can investigate the questions that cannot be pulled.

Note that you can pull over multiple open ended questions at the same time. In the GIF below, I make one integration for "what does garen corp do well" and another integration for "what does garen corp do poorly". These integrations can come either to the same collection, or to a different one - its your choice.

In the image below, we are selecting multiple open ended questions within the same integration. In this case, the system will check for the first open ended answer it encounters.

The use case is that Netigate NPS templates have three different open ended questions for detractor, neutral, promotor, but a user can only response to one of them (based on the NPS score they leave). So the integration will look for the one the user did respond to, pull that, and then go to the next user.

If you want to combine each open ended question, so that there is ONE response, containing all open text, you can do so with the "Combine text fields into one" Checkbox. In the below example, we are taking two open ended questions and combining them into one response:

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.

Statis tags are Tags that you want to be applied to every feedback that gets pulled through this survey. Static Tags are added by the system, once the integration has been started - these tags do not have to exist in your current survey responses from Feedback, nor do they have to exist with the current data in Lumoa.

Static Tags are formatted using tagName and tagValue. For example, tagName Region with and tagValue Japan. If this Static Tags is applied, all responses pulled through this integration will come over with Region = Japan as one of their tags, in addition to any other tags that may have been pulled through the URL of metadata of the survey.

In the GIF below, I create a statis tag "Country = Germany" so when I send this to my German customers, all responses to the survey will automatically come over with the tag "Country = Germany":

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.

📧 Do you have any questions or comments about using Lumoa? Please don't hesitate to email us at [email protected].