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

# Card Delivery

> YiDA data cards can be used in portals and DingTalk IM. In portals, configure content and data push, with up to 5 data card components per portal. For DingTalk push, set the first send time, repeat rule, end time, and send scope. Testing via bots is also supported.

YiDA data cards can currently be delivered to two scenarios: portals and DingTalk IM. On the delivery management page, view all card statuses in one place, such as whether push is on and any usage records.

## Use in Portals

In a portal, select the data card component. Two configuration sections appear:

* Content configuration

* Data push

When using data cards in a portal, **each portal supports up to 5 data card components**.

## Push to DingTalk

### Toggle

Each data card supports one push. When turned off, the push stops.

### Configure

The configuration items are shown in the panel above:

* First send time: the time the card is pushed for the first time.

* Repeat rule: send the card repeatedly according to a specified rule.

* End time:

* Send scope:

* Configure card click-through page: set the URL the card links to.

* DingTalk chat list tip: the tip shown when the card is sent to DingTalk. The default is "YiDA app data push".

### Data

<Note>
  **Data snapshots follow these rules:**
</Note>

**Data timeliness**: Data cards are sent as snapshots. Before each send (usually in the early morning of the day), YiDA generates the data snapshot in the background. Therefore, **the data pushed by data cards is not real-time**, but the statistical result from the previous day.

**Data perspective**: The card's data content is **snapshotted and pushed based on the developer perspective from the last edit and save**. In the card preview, you can see which developer's perspective is in use.

### Test

Send a card to the builder via a bot for a push test, similar to the Cool Card test capability.

Notes:

* The test send target is the operator themselves.
* The test requires a snapshot of a published card page, pushed to the operator via the YiDA bot.
* Wait for one test card to finish sending before starting the next test. Do not click the test button repeatedly at a high frequency.