---
title: Increment Login Count node
description: The Increment Login Count node increments the successful login count property of a managed object.
component: auth-node-ref
version: latest
page_id: auth-node-ref::increment-login-count
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/increment-login-count.html
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-increment-login-count.adoc"]
superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/increment-login-count.html
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
---

# Increment Login Count node

The Increment Login Count node increments the successful login count property of a managed object.

Use the [Login Count Decision node](login-count-decision.html) to change the flow of the journey based on the count.

## Example

The following journey uses the [Increment Login Count node](increment-login-count.html) to update the login count on successful authentication:

![Incrementing login count](_images/login-journey.png)

* The [Platform Username node](platform-username.html) injects the `userName` into the shared node state.

* The [Data Store Decision node](data-store-decision.html) determines whether authentication is successful.

* The [Increment Login Count node](increment-login-count.html) (outlined in the image) updates the login count.

* The [Inner Tree Evaluator node](inner-tree-evaluator.html) invokes the following nested journey for progressive profiling:

![Determining next steps based on login count](_images/progressive-profile-journey.png)

* The [Login Count Decision node](login-count-decision.html) triggers the rest of the journey depending on the login count and its settings.

* The [Query Filter Decision node](query-filter-decision.html) determines whether managed object profile fields are still missing.

* The [Page node](page.html) requests additional input for the profile.

* The [Patch Object node](patch-object.html) stores the additional input in the managed object profile.

## Availability

| Product                               | Available? |
| ------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud       | Yes        |
| PingAM (self-managed)                 | Yes 1      |
| Ping Identity Platform (self-managed) | Yes        |

1 This functionality requires that you configure AM as part of a [Ping Identity Platform deployment](https://docs.pingidentity.com/platform/8.1/sample-setup/).

## Inputs

This node's Identity Attribute specifies the property it requires in the incoming node state. It uses this property to access the managed object.

## Dependencies

This node depends on the underlying identity service (PingIDM) to store the managed object.

## Configuration

| Property           | Usage                                                                                                              |
| ------------------ | ------------------------------------------------------------------------------------------------------------------ |
| Identity Attribute | The attribute used to identify the managed object in the underlying identity service (PingIDM).Default: `userName` |

## Outputs

This node doesn't change the shared state.

## Outcomes

Single outcome path; on success, this node increments the managed object's `loginCount`.

## Errors

If this node fails to access the managed object, it throws an exception with a `No object to increment` message.

If this node fails to increment the login count, it logs an `Unable to increment login count` warning message.