# How to Reconcile TikTok Creator Rewards Records With Public Video Views

Use the Creator Rewards records that you can access in your own account. Keep estimated rewards, confirmed payments, qualified views, and public views separate. Match records with exact video IDs, which are the codes that identify videos. Add public views as a dated observation beside each owner record. Public views cannot recover missing earnings or qualified views.

This process creates a reconciliation table: a table that matches related records while keeping their sources and differences clear. Start with your owner records. Add public data only when it helps answer your report question.

TikTok documents an owner dashboard with estimated rewards, video performance information, and video eligibility details. Eligibility means whether a video meets the program's requirements. The checked source does not establish a complete Rewards export or a current download process. Use the records your account actually provides. [TikTok Support, checked October 25, 2026; dashboard information only](https://support.tiktok.com/en/business-and-creator/creator-rewards-program/how-is-the-creator-rewards-program-different-from-the-tiktok-creator-fund?invalid_lang=ko).

## 1. Define the question and the report period

Write one sentence that states what you need to check. For example: “I need to list the estimated rewards shown for September and add the latest available public view count for each matched video.”

That question has two date references. September belongs to the owner reward records. The public observation has its own date and time. A public count read in October does not become a September count when you place it beside September rewards.

Choose which facts your report needs:

| Fact | Source to use | Meaning to preserve |
| --- | --- | --- |
| Estimated reward | Available owner Rewards record | An estimate under the source label |
| Confirmed payment | Available owner payment evidence | A payment supported by that record |
| Qualified views | Owner record that explicitly reports them | The source's qualified-view count |
| Eligibility | Owner record that explicitly reports it | The source's eligibility state |
| Public views | Dated public video observation | A public counter at the observation time |

Qualified views are views that the owner Rewards source identifies as qualified. This guide does not supply a separate qualification rule. Preserve the account's exact label. Do not treat ordinary public views as qualified views.

Record the report period, currency, and date you checked the owner source. Keep any stated time zone. If the source does not show a time zone or a precise time, record that gap. Do not add precision that the source does not provide.

Also state the report's coverage. “Three selected September owner records” is different from “all September Rewards records.” Use the second description only when your evidence supports that coverage.

## 2. Collect the owner records you can access

Open the Rewards dashboard or files available to your account. Keep a reference to the screen or file behind each copied record. Preserve the original labels, dates, video references, and amount states.

If you cannot find an export, manually record a small set that you can check. This method does not depend on a CSV export. CSV means a text file that stores table values separated by commas. The frozen evidence does not confirm that a complete Rewards CSV export is available.

Use these steps for each owner record:

1. Record where you found it and when you checked it.
2. Copy its period and video reference.
3. Copy the reward amount, currency, and exact amount label.
4. Copy qualified views and eligibility only when the source shows them.
5. Mark each missing value as unknown.
6. Check the copied values against the source again.

Keep estimated rewards and payment evidence in separate columns or tables. A displayed estimate does not prove that cash was paid. If a payment record lacks a video reference, keep its stated scope. Do not assign it to a video without evidence.

Preserve the source's unit. A currency amount and a view count are different units. Do not place them in one total. Keep different currencies in separate totals unless you have a separate, supported conversion method.

A missing value is not zero. Zero means the source reports none for that field. Unknown means the record does not establish the value. This distinction applies to rewards, payments, qualified views, eligibility, and public views.

## 3. Save three linked tables

Keep owner records, video identity checks, and public observations in separate tables. This makes later checks easier. It also prevents repeated public observations from creating repeated reward amounts.

The fields below are proposed report fields. They are fields for your own table, not extra fields returned by the public data collector.

### Owner records

Use one row per owner source record. A video can have several records for different periods or record types.

| Field to save | What to record |
| --- | --- |
| Owner record key | A unique reference for this source record |
| Source reference | Dashboard screen or file reference |
| Source checked at | When you checked the owner record |
| Record type | The source's label for the record |
| Report period | The exact period shown |
| Owner video reference | The source video link or ID |
| Estimated reward | Amount shown, or unknown |
| Currency | Currency attached to the amount |
| Payment evidence | Separate payment record reference, if available |
| Qualified views | Source count, zero, or unknown |
| Eligibility | Exact source state, or unknown |
| Open issue | Any missing or unclear detail |

### Video identity map

An identity map connects the owner video reference to the checked public video. Save the owner reference, exact public video ID, public URL, check date, and identity decision.

Check exact IDs wherever they are available. A similar caption, title, or date is not enough. If you cannot establish that both records concern the same video, leave the identity unresolved.

