Third-party IDs are unique codes to allow customers to identify responses using their own references.
Vocads assigns a unique, random-based ID to each conversation that happens through our Widget UNI. These IDs are immutable (they never change) and are guaranteed to be unique across the system. A typical Vocads conversation ID looks like this: ef1c49b2-e5cb-4a23-ae2c-120000f8952a and it will be highlighted in the raw data page at the end of the table.
In addition to Vocads Conversation IDs, the system also allows our customers to associate each conversation with an ID of their choosing.
Discussing now a use case in the survey field
The Third-party ID feature offered by Vocads can help you keep a relation between Vocads’ Conversation IDs and your internal system references using GET parameters. Before we start, make sure that you only use the v_ref parameter throughout the different steps
- Prepare the reference of the data from your database you would like to use like customer reference or any desired data
So our parameter to identify the data will be:
v_ref=customer_reference or v_ref=ANY_DATA
2. Now add the parameter to your first URL under this format
https://my-site.com/vocads-survey/ + ? + v_ref=ANY_DATA
Example : https://my-site.com/vocads-survey?v_ref=client_id_42
The third-party ID will be permanently be associated with the conversation
In case the client will use a redirection node when building a Vocads campaign, the parameter will be passed on the URL used in the node as seen on the illustration.
Example:
Data wise, on Vocads side you’ll be able to retrieve the value of the parameter used in a conversation which will help to match the conversation ID with the parameter used.
