This feature allows you to create personalized, trackable links for each transaction, enabling targeted survey distribution based on individual customer interactions. By utilizing transaction metadata, every customer receives a unique link tailored to their specific experience.

These unique transaction links can be exported for distribution, while response data can be seamlessly analyzed through Sprinklr Customer Feedback Management’s analytics platform.

Prerequisites

Access to the Distribution module would require View Distribution and Edit Distribution permissions at the Survey Level.

Setting Up Personalized Links Using Transactions

The Transactions Import distribution type in Personalized Links enables you to create a traceable link for each individual transaction, complete with the relevant metadata.

After configuration, unique links for every chosen transaction can be exported and utilized for separate distribution. The profile data facilitates survey customization through placeholders and is accessible with the responses for reporting purposes, offering valuable additional context.

1. Navigate to the Customer Feedback Management persona app and open a Survey and navigate to Distribution.

2. Select Personalised Links and click Create Now.

3. Click Transactions.

4. Go to the Distribution Details page and fill in the details:

   1. Name: Add a meaningful name to the distribution details.

   2. Description: Add a description to the detail (Optional).

   3. Conversational Survey: Toggle this option to allow all created links to offer a chat-based survey experience. Please note that this setting cannot be reversed after the links are generated.

   4. Start Date and Time: Indicate a start date and time, and optionally, an expiration date for the survey link. After the expiration date has passed, the link will become inaccessible.

      Example: Submissions for the survey will be accepted starting January 24th, 2025, and will conclude on March 31st, 2025.

      Any user who visits the link prior to January 24th will encounter the "Paused" special page, while those accessing it after March 31st will be directed to the "Expired" special page.

   5. Expiration Type: Select the expiration type out of the two options:

      1. Static: Establish a specific date and time for expiration, after which the survey link will become inaccessible.

      2. Dynamic: Set the survey to expire based on the time it is sent out, ensuring that all recipients share the same duration for responding.

   6. End Date and Time: Choose an end date and time, and once that expiration date and time is reached, the link will become inaccessible.

   7. Limit submissions per respondent: Activate this feature to limit the number of submissions a recipient can make for the survey. By default, there is no restriction on the number of submissions per user.

      1. Reset Limit After Interval : Decide whether to restore the previously mentioned submission limit after a designated time period (Optional).

         Example: Each participant in the survey is permitted to submit their response once a week. For instance, a respondent can submit their answer on January 24th and then again on January 31st or later, but they are restricted to one submission each week.

         The “reset limit” feature is optional, allowing you to restrict submissions to just one response, thus stopping any additional submissions after the initial one.

         ​

   8. Add Transactions: You have two options to add transactions:

      ​

      1. Import New: As another option, upload new transactions straight to the system.

         ​

      2. Choose Existing: Select a Transaction Group that has already been shared with the project.

         ​

         Let's explore the procedure for creating a Transaction File for Import. To save transaction data in Sprinklr, you have the option to import a file that holds your data. This guide outlines the proper formatting for your file to ensure a successful import.

         1. Template File: Sprinklr provides a ready-to-use template to streamline transaction imports and accelerate your setup process.

            ​

            1. To obtain the template, select "Download a Sample Template" while creating the transaction.

            2. Launch the template in a spreadsheet application like Excel and modify it with your transaction information.

            3. Please adhere to the guidelines below regarding the mandatory and suggested fields. Please fill all the mandatory fields:

               1. Required Fields

                  1. User ID: A distinctive identifier for the user.

                  2. Profile Channel: The channel linked to the user profile. This can be one of the following:

                     1. Email

                     2. SMS

                     3. WhatsApp

                     4. Source Agnostic (if none of the above apply).

               2. Recommended Fields: Although it's not mandatory, it is highly advisable to include these fields:

                  1. Transaction Time: Records the date and time of the transaction.

                  2. First Name: Input the user's name.

                  3. Last Name: Input the surname of the user.

                  4. Transaction Field: Any extra metadata required for the transaction can be found. Please consult this article for instructions on how to create Transaction Fields.

                  Note: You won't be able to import if the column labeled "Profile Channel" is missing from the sheet.

5. Click Next and go to Import from Excel page.

6. Once the file is complete, you can proceed to import the transactions by clicking Next.

   Mapping Transaction Fields and Importing

   ​

   1. ​​Go to Column Mapping: Map each column in your Excel file to the corresponding Transaction Fields in Sprinklr, or create new fields directly as needed.

   2. Profile ID: Define your Profile ID. On the following screen, align the columns from your Excel file with the corresponding Transaction Fields.

      1. Profile ID / User ID Field: Please choose the Excel column that holds the customer's identifying details, including a mobile number, email address, or unique reference ID.

      2. If a profile associated with the given User ID is already present, the metadata will be incorporated into that profile.

      3. If there is no existing profile, a new one will be generated.

         Note:

         • Distinction Between Defining and Mapping the Profile ID/User ID.

           • Defining the User ID Field (Step 1):Recognizes the customer profile and is utilized to create or modify profiles.

             

           • Mapping the User ID to a Transaction Field (Step 2): Retains the User ID specifically for each transaction.

             

             The second step for the User ID is not mandatory.

         • Make sure that all other necessary transactional metadata is appropriately mapped.

         • It is unnecessary to map the "Profile Channel" field because it is retrieved directly.

   3. After the mapping is finished, click on Create to import the transactions and generate the related survey links.

   4. A new record will be included in the Distributions Record Manager, and you will get a notification that allows you to download a CSV file containing the links.

      

​

​