---
title: Progressive profile completion and metadata
description: Progressive profile completion requires that you track object metadata. Configure tracking of the following data:
component: pingidm
version: 7.5
page_id: pingidm:self-service-reference:pp-managed-json
canonical_url: https://docs.pingidentity.com/pingidm/7.5/self-service-reference/pp-managed-json.html
keywords: ["JSON", "Configuration", "Authentication", "Self-Service", "User Self-Service", "Terms &amp; Conditions"]
section_ids:
  pro-profile-percentage: Defining overall profile completion
---

# Progressive profile completion and metadata

|   |                                                                                                                                                                                                                      |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Progressive profiling is deprecated and will be removed in a future release of IDM. For more information, refer to [Deprecation](../release-notes/deprecated-functionality.html#deprecated-standalone-prog-profile). |

Progressive profile completion requires that you track [object metadata](../objects-guide/managed-objects.html#object-meta-data). Configure tracking of the following data:

* `createDate`: The date the user was created; used in the `onCreateUser.js` script in the `openidm/bin/defaults/script` directory.

* `loginCount`: The number of logins, by user.

* `stagesCompleted`: Used to track progressive profile forms, and whether they've been completed, by user.

User acceptance of Terms & Conditions is tracked by default (see [Terms & Conditions](terms-conditions.html)).

## Defining overall profile completion

A user profile is based on every item in `managed.json` where both `viewable` and `userEditable` are set to `true`. Every qualifying item has equal weight.

So, if there are 20 qualifying items in `managed.json`, a user who has entries for 10 items has a *Profile completion percentage* of 50.
