---
title: Login Count Decision node
description: "Configure the Login Count Decision node to trigger a journey action when a user's successful login count reaches a specified threshold."
component: platform
version: 7.5
page_id: platform:auth-node-ref:login-count-decision
canonical_url: https://docs.pingidentity.com/platform/7.5/auth-node-ref/login-count-decision.html
llms_txt: https://docs.pingidentity.com/platform/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-login-count-decision.adoc"]
section_ids:
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
  example: Example
---

# Login Count Decision node

The Login Count Decision node triggers an action when a user's successful login count property reaches a specified number.

Use the [Increment Login Count node](increment-login-count.html) to set the login count on successful authentication.

## Availability

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

This functionality requires that you configure AM as part of a sample Ping Identity Platform deployment. | Yes        |
| Ping Identity Platform (self-managed)                                                                                                   | Yes        |

## 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 IDM to store the managed object.

## Configuration

| Property           | Usage                                                                                                                                                                                                                                                                                |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Interval           | Trigger the `True` outcome depending on this setting, the Amount, and the login count:- `AT`

  Proceed to `True` when the login count matches the Amount setting.

- `EVERY`

  Proceed to `True` every time the login count reaches a multiple of the Amount setting.Default: `AT` |
| Amount             | The login count to trigger a `True` outcome depending on the Interval.Default: 25                                                                                                                                                                                                    |
| Identity Attribute | The attribute used to identify the managed object in IDM.Default: `userName`                                                                                                                                                                                                         |

## Outputs

This node does not change the shared node state.

## Outcomes

* `True`

  The login count reached Amount, and the Interval setting triggered this outome.

* `False`

  All other cases.

## Errors

This node can throw exceptions with the following messages:

| Message                                     | Notes                                                                                           |
| ------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| `<Identity Attribute> not present in state` | Failed to read the specified Identity Attribute in the shared node state                        |
| `Failed to retrieve existing object`        | Failed to find the managed object using the Identity Attribute value from the shared node state |
| `Retrieve login not found`                  | Failed to read the managed object's login 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.