> ## Documentation Index
> Fetch the complete documentation index at: https://developers.pleo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tags Sync Periodicity and Scheduling

This page describes **when Tags Sync runs**, how it is triggered, and the constraints integrations must respect when scheduling sync operations.

## Sync Schedule

Tags Sync runs **automatically every 60 minutes**.

An initial sync is performed immediately after the integration is connected and authorised.

This ensures Pleo Tags are populated from the outset and remain continuously up-to-date.

## Longer Sync Interval

If there is a risk of exceeding the Accounting System's API rate limit due to large volumes of Dimensions or Dimension Values, a longer sync interval of **12-24 hours** may be used instead.

The chosen interval should balance data freshness with API usage constraints.

## Ad Hoc Tags Sync (Optional)

If technically possible, integrations should support user-triggered sync.

Ad hoc sync allows users to:

* Trigger a Tags Sync for **all selected Dimensions** at any moment.
* Trigger a Tags Sync for a **single specific Dimension** at any moment.

This is useful when:

* A bookkeeper has added new Dimension Values in the AS and wants them reflected in Pleo immediately.
* A user suspects Tags are out of date and wants to force a refresh.

Ad hoc sync follows the same process as scheduled sync.

## Pleo API Rate Limit

Although the [Pleo API rate limit](/docs/current/authentication/api-base-urls#rate-limits) is 600 requests per minute, the integration should target a maximum of **500 requests per minute** to avoid errors under load.

Integrations should:

* Monitor request volume during sync cycles.
* Implement throttling or batching if Dimension or Tag volumes are high.
* Avoid unnecessary repeated requests within a single sync cycle.

## Tags Columns

Active Tag Groups in Pleo always have two visible columns: **Name** and **Code**.

This is consistent across all integrations, regardless of the AS used.

Some legacy integrations may have applied different column names. This does not affect matching behaviour, which is always code-based.

***

## What Comes Next?

* [Tags Sync Workflow Guide](/docs/current/guides/accounting-integrations/imports/tags-sync-workflow-guide)

***

## Related Reading

* [Sync Tag Groups with Dimensions](/docs/current/integration-design/accounting-integrations/imports/tags/integration-design-tags-sync-tag-groups)
* [Sync Tags with Dimension Values](/docs/current/integration-design/accounting-integrations/imports/tags/integration-design-tags-sync-tags)
* [Platform Capabilities: Tags Sync](/docs/current/platform/accounting-integrations/imports/tags/tags-sync-overview)

***