Technical integration

This article shows you how to integrate the data subject right request widget into a web page

Purpose

The data subject right request widget allows you to automatically collect from a page of your site data subject right request of various types (deletions, modifications, rectifications...)

The widget is integrated to the dastra javascript SDK.

Prerequisites

In order to set up thedata subject right request widget, you need an API public key: read the documentation or go directly to the API key management page

Setting up the widget in the dedicated interface

To start with, you need to set up the widget in the rights exercise widget management panel:

Here is a simple example of how to integrate the widget (in popup mode with an open button):

How to force the language of the form?

By default, the browser language will be taken. If the language is not available in the widget translations, the default language will be selected automatically. You can force the current language of the widget by adding the data-lang property to the div where the form will be displayed.

In this example, the Italian language will be selected by default (if available)

How to automatically send form values to the widget?

You can automatically send form values to the widget by using the dastra.push method. This method allows you to set various properties of the form widget, such as user identifiers and personal data fields.

Here's a simple example of how to pass additional user information to the form widget:

Ensure you replace the placeholder values ('Rossi', 'Mario', etc.) with the actual user data retrieved from your system. This approach helps personalize the user experience by pre-filling form fields with known data.

In the specific case of a custom userId (in session cookie for example), you can do it as following :

You can replace the name of the refId column with the following property name :

  • refId : the unique identifier of the user in your system (customerId, sessionId...). This column is not visible and will be not accessible to the customer.

  • familyName

  • givenName

  • email

  • city

  • zipCode

  • countryCode

  • address

  • phoneNumber

  • message

  • additionalDatas

*For the specific case of custom fields, you must reference the name additionalDatas :

Additional fields will be automatically merged

Sending parameters using page mode

It is also possible to pass these parameters using querystring parameters, just prefix the parameter name with dsr_ :

Last updated

Was this helpful?