Every active post, prefilled with its last numbers — change what moved and save. Paste counts exactly as the platform shows them: 3K, 1.4K and 2,486 all work, and rounded values get flagged as approximate in the report.
A topic groups posts into one report — use the same topic name for every post on the same story (e.g. "Merchant Issue"). Registering the same URL twice reuses the existing tracker rather than creating a duplicate.
Logged as the first capture the moment you start tracking, so growth is measured from the real starting point rather than from whenever the app is next opened. Same formats as the Capture tab: 3K, 1.4K, 2,486. Leave blank to start with no baseline.
Pause a post to stop reminders without losing its history.
Paste the exported comment thread, then run the coding pass. Themes are derived once per topic and reused for every later batch, so labels stay consistent across the whole story. Re-pasting the same thread never duplicates rows — only new comments are stored and charged for.
One comment per line as author⇥tab⇥comment text⇥tab⇥likes (straight from a spreadsheet), or paste a JSON array of {author, text, likes}. Lines with no tabs are treated as comment text only.
Everything the deck needs for one topic, with the disclosure notes already worked out. The JSON is what the deck generator consumes.
Same worker and team password as the other foodpanda tools. Stored in this browser only.
The standing formula, now computed server-side so it is identical in every deck.
(likes or total reactions × 1) + (comments × 2) + (shares or reposts × 3)
Saves and bookmarks are excluded so figures stay comparable across platforms. On Facebook the ×1 term is total reactions, not the Like bucket. On Threads and X the ×3 term is reposts, not shares — a Threads post carries both and only reposts count. Reaction percentages are always taken against the stored total, because platforms hide the small buckets and the visible reactions do not add up to it.