Overview
There are different kinds of Survey IDs.
Survey Group ID
The Survey Group ID is what is shown in the URL when you edit a survey:
This survey has a Survey Group ID of 132.
Survey ID (Survey Channel ID)
Survey ID is the ID of the channel within some survey group. In the scope of VoC Feedback terminology, it was previously called Survey Channel ID, but later in the article and in the further communication, it is referred to as Survey ID. This is the ID you need to use in import files. Survey Group ID might sometimes be the same as one of the Survey IDs.
This survey has 4 Survey IDs: 4647, 4650, 4651, 4649. Currently, you can use any Survey ID as a survey identifier in the import file.
If you supply just the Survey ID in the import file, this means that you automatically reference a survey by its Channel ID and by the channel this ID belongs to.
You can also supply any Survey ID from any channel in a single survey and then reference a specific channel in that survey by specifying it additionally to the Channel ID in the same row in the import file.
To reference to WEB channel in the example given above you can use one of the three ways:
SURVEY_ID;CHANNEL
4647
4650;WEB
4651;WEB
4649;WEB
Explanation:
In the first case, we find the survey by Survey ID and since it's a WEB channel we don't need to define it implicitly. However, if you will specify WEB
in CHANNEL
column in this case (which means you're referencing to the same channel twice), the import will still succeed.
In the second case, we find the survey by Survey ID of the SMS channel and additionally reference WEB channel by its name in the second column.
In the third case, we find the survey by Survey ID of the IVR channel and additionally reference WEB channel by its name in the second column.
In the fourth case, we find the survey by Survey ID of the DIGI channel and additionally reference WEB channel by its name in the second column.
In all four cases we will reference to the same channel of the same survey (WEB channel with Survey ID 4647).
Comments
0 comments
Article is closed for comments.