Owners, managers & users

TikTok App Updates: read releases and configure Discord notifications

Review recorded Apple and Google app releases, enable owner-managed Discord delivery and inspect delivery results.

Browse all guides

This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.

Start here

  1. Open TikTok App Updates and check the latest Apple App Store and Google Play cards and the scheduler’s last-check time.
  2. Owners: enter the destination Discord webhook URL, turn on Enable alerts if wanted, and choose Save settings.
  3. Use Send test alert to confirm the saved destination, then check Discord and the page’s delivery status.
  4. Use Send latest versions to Discord for a current-version summary, or expand Release history notes to read past recorded updates.

Read the latest versions and history

The page records new store versions as the platform discovers them, with automatic checks scheduled every 20 minutes. The latest cards show version information and store links; Waiting for first check means the scheduler has not yet populated the record.

Release history stores each version when first seen by this platform. Released and First seen are different timestamps: a store release may predate the first platform check. Expand a release-notes summary to read its full text. No release notes supplied means the store record did not include notes.

Configure the owner’s Discord destination

Owners can save a webhook and change Enable alerts. Managers may read the release information but cannot change alert settings or send the owner’s alert actions. The saved webhook is shown in masked form, and a blank replacement field keeps the existing destination when saving settings.

Alerts include the app icon, version, release notes and a direct store link. Use a webhook URL for the intended Discord channel, not a regular channel or invitation link. Save a replacement URL when the old webhook has been revoked.

Choose the appropriate delivery action

Send test alert sends an actual test message to the saved Discord destination. Send latest versions to Discord sends the latest available version summaries, useful when first setting up a channel. These actions are distinct from waiting for a newly detected release alert.

Remove webhook clears the stored destination and disables alert delivery. Turning off Enable alerts pauses automated delivery while retaining the saved webhook. Check the current enabled/disabled state after saving.

Review delivery results and failures

Your recent alert deliveries is visible to the owner and shows recorded statuses, timestamps and any available failure details. A release in the history does not by itself mean this network successfully received a Discord message.

If delivery fails, check the saved destination and the error rather than repeatedly sending tests. A missing webhook, no available release record or a Discord error can prevent the requested send. If automatic checks appear stale across store cards, ask the administrator to inspect the scheduler.

Frequently asked questions

Can a manager enable alerts?

No. The main account owner controls the webhook, alert setting and send actions; managers can review release information.

Why did the recorded date differ from the store release date?

First seen is when this platform discovered the version. Released is the store’s supplied release date.

Do I need to paste the webhook again every time I save?

No. Leave the replacement field blank to keep the existing saved webhook; use Remove webhook to clear it.

Does Send test alert check for a new app version?

It checks delivery to the saved Discord channel by sending a test. The release scheduler and the latest-version summary are separate functions.

Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.