Facebook public engagement data workflow
Use ego(lite) with Codex or Claude Code to review public Facebook posts and organize their visible reactions, comments, shares, post dates, source URLs, and check times into one source linked report. Compare Pages and posts with every number tied to its source.
Use this bounded workflow for public posts and public Pages you are allowed to review. Your agent records what the current browser session visibly shows and saves a source linked report. It does not act as a Facebook post liker, add a reaction, or make a hidden metric appear.
Download ego(lite), then import only the Chrome context you choose to authorize. Some public Pages and posts are visible without signing in, but Facebook still controls what a region, session, consent choice, or account can see. The agent does not enter credentials or work around those controls.
Add the public post or Page URLs you want to review, choose fields such as reactions, comments, shares, post dates, and source URLs, then select CSV or Markdown. Send the prompt to Codex or Claude Code to start a structured, source linked collection.
The agent opens each source in a separate ego(lite) Space so you can see which page supplied a count and take over if Facebook asks for a human decision. It records reactions, comments, and shares exactly as the page displays them and marks a field unavailable when the post does not show it.
Each Facebook Page review runs in its own ego(lite) Space while your Default Space stays open for other work. Track several sources in parallel, switch between tasks instantly, and keep every session, tab, and result organized.
Open the finished CSV or Markdown report to compare the public values with their URLs and check time. The output is a research record, not an engagement tool: it never claims that a displayed count is private analytics, guaranteed accurate, or caused by the workflow.
A Facebook liker site gives you fake numbers and takes your account in exchange. That is not what ego(lite) is for. Give your own Agent a visible browser, a bounded list, and a simple output contract instead. You retain the public source, the displayed value, the check time, and the stopping point for every post.
Use the same coding agent for the collection and the analysis that follows. It reads each public post in a real browser and returns one source linked report you can hand to a teammate. Across our 31-task benchmark on live sites, ego(lite) averaged 398 seconds per task against 605 for agent-browser, 52% faster. Actual timing varies by website, workflow, and network conditions.
Use a separate Space for each Page, campaign, or small source list. The collection stays away from your everyday tabs, and you can return to the exact post where a value was visible or where Facebook asked for your attention.
Open any Space to see which public post the agent is reviewing. If Facebook asks for sign in, a security checkpoint, consent, or another human decision, the agent records the status and hands the browser back to you instead of trying to bypass the control.
Import the Chrome context you choose rather than handing your login or an access token to a liker site. The data available to the agent matches what that browser can visibly open, while Facebook's login, privacy, regional, and rate limit rules stay in effect.
Meta's spam policy prohibits buying, selling, or exchanging likes, shares, follows, and clicks, and prohibits automated high frequency engagement. ego(lite) is not a Facebook auto liker: it turns values already visible in your authorized browser session into a source linked research record, then stops at access controls or unavailable fields.
Only public values that the current browser session visibly shows.
No fake engagement, no credential handoff, no access control bypass, no automatic liking.
Give your agent a bounded source list and an exact output contract. ego(lite) keeps the public source, displayed value, status, and stopping point visible, so your report remains useful without ever acting like a Facebook auto liker.