OnimatorOnimator
Check price

What is Limit per Feed Source in follow tool? Limit per Feed Source is the specific Follow Tool safety cap that limits how many accounts the automation follows from any single feed source before rotating to a different source, preventing the specific correlated-targeting pattern where an account follows dozens of users all traceable back to the same source account’s graph. Without the cap enabled, the Follow Tool works through the current feed source’s targets until the daily limit is reached, which can produce a follow history where the majority of the day’s follows came from one specific source’s followers — the specific correlated-targeting signature that platform detection systems use to identify follow campaigns keying off a single seed account. With the cap enabled, the tool switches to a different source after hitting the per-source ceiling, distributing the day’s follow volume across multiple sources and producing the varied-target pattern real user browsing generates.

How Limit per Feed Source Works

The mechanism runs at the per-session and per-day level within the Follow Tool. As the tool processes follows from a specific feed source, it counts how many follows have been dispatched from that source during the current window. When the count reaches the configured Maximum Follow per Feed Source Value, the tool stops using that source and rotates to the next source in the operator’s source list. The remaining daily follow capacity gets distributed across the alternative sources rather than concentrating on the original one.

The specific implementation uses two paired configuration fields: Limit Maximum Follow per Feed Source (the checkbox that enables the cap) and Maximum Follow per Feed Source Value (the numeric limit — say, 5 or 10 follows per source before rotation). Enabling the checkbox without setting a meaningful value leaves the cap effectively inactive; setting a value without enabling the checkbox means the cap doesn’t get enforced at runtime.

Why Per-Source Caps Matter

The specific reason Limit per Feed Source matters is that Instagram’s correlation detection models watch for the specific pattern where an account’s recent follows cluster suspiciously around users related to a single seed account. Real users don’t produce this pattern naturally — a person browsing Instagram might follow a handful of accounts related to one source, but their overall follow history spans many different sources reflecting the many different browsing sessions and content interests they experience.

Automated accounts running without per-source caps produce the opposite pattern. When a Follow Tool works through one source’s followers until the daily limit hits, the account’s daily follow batch consists entirely of users traceable back to that one source — a clear signal that the follows came from targeting rather than from organic browsing. Multiple days of this pattern accumulate into a follow history where the source-attribution correlation becomes obvious, and the detection outcome typically manifests as the account absorbing correlation-related enforcement even when no individual follow action produced any specific rule violation.

The per-source cap addresses this by forcing the day’s follow volume to distribute across multiple sources. An account with a 30-follow daily limit and a per-source cap of 5 draws from at least 6 different sources per day, producing the varied-source follow history that reads as ordinary user browsing rather than as targeted campaign execution.

Typical Configuration Values

The specific per-source cap values that produce sustainable patterns reflect the trade-off between operational efficiency and detection resilience.

Tight caps (3–5 per source) produce the most distributed follow history and the strongest correlation-resistance signature. Every source contributes a small fraction of the day’s follows, and the aggregate reads as broad browsing rather than as focused targeting. The trade-off is operational — tight caps require larger source lists to sustain daily follow volume without running out of sources to rotate through.

Moderate caps (5–10 per source) balance distribution with source-list efficiency. Each source contributes a meaningful but not dominant fraction of the day’s follows, and the pattern still reads as varied browsing while requiring smaller source lists than tight caps.

Loose caps (10–20 per source) allow more follows per source but produce weaker correlation-resistance signatures. These configurations suit specific strategies where source-list size is constrained and the operator has to make each source contribute more, but they accept the trade-off of producing more concentrated follow histories per source.

Well-configured setups typically settle on moderate caps (5–10 per source) for most operational use cases, with tight caps reserved for accounts particularly sensitive to correlation detection and loose caps used only when specific constraints justify the reduced detection resilience.

Interaction with Source Rotation

Limit per Feed Source is one of the specific mechanisms that supports source rotation at the per-session level. Source rotation as a broader practice involves systematically cycling through different source accounts across campaigns; the per-source cap enforces the same principle at the tighter granularity of within-session rotation.

The two mechanisms work together. Source rotation across campaigns prevents any single source from getting exhausted through repeated targeting across weeks and months. The per-source cap prevents any single source from dominating within-day follow volume. Together, they produce the follow history that spans many sources at both the daily and long-term levels rather than concentrating on any one source at either time scale.

Operators with well-configured source lists benefit disproportionately from per-source caps because the source lists have enough member accounts to sustain the daily follow volume even when the cap forces distribution across many sources. Operators with thin source lists (5–10 sources total) may find tight per-source caps operationally constraining and need to either expand their source lists or accept looser caps that produce weaker distribution.

Where the Setting Sits in the Follow Tool

Limit per Feed Source appears specifically under the Follow Account’s Followers from Feed targeting method in Onimator’s Follow Tool configuration — the targeting method where per-source concentration risk is highest because the tool works through a specific source’s follower graph. The parallel Follow Account’s from Feed method doesn’t necessarily need the cap because its target selection distributes across whatever accounts appear in the feed source’s own feed, which produces varied targets by construction.

The setting propagates through Copy Settings in Threads Manager (and its equivalents), which means template-based configuration replication carries the per-source cap forward across new accounts automatically. Operators developing template configurations that include the cap don’t need to manually enable it on every new account added to the fleet — the copy operation handles it as part of the Follow Method group of settings.

Why It Matters for Automation

Limit per Feed Source is the specific mechanism that prevents follow automation from producing the concentrated-source pattern that platform correlation detection uses to identify targeted follow campaigns. The setting takes seconds to configure — a checkbox and a numeric value — and produces the distributed follow history that reads as varied browsing rather than as source-driven targeting. Skipping the setting (leaving it disabled) produces the specific configuration state where daily follow batches cluster around single sources, which is one of the specific signatures that accelerates correlation detection outcomes on accounts running follow automation at any meaningful volume.

Related Terms