UGC Tracking: How to Track Posts, Views and Payouts

To track UGC and clipping creator posts, keep a record for each published link, save its agreed payment terms and counting deadline, and freeze the view count used to calculate its earnings. Check the content and required proof, resolve holds, then pay the approved amount and record which posts the transfer settled.

This guide is for founders, brand marketers and agencies paying creators per post or per view. If you're a creator looking for work, start with a campaign's offer and earning conditions. Buyers still recruiting can use our guide to hiring clippers; for the brief and launch, see how to set up a clipping campaign.

What exactly am I tracking: content, views or sales?

Start with the deliverable. UGC commissioned only for your ads needs a delivered-file link, acceptance record and agreed usage permissions. The workflow below covers published posts on creator or campaign accounts. An independently agreed editing or delivery fee follows its acceptance criteria and due date; don't add a view requirement afterward.

Keep these questions separate:

Views are not a count of unique customers. Creator links and promo codes can sit alongside the post ledger, but neither replaces evidence of payable views or captures every possible downstream sale. Review and sentiment analysis is another meaning of “UGC analytics”; it answers a different question from what you owe a paid creator.

Can I use a spreadsheet, or do I need a UGC tracker?

A spreadsheet can calculate CPM and capped payouts. The recurring work is collecting links, updating counts at the right time and keeping payment records accurate.

Choose by the work slipping through, rather than a universal creator-count threshold. Before adopting software, follow an actual post from submission through closing and payment recording. Check what happens when its view count is unavailable. If an agency manages the program, request evidence for individual posts alongside its campaign totals.

What should I record for every creator post?

Use one row per public post. Cross-posts on different platforms get separate rows, linked by a shared content ID. Whether both earn money depends on the agreement.

The following is a suggested tracking template, not a list of fields every tool fills automatically. Treat each semicolon-separated item as a column; leave genuinely inapplicable fields blank.

Link each row to the creator's saved deal version so terms remain readable without retyping them. Protect closed counts and formulas from casual edits. Keep payout-account details in controlled records rather than a broadly shared reporting sheet.

How do I know they actually posted?

Collect the live URL through a submission form, shared sheet or tracker. Open it and check the account, publication time and content against the agreed brief. Match the platform post ID before adding a row: differently formatted links can point to the same post.

Compare expected deliverables with accepted links. An empty row needs a follow-up owner; it isn't a verified zero-view post. If account monitoring discovers posts automatically, check campaign relevance before counting them as deliverables.

ViewsBase accepts creator submissions through web or Discord, team-pasted links and optional watched accounts. Watching is off by default; Instagram watching imports Reels, and YouTube watching finds Shorts. Discovery and metric refresh are separate jobs.

Check which metrics each platform exposes. ViewsBase tracks TikTok views, likes, comments and shares; Instagram views when exposed, likes and comments; and YouTube Shorts views, likes and comments. Instagram shares are not tracked. Missing public views need investigation or documented creator analytics, not a zero pasted into the sheet.

When do I stop counting views?

Save the counting rule before posting, including whether the window starts at publication or submission. Then distinguish the agreed deadline from the time the closing count was actually observed.

A count fetched after the deadline is not an exact historical snapshot of that deadline. Record both timestamps and make sure your collection method fits the agreed rule. Don't present today's total as yesterday's final count.

In ViewsBase, the default window runs for seven days after publication, with creator-specific overrides available. The closing fetch happens on the next scheduled check, generally within about six hours after the deadline; Shorts follow their daily check. A failed closing fetch leaves the post open instead of finalizing stale views. The docs explain how the final count is fetched.

For late submissions, apply the agreed submission rule and document exceptions. If ViewsBase permits submission after counting has ended, it finalizes with the views available then; it does not reconstruct the earlier count.

Private, deleted or unavailable posts need a retry or evidence review. When entering a count manually, save its source, capture time and explanation. Once closed, keep ongoing performance reporting separate from the frozen payment count.

How do rates, caps and tiers become money owed?

First confirm content acceptance, any view minimum and the applicable audience tier. For a qualifying view-based post with a view cap:

View pay = min(views at close, view cap) ÷ 1,000 × rate

Illustration, not campaign results: both posts below qualify, have no base fee and use $0.50 per 1,000 views with a 500,000-view cap.

The payment documentation supplies these examples. A dollar cap needs its unit recorded too. A limit on one post's view pay does not limit the campaign's total obligation.

