Backdating Actions

Backdating may be necessary when the time that an action was logged/mission was completed/points were credited is different from the time the log action call occurred. This is often the case when actions are batched and sent to Nitro after the mission completion date. Backdating an action logs the given actionTime (which may be in the past) instead of when the actual log action call occurs.

Note: The daily achievement limit in repeatable missions does not have backdating support. It uses the current date/time (in Pacific Standard Time) when the action comes in.

If a mission has a set date range, you can log a backdated action after the mission ends and still complete the mission. A mission will complete as long as:

The actionTime provided in the action is within the mission's date range and the action is logged after the date range is set.
The mission is active, inactive, or expired.
The mission limit has not been reached.

To backdate an action, use the actionTime parameter in the POST /users/{userId}/actions method or in a data import actions file to set the completed action time. The mission's completion date will reflect the backdated time.

Leaderboard Impact

When you log a backdated action, that action is applied to the groups that the user is in at the time the API call was made, not the groups the user was in at the time the action is backdated to. Show me an example If you must move a user between groups, log any backdated actions before moving the user to the new group.