Cleaning rules

Cleaning rules define how each datamart manages the deletion of user data. They can apply to two different user objects: profiles and events.

When an object enters the datamart, mediarithmics computes the expiration timestamp of this object based on the different cleaning rules that can be applied. This expiration timestamp is part of the object properties, and can't be modified. That means cleaning rules are non-retroactive: changing the rules will only have an effect on future incoming events and profiles.

  1. A user profile or user event enters the datamart

  2. Which cleaning rules apply to it?

  3. Based on the cleaning rules and the priority between them, compute the expiration timestamp of the object

  4. Store the expiration timestamp in the object

An event or profile expires if it hasn't been modified before the expiration timestamp. In details:

  • For profile: last modification timestamp field ($last_modified_ts for profile) is checked against expiration timestamp field.

  • For event: since an event cannot be updated, creation timestamp field ($ts) is checked against expiration timestamp field.

When an object expires, it does not return in queries or in the interface. It still exists in the passive database, until it is removed by a scheduled operation.

All cleaning rules have a status (DRAFT, LIVE or ARCHIVED), an action (KEEP or DELETE), a duration and a set of filters.

KEEP action means the associated object should stay in the datamart for the duration.DELETE action means the associated object should be removed from the datamart after the duration has expired.

There are two types of cleaning rules:

  • Event-based cleaning rules apply to events. They can apply to all events, or only to different channels, activity types or event names.

  • Profile-based cleaning rules apply to profiles. They can apply to all profiles or only to a compartment.

When a user point does not have any activity, nor profile, nor USER_LIST segment, it is removed from the platform. By cleaning activities and profiles, cleaning rules will clean your user points.

Cleaning rules can be easily edited in the navigator, in your datamart settings

Rules priority

KEEP cleaning rules have the priority on DELETE rules.

Only LIVE cleaning rules are taken into account when computing the expiration timestamp of an object.

Example 1

The following cleaning rules apply to my incoming event : - KEEP for 60 days - KEEP for 180 days - DELETE after 150 days

The event will be kept for 180 days then deleted.

Example 2

The following cleaning rules apply to my incoming event : - KEEP for 60 days - DELETE after 150 days

The event will be deleted after 150 days.

Example 3

The following cleaning rules apply to my incoming profile : - DELETE after 10 days - DELETE after 150 days

The profile will be deleted after 10 days.

Rules lifecycle

Cleaning rules are created with the DRAFT status. They can't be created LIVE or ARCHIVED. While DRAFT you can change the different properties of the rule, except its type. You then change the rule status to LIVE by doing an edit request. Once live, a rule can't be edited anymore and only the status can be changed to ARCHIVED.

At any moment, there should always be a LIVE event based rule with a DELETE action. You'll need to create at least an other rule to be able to archive this one.

Once ARCHIVED, rules can't be changed anymore, nor deleted.

You can only delete DRAFT cleaning rules. Once LIVE, they'll have to be ARCHIVED

Object reference

A cleaning rule has the following set of properties.

Content filter

Cleaning rules of type USER_EVENT_CLEANING_RULE can be associated with a content filter :

Samples

// KEEP User event cleaning rule with channel filter and activity type filter
{
    "id": "907",
    "action": "KEEP",
    "archived": false,
    "datamart_id": "1509",
    "channel_filter": "3844",
    "activity_type_filter": "SITE_VISIT",
    "life_duration": "P65D",
    "status": "DRAFT",
    "type": "USER_EVENT_CLEANING_RULE"
}

// DELETE User event cleaning rule without filters
{
    "id": "778",
    "action": "DELETE",
    "archived": false,
    "datamart_id": "1509",
    "channel_filter": null,
    "activity_type_filter": null,
    "life_duration": "P60D",
    "status": "LIVE",
    "type": "USER_EVENT_CLEANING_RULE"
}
// its associated content filter


// DELETE User profile cleaning rule with compartment filter
{
    "id": "905",
    "action": "DELETE",
    "archived": false,
    "datamart_id": "1509",
    "compartment_filter": "1606",
    "life_duration": "P365D",
    "status": "ARCHIVED",
    "type": "USER_PROFILE_CLEANING_RULE"
}

List cleaning rules in a datamart

GET https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules

Path Parameters

Query Parameters

{
    "status": "ok",
    "data": [
        {
            "id": "904",
            "action": "DELETE",
            "archived": false,
            "datamart_id": "1509",
            "compartment_filter": null,
            "life_duration": "P300D",
            "status": "LIVE",
            "type": "USER_PROFILE_CLEANING_RULE"
        },
        {
            "id": "778",
            "action": "DELETE",
            "archived": false,
            "datamart_id": "1509",
            "channel_filter": null,
            "activity_type_filter": null,
            "life_duration": "P60D",
            "status": "LIVE",
            "type": "USER_EVENT_CLEANING_RULE"
        },
        {
            "id": "902",
            "action": "KEEP",
            "archived": false,
            "datamart_id": "1509",
            "channel_filter": "3844",
            "activity_type_filter": null,
            "life_duration": "P250D",
            "status": "ARCHIVED",
            "type": "USER_EVENT_CLEANING_RULE"
        }
    ],
    "count": 3,
    "total": 3,
    "first_result": 0,
    "max_result": 50,
    "max_results": 50
}

Get a cleaning rule

GET https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules/:ruleId

Path Parameters

{
    "status": "ok",
    "data": {
        "id": "778",
        "action": "DELETE",
        "archived": false,
        "datamart_id": "1509",
        "channel_filter": null,
        "activity_type_filter": null,
        "life_duration": "P60D",
        "status": "LIVE",
        "type": "USER_EVENT_CLEANING_RULE"
    }
}

Get the content filter for a rule

GET https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules/:ruleId/content_filter

Only applies to event-based cleaning rules

Path Parameters

{
    "status":"ok",
    "data":{
        "filter":"$transaction_confirmed",
        "content_type":"EVENT_NAME_FILTER"
    }
}

Create a cleaning rule

POST https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules

Path Parameters

Request Body

{
    "status": "ok",
    "data": {
        "id": "917",
        "action": "KEEP",
        "archived": false,
        "datamart_id": "1509",
        "channel_filter": "3844",
        "activity_type_filter": "SITE_VISIT",
        "life_duration": "P70D",
        "status": "LIVE",
        "type": "USER_EVENT_CLEANING_RULE"
    }
}

Update a cleaning rule and/or change its status

PUT https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules/:ruleId

Path Parameters

Request Body

{
    "status": "ok",
    "data": {
        "id": "917",
        "action": "KEEP",
        "archived": false,
        "datamart_id": "1509",
        "channel_filter": "3844",
        "activity_type_filter": "SITE_VISIT",
        "life_duration": "P70D",
        "status": "LIVE",
        "type": "USER_EVENT_CLEANING_RULE"
    }
}

You'll have an error if doing any update that is prohibited, like changing a property while the status is not DRAFT or

Delete a DRAFT rule

DELETE https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules/:ruleId

Path Parameters

{
    "status": "ok"
}

Add or update a content filter for a rule

POST https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules/:ruleId/content_filter

Path Parameters

Request Body

{
    "status": "ok",
    "data": {
        "filter": "$transaction_confirmed",
        "content_type": "EVENT_NAME_FILTER"
    }
}

Remove a content filter for a rule

DELETE https://api.mediarithmics.com/v1/datamarts/:datamartId/cleaning_rules/:ruleId/content_filter

Path Parameters

{
    "status": "ok",
    "data": {
        "filter": "$transaction_confirmed",
        "content_type": "EVENT_NAME_FILTER"
    }
}

Last updated