Beauty pipeline
Sales-safe mode: customer leads come only from explicit buyer-intent social comments under Dubai-relevant provider posts. Provider posts and empty posts are not customers.
Investment pipeline
Reset mode: search creates demand_thread/source rows only. A row becomes a lead only after deep extraction creates a person-level observation.
Affluence Audience Radar
Separate dashboard section for HNWI-adjacent discovery: luxury buyers, Golden Visa / business-setup intent, private-banking/wealth-management signals, and referral partners who already serve affluent clients.
Background Target Runner
Set how many net-new Beauty and Investment leads you need. LeadOS keeps running the existing discovery engines in the API background and updates progress while you work on other pages.
Connector status
Target Runner
Set exact net-new targets. Outputs are written into a job ledger, capped at the requested target, and extra candidates are separated for review.
Advanced run controls
Live progress
Progress is job-scoped and freezes when the job finishes.
Worker events
Job output browser
Filter, sort, and page through every row captured by this target job. Target rows and extra candidates are intentionally separated.
Recent target jobs
Open an older job to review its frozen ledger.
Beauty Sniper: real buyer comments
Elaris ICP mode: mines public social posts, opens comments, and keeps only visible buyer-intent comments for hair, nails, skin, lashes, brows, makeup, bridal, massage, waxing, and home service. Instagram, TikTok, and Facebook can run with Apify public-post/comment actors. LinkedIn/Snapchat need configured post/comment sources.
What counts as a beauty customer?
Accepted examples: “How much?”, “Price?”, “Location?”, “Available tomorrow?”, “Can I book?”, “Details please?”, “Home service?”, “Lash lift price?”, “BIAB?”, “Bridal makeup package?”.
Rejected examples: emojis, compliments, spam, provider ads, salon posts, creator self-promotion, non-Dubai content.
Important: Google search rows, social posts, Maps rows, provider captions, public stories, and empty posts are not customers. Only visible buyer-intent comments pass. Comment date is stored and shown when the actor provides it.
Beauty customer leads
Only sniper-approved buyer-intent comments.
Acquisition inventory
Hidden by default. These are provider/source rows used for dedupe, audit, and future comment mining; they are not customers.
Investment Sniper: Persian Horizon ICP
Investment is now running v3.9.5 Strict Latent Investor Radar. It does not wait for people to publicly say they have money; it hunts adjacent investor intent: idle savings, fixed-deposit alternatives, passive/managed business ownership, Golden Visa / investor-visa / business-ownership questions with strict visa-admin noise filtering, and buyer comments under business-for-sale/capital-seeker posts. Source posts stay inventory until a person-level signal is extracted.
Investment interpretation
Persian Horizon target: people who may want to invest, buy/acquire a business, become a silent/capital partner, solve idle-savings/passive-income problems, or use Golden Visa / investor-visa / business ownership as a UAE entry path. Capital seekers, sellers, brokers, and advisors are kept separate from investor prospects.
Investment Radar
Paid discovery output is separated by commercial role. Investor prospects are not mixed with business-sale or commercial-partner opportunities.
Hidden source queue / acquisition inventory
These are demand threads, SERP rows, and provider/source pages kept only for dedupe, cooldown, and future deep extraction. They are not customers.
Affluence Radar: target buyer comments
This section now has a strict next-stage mode: first it finds high-ticket source/provider posts, then it reads their public comments and lists only person-level commenters who ask price, details, availability, viewing, test drive, cost, Golden Visa/business setup requirements, or similar buying-intent questions.
What this section lists
Default view shows target people, not sellers. For LinkedIn, LeadOS now tries three layers: group discovery, group/post author intent, and post comments when the actor/cookies allow it. Provider/source rows are still available for debugging if you turn off “Only target buyer comments”.
Affluence run history / latest comment run
Use this to see exactly when a run started/finished, what failed, what returned no data, and how many rows passed the target-buyer gate.
Target buyer / affluence observations list
Default filter shows only person-level target comments. Turn it off only when debugging source inventory or referral partners.
External source map
What each connector is supposed to do. This page is for discovery connectors, not owned social channels.
Runtime settings / tokens
Stored in PostgreSQL table ops.runtime_settings. Secret values are masked; paste to replace.
Manual Apify run
Use only for debugging a specific actor.
System actions
Danger zone for test data only. Tokens/settings are not deleted.