1.Processing shall be lawful only if and to the extent that at least one of the following applies:a. The data subject has given consent to the processing of his or her personal data for one or more specific purposes.b. Processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract;c. Processing is necessary for compliance with a legal obligation to which the controller is subject;d. Processing is necessary in order to protect the vital interests of the data subject or of another natural person;e. Processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller;f. Processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by theinterests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child.
1.Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data. 2.The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consentbefore its withdrawal. Prior to giving consent, the data subject shall be informed thereof. It shall be as easy to withdraw as to give consent
1.The data subject shall have the right to object, on grounds relating to his or her particular situation, at any time to processing of personal data concerning him or her whichis based on point (e) or (f) of Article 6(1), including profiling based on those provisions. The controller shall no longer process the personal data unless the controllerdemonstrates compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject or for the establishment, exercise ordefence of legal claims. 2.Where personal data are processed for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning himor her for such marketing, which includes profiling to the extent that it is related to such direct marketing. 3.Where the data subject objects to processing for direct marketing purposes, the personal data shall no longer be processed for such purposes. 4.At the latest at the time of the first communication with the data subject, the right referred to in paragraphs 1 and 2 shall be explicitly brought to the attention of the datasubject and shall be presented clearly and separately from any other information
1.Taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing as well as the risks of varying likelihood andseverity for rights and freedoms of natural persons posed by the processing, the controller shall, both at the time of the determination of the means for processing and atthe time of the processing itself, implement appropriate technical and organisational measures, such as pseudonymisation, which are designed to implement dataprotection principles, such as data minimisation, in an effective manner and to integrate the necessary safeguards into the processing in order to meet the requirements ofthis Regulation and protect the rights of data subjects. 2.The controller shall implement appropriate technical and organisational measures for ensuring that, by default, only personal data which are necessary for each specificpurpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage andtheir accessibility. In particular, such measures shall ensure that by default personal data are not made accessible without the individual’s intervention to an indefinitenumber of natural persons.
CONSENT
The data subject has given consent to the processing of his or her personal data for one or more specific purposes
CONTRACTUAL_PERFORMANCE
“Processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract
LEGAL_OBLIGATION
“Processing is necessary for compliance with a legal obligation to which the controller is subject
PUBLIC_INTEREST_OR_EXERCISE_OF_OFFICIAL_AUTHORITY
“Processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller
LEGITIMATE_INTEREST
“Processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child. Shall not apply to processing carried out by public authorities in the performance of their tasks.
$set_user_choice
name and a set of metadata. It will then be computed and stored. You can also create choices via API.$set_user_choice
events from the $processing_token
property$set_user_choice
events from the $ts
property$set_user_choice
events from the $choice_acceptance_value
property$set_user_choice
events from the $choice_source_token
property. Allowing a choice update will depend on the source weight (see below).vec:89090939434
$set_user_choice
event (pixel or /user_activities API): we copy the identifiers from the activity origin (after interpreting those within events if pixel)/user_choices
API, we consider those in the request payload. If no identifier is defined in the request payload, we copy those in the URL$set_user_choice
event (pixel or /user_activities API): we copy the identifiers from the activity origin (after interpreting those within events if pixel)/user_choices
API, we consider those in the request payload. If no identifier is defined in the request payload, we copy those in the URL$set_user_choice
event (pixel or /user_activities API): we copy the identifiers from the activity origin (after interpreting those within events if pixel)/user_choices
API, we consider those in the request payload. If no identifier is defined in the request payload, we copy those in the URL$set_user_choice
event (pixel or /user_activities API): we copy the identifiers from the activity origin (after interpreting those within events if pixel)/user_choices
API, we consider those in the request payload. If no identifier is defined in the request payload, we copy those in the URL$set_user_choices
events from the events custom properties$set_user_choice
events and creates a user choice using some fields of the user activity.$set_user_choice
events$set_user_choice
events from external sources (CRM files, server-side CMPs, ...).UPSERT
of user activities of type SITE_VISIT
and APP_VISIT
. To achieve this, you link a list of processing activities to a channel. The upsert of data will be allowed for a user if he has allowed at least one of the selected processing activities. User activities of types TOUCH
, EMAIL
and DISPLAY_AD
are not covered yet.UPSERT
of user profiles. This is done by linking a list of processing activities to a compartment. The upsert of data will be allowed for a user if he has allowed at least one of the selected processing activities.USER_LIST
), the decision to upsert or drop is taken just before saving it into the datamart. In the case of user activities, the decision takes into account the presence of a $set_user_choice
event in the activity. If a user changes his choices, new data upserts will be blocked but already captured data is kept and follows the standard cleaning rules.USER_QUERY
segments, the segment query is automatically updated with conditions on the user choices to include only users with compatible choices. If a user changes his choices, the user will exit the segment as he doesn't match the query anymore?$creation_ts
is kept active on the user point survivor, the other one being added to the change log.processing_id
, choice_ts
, creation_ts
and choice_acceptance_value
.$choice_source_id
, relating each choice to a reference table that can be created by mediarithmics for each client.$set_user_choice
events, use $choice_source_token
. Il will be translated by the platform in to a $choice_source_id
/user_choices
API, use directly the $choice_source_id
$set_user_choice
event will overwrite the existing one if and only if it has a choice source with a weight equal or superior to the existing one