For fixed post pay, apply the agreed qualification conditions. For a hybrid, calculate the base and performance components under their own rules. ViewsBase offers can limit base slots per period; its milestone bonuses are the total bonus at the attained level, not the sum of every crossed milestone. Existing posts retain their saved terms when offers change.

You can check simple payout arithmetic using final counts and a shared rate, cap, minimum and flat fee. That calculator does not decide eligibility or model audience tiers, recurring base slots or milestones.

What proof do I need before paying?

The evidence should let a reviewer trace the amount back to this post:

• Identity and acceptance: the live link, correct account and recorded content check.
• Count: the observation used to close payment, with its timestamp and source.
• Tier: analytics supporting any audience condition that changes the rate.
• Decision: who resolved a hold or exception, when and why.

A screenshot should identify the post and capture time. A cropped account-wide total cannot explain an individual post's earnings. ViewsBase supports creator-uploaded analytics recordings for audience tiers; inspect the evidence rather than treating the file itself as a guarantee.

A suspicious view spike calls for review, not an automatic accusation of fraud. Keep the affected amount outside the payment batch while you resolve the held post. Record missing evidence as a specific next action so it doesn't disappear inside a vague “pending” status.

What did 13,333 posts teach us about tracking?

Our 10 November 2026 aggregate pull covers 13,333 pay-per-view posts by 430 creators across seven campaigns, posted 2 July 2025–27 October 2026 for our own consumer app, DePuff AI. These were mostly TikTok slideshows and talking-head posts; 96.9% were on TikTok. This is one advertiser, not a market census or forecast, and these were not Whop campaigns.

Operational illustration: the actions below are our proposed recordkeeping choices based on that sample, not tested performance improvements.

The pooled cost was $362,275.86 in positive finalized earnings ÷ 1,463,930,987 recorded views × 1,000 ≈ $0.247, across 7,840 earning posts. Those posts had paid or finalized status; the total is not confirmation that every amount had been transferred. It excludes rejected posts, software, labor and payment fees, while including beyond-cap views on earning posts. It does not establish ROI or software savings.

Our published study's methodology explains the approach and limits; that page contains the earlier October snapshot. The figures above use the refreshed November pull.

How do I close posts and avoid paying twice?

Assign a closing owner and use this checklist for each payment batch:

1. Confirm the posts. Check identity, campaign relevance and duplicates against the proposed selection.
2. Confirm the counts. Verify the window ended, the closing observation succeeded and its timestamp/source are saved. Resolve missing views rather than calling old data final.
3. Confirm eligibility and price. Apply the saved terms, required proof, tier and cap. Record hold decisions. An independently due delivery fee should not wait for a separate view bonus.
4. Freeze the selection. Choose the exact approved, closed, unpaid posts. Save a batch ID and share the calculation with the creator.
5. Pay on the agreed schedule. Verify changed payout details with the creator and send money through your chosen provider.
6. Match the transfer. Record the reference, date and posts actually settled. Reconcile any remaining ready, held and still-counting amounts separately.

Continuing the illustration: A and B above are approved for the same creator, so the batch totals $410. If the transfer settles only A, record $160 paid against A and leave $250 ready unpaid against B. If another post finishes afterward, put it in a later batch. Never mark the creator's entire changing balance paid because one transfer succeeded.

In ViewsBase, saved summaries identify selected ready posts. Scale and higher plans can also record a selection in a payout file. Downloading that file or sharing a summary does not send money or mark posts paid. If a selected post becomes held or its amount changes, review the summary before recording payment.

ViewsBase supports this workflow across TikTok, Instagram and YouTube Shorts: it prices posts from each creator's deal, holds suspicious view spikes for review and keeps a payout ledger. Your team brings the creators and pays them with its own method. ViewsBase never sends or holds creator money and takes no cut of creator pay.

Try a completed batch with your actual terms and compare the ledger with your records. Plans start at $49/month, checked 10 November 2026. The 14-day trial requires a card; cancel before it ends to avoid a subscription charge.

What should my weekly creator report show?

Report the campaign period and observation date, then show expected, published and closed posts; closed unpaid amounts; live estimates; holds and missing proof; paid totals and references; and failed refreshes with an owner. Split performance by creator and platform, including posting cadence, views and available engagement.

For a paid creator CPM, divide payments allocated to a defined set of posts by those same posts' stated view counts, then multiply by 1,000. For total program cost, add software, fees and labor once and keep the same denominator. Label reports using finalized earnings rather than cash paid accordingly. Neither cost measure proves sales impact.

Agency teams can share branded live client reports on ViewsBase's Agency plan. Keep the frozen batch record separately: a live dashboard can change after the payment it helped explain.