How to detect leads from a post

A detection tells MagicPost to scan everyone who liked or commented on one of your posts and qualify them against your ICPs. It is the main way leads land in your pipeline.

You can run detections by hand, post by post, or let the detection agent scan your new posts on its own. Detection only works on your own posts: you cannot point it at someone else's.

Capturing the engagers is free. Scoring them costs 1 credit per lead, per ICP, out of the 100 credits a month a paid plan (Creator and above) gives you, or the 10 credits of the free trial.

Run a detection by hand

1. Go to the Posts tab.

2. Find the post you want and click Detect.

3. Pick the ICPs to score against. Every ready ICP is ticked by default. ICPs that are still being computed, or already scanned for this post, cannot be selected.

4. Check the credit line: it tells you what you have left, and reminds you that 1 credit is spent per lead detected, per ICP.

5. Click Start detection.

MagicPost captures the post's engagers, runs them through the free pre-qualification, then sends the survivors to the AI. You can leave the page, the work carries on in the background.

A progress panel appears at the bottom right showing the engagers being fetched, then analysed, then the leads found. When it finishes, click View leads.

One detection at a time

MagicPost runs one detection at a time per account. While one is running, the buttons on every other post are greyed out with the tooltip *"A post is already being analyzed"*.

This is deliberate: it keeps a single account from saturating the queue, and it makes the cost of each detection visible instead of letting you fire off ten at once. A detection that gets stuck is released automatically after 15 minutes.

You can cancel a running detection with Cancel next to the progress chip. A cancelled detection shows as Cancelled, not as a failure.

Re-syncing a post

A post keeps collecting likes and comments long after you published it. When new people have engaged since the last scan, the post's status flips to To resynchronize and a Synchronize button appears, telling you how many new reactions are waiting.

Re-syncing scores only the new people. Anyone already scored against that ICP is skipped: not re-analysed, not re-charged. So a re-sync only costs credits for the leads it actually adds, at 1 credit each, per ICP.

If the post shows ICP updated instead, you regenerated one of its ICPs since the scan. Click Re-run to score the engagers that the older version of the ICP was discarding.

Posts you have not scanned with every ICP

On a post already marked Synchronized, you may see a discreet line saying some ICPs were never scanned. It simply means you ran the detection against a subset of your ICPs, and the post itself is up to date. Run it again with the missing ones for full coverage.

Where your results land

Go to the Leads tab. Filter by the source post or by ICP to see exactly what the detection turned up. Opening a post also lists every engager with their fit level.

If a status on a post or a lead is not obvious, understanding lead detection statuses decodes them all.

FAQ

Which interactions are captured?

Likes and comments. Reposts are not captured.

Can I detect leads on a post that is not mine?

No. Detection only runs on posts you published.

The post shows "No interaction". Why can't I detect?

Nobody has liked or commented on it yet. There is nothing to scan.

Why did a detection find no leads?

Everyone who engaged was ruled out at the free pre-qualification step: nobody matched your ICP's keywords, or they failed one of its filters. That costs you nothing, and it usually means the ICP is too narrow rather than the post being bad.

The detection failed. What do I do?

Click Retry on the post. Failures are usually transient.

Need help?

Reach out via the in-app chat, or book a 30-minute onboarding call: https://cal.com/magicpost-team/contact-sales-team