Keep the owner record key when you make this match. A video ID alone does not distinguish two reward periods for the same video.

### Public observations

A snapshot is one observation saved at a particular time. Keep each public snapshot as a separate row. Save the following documented fields when they are returned:

| Actor field | Use in this report |
| --- | --- |
| `inputUrl` | URL submitted for the check |
| `postId` | Returned video ID |
| `postUrl` | Returned public video URL |
| `views` | Observed public view count |
| `postMetricStatus` | Availability and precision information for public metrics |
| `status` | Overall result state for the row |
| `statusReason` | Detail about that state, when available |
| `scrapedAt` | Time the public observation was collected |

The documented output also includes `publishedAt`. That is the video's publication time. Keep it separate from `scrapedAt` and the owner Rewards period.

## 4. Add one public observation when it helps

An Actor is a hosted data collection program. The TikTok Metrics Scraper Actor documents public video counters and identity fields. Its documented output has no earnings or qualified-view field. It does not create your reconciliation table.

The checked contract supports known public video URLs through `startUrls`, with `mode` set to `knownUrls`. Use this small input as the starting shape:

```json
{
  "maxItems": 1,
  "mode": "knownUrls",
  "startUrls": ["https://www.tiktok.com/@mrbeast/video/7654638524729216287"]
}
```

4. Add one public observation when it helps

Replace the sample URL with one checked public video URL from your identity map. The supplied address is a sample. It is not evidence about your account or Rewards records. `maxItems` limits the total output rows. A limit of 1 keeps this proposed check small; it does not establish complete account coverage.

This input is valid under the supplied schema. No run was made for this article. The output fields describe the public contract, not a result observed here. [Public Actor contract, checked October 25, 2026; documented input and output, no runtime result](https://api.apify.com/v2/acts/chronometrica~tiktok-metrics-scraper/builds/default).

A Task is a saved input preset for an Actor. The public TikTok Creator Analytics Task page was present at the source check. Its saved settings were not read through an authenticated account, and it was not run. Check the input yourself before use. [TikTok Creator Analytics Task, checked October 25, 2026; public presence only](https://apify.com/chronometrica/tiktok-metrics-scraper/examples/tiktok-creator-analytics).

After your own check, inspect `status`, `statusReason`, and the `views` entry in `postMetricStatus`. Keep both the metric status and its precision value. The documented precision values include `exact`, `display_rounded`, `likely_rounded`, `unavailable`, and `unknown`.

Do not present a rounded count as exact. Do not turn a missing `views` value into zero. Even an exact public counter is not evidence of that many distinct people.

This report concerns owner Rewards records. If your separate task is to document delivery under a brand agreement, use the [TikTok UGC view evidence method](/en/articles/tiktok-paid-ugc-view-receipt/). That method has different checks for the agreement and its cutoff time.

## 5. Match records without changing reward totals

A join is a step that combines records through a shared field. Here, join only through a checked video identity. Keep the owner record key, period, and record type in the result.

Use this sequence:

1. Total the known owner reward amounts before adding public data.
2. Count the owner source records and the records with missing amounts.
3. Select at most one public snapshot for each owner record in this report.
4. Match the selected snapshot through the checked video ID.
5. Keep the owner period and public observation time in separate columns.
6. Total the owner amounts again and compare them with the original total.

If you retain several public snapshots, keep them in the public observations table. Select one for the report under a stated rule, such as the latest usable observation available for this report. Record which snapshot you selected.

One owner record must not become several payable amounts because it has several public readings. Likewise, two owner records for one video remain two source records when their periods or record types differ.

Describe the date relationship directly. “September estimate with public views observed October 25” is clear. “September views” would be unsupported if you only collected the public count in October.

Public counts also cannot show which moments viewers watched. If that is your next question, use the [TikTok retention data choice guide](/en/articles/tiktok-retention-data-choice/) to select owner data suited to that question.

## 6. Worked example: three selected videos

Original fiction. All values below are invented to explain the method. They are not actual earnings, a platform result, an Actor run, or a payout expectation. V1, V2, and V3 are fictional video labels.

The available owner records concern September. The separate public observations are dated October 25. The example supplies no public precision flags, exact observation times, payment records, or eligibility states. Keep those details unknown.

| Fictional video | Owner period | Estimated reward | Qualified views | Public views | Public observation date |
| --- | --- | --- | --- | --- | --- |
| V1 | September | 12 USD | 6,000 | 12,000 | October 25 |
| V2 | September | 8 USD | Unknown | 9,000 | October 25 |
| V3 | September | Unknown | Unknown | Unknown | October 25 |

The known estimated reward total is:

12 USD + 8 USD = 20 USD.

That is 20 USD across two owner records with known estimates. Three selected videos appear in the table, but the third estimate is unknown. Therefore, 20 USD is not a complete three-video reward total. It is also not confirmed paid cash.

The known qualified-view count is 6,000 for V1. V2 and V3 have no supplied qualified-view values. Do not describe 6,000 as a complete total for all three videos.

V2's 9,000 public views do not fill its missing qualified-view field. Do not use V1's relationship between public and qualified views to estimate V2. The source does not establish a conversion rule. The September owner period and October public observation also remain different date references.

Now suppose you later add another public snapshot for V1. That is a proposed additional record in this fictional example. Keep V1's owner estimate at 12 USD. The known owner total remains:

12 USD + 8 USD = 20 USD.

If your joined table counts V1's 12 USD twice, it produces:

12 USD + 12 USD + 8 USD = 32 USD.

The extra 12 USD comes from a repeated owner record. It is not another reward. Fix the join before you use the report.

For V3, retain unknown for both the estimate and public views. The example gives no reason for the missing public value. Do not label it as a failed lookup, a removed video, or zero views without evidence.

## 7. Record gaps and check the finished table

Give each unresolved item a plain explanation. Different gaps require different next steps.

| Gap | What to preserve | Next step |
| --- | --- | --- |
| Owner record unavailable | Unknown owner value and limited coverage | Check the available account records |
| Video identity uncertain | Unmatched owner record | Verify the source link or exact ID |
| Periods differ | Both original date references | Describe the difference in the report |
| Estimate lacks payment evidence | Estimated amount state | Check separate owner payment evidence |
| Qualified views or eligibility missing | Unknown value | Recheck the owner source |
| Public lookup failed | Returned status and reason | Keep the owner record and explain the failed check |
| Public count missing or rounded | Missing value or precision state | Limit the public comparison accordingly |

Accept the report only after these checks:

1. Every owner amount has a source reference, period, currency, and amount state.
2. Every match uses a checked video identity.
3. The owner record count and known totals stay unchanged after the join.
4. Missing values remain distinct from zero.
5. Each public count retains its observation time and available precision information.
6. Estimates remain separate from confirmed payments.
7. No calculation converts public views into earnings or qualified views.
8. The coverage statement names any missing owner records or export gaps.

The source evidence supports this proposed method, not a measured reconciliation result. One public question asks how to export Creator Rewards data from TikTok Studio. That supports the wording of the reader's problem. It does not establish an export feature or show how many creators have the problem. [Public export question, retrieved August 11, 2026; one question record only](https://www.reddit.com/r/TikTokMonetizing/comments/1tt3miy/how_do_you_export_creator_rewards_data_from/).

## Choose the next action from the remaining gap

Start with a small set of owner records that you can check. Save their sources, periods, currencies, and exact labels. Build the identity map before adding public counts. Your first useful result is a table whose known owner total stays unchanged and whose missing values remain visible.

If the remaining question concerns earnings, qualified views, eligibility, or payment, check the relevant owner record. Another public view reading cannot supply those facts. If dated public context would help, use the [TikTok Metrics Scraper Actor, contract checked October 25, 2026; public data collection only](https://apify.com/chronometrica/tiktok-metrics-scraper) with one checked video URL first. Then inspect the returned status and precision before you add the observation.

## Sources

- [TikTok Support: Creator Rewards dashboard, checked October 25, 2026; supports dashboard information, not a complete export workflow](https://support.tiktok.com/en/business-and-creator/creator-rewards-program/how-is-the-creator-rewards-program-different-from-the-tiktok-creator-fund?invalid_lang=ko)
- [TikTok Metrics Scraper default build 0.1.36 and README evidence, checked October 25, 2026; static contract, no run made](https://api.apify.com/v2/acts/chronometrica~tiktok-metrics-scraper/builds/default)
- [TikTok Creator Analytics Task, checked October 25, 2026; public page presence only, saved settings and execution not checked](https://apify.com/chronometrica/tiktok-metrics-scraper/examples/tiktok-creator-analytics)
- [Creator Rewards export question, retrieved August 11, 2026; one public question, no feature or demand-volume proof](https://www.reddit.com/r/TikTokMonetizing/comments/1tt3miy/how_do_you_export_creator_rewards_data_from/)