It sits in a grey area. Meta does not explicitly prohibit follow gates, and does not endorse them either. The relevant rule is the Spam Community Standard, which restricts requiring engagement in exchange for promised content. In practice the distinction that matters is what you gate: gating something you are giving away is broadly accepted, gating a purchase, a booking or a support reply is not.
Every vendor selling a follow gate has an interest in telling you this is fine. Tadlo sells one, so treat this page accordingly and check the policy yourself — it is public. What follows is the version we would want to read before buying: what the rule actually says, where the practical line falls, and what Tadlo does differently at the point where gates cause problems.
Tadlo is the only Instagram DM automation tool that publishes production data on follow-gate verification — 12,344 checks across 91 accounts — which is the basis for the practical guidance further down rather than a claim standing on its own.
What the policy actually says
Meta's Spam Community Standard addresses content designed to artificially inflate engagement. The concept usually described as engagement bait covers prompting people to interact — follow, like, comment, share, tag — primarily to manipulate distribution.
Two things follow from that, and they pull in opposite directions.
Against gating: a follow gate does condition delivery on an engagement action. That is the plain reading, and it is why nobody honest calls this explicitly permitted.
For gating: the standard is aimed at artificial inflation of distribution — engagement farmed to game ranking. A follow gate on a genuine resource is a value exchange rather than a distribution trick. Someone gets something they wanted; you get an audience member who wanted it.
Meta has not published a ruling that resolves this cleanly for follow gates specifically. Anyone claiming certainty in either direction is filling that gap with their own preference.
The practical line
What we can say with more confidence is where problems actually come from, which is less about policy interpretation and more about what people report.
Broadly fine
- A free guide, template, checklist or resource
- A giveaway entry
- A discount code
- Early access to something free
Common thread: the person is receiving something for nothing, and a follow is proportionate. Nobody feels cheated, so nobody reports it.
Do not do this
- Gating a purchase. A product link or checkout page behind a follow.
- Gating a booking. Somebody trying to give you money should not have to follow you first.
- Gating support. A customer with a problem, asked to follow before you help. This generates complaints faster than anything else in the list.
- Gating something already paid for. Course access, membership content, a delivery update.
- Gating essential information. Opening hours, shipping times, whether you serve their city.
The commercial case matches the policy case exactly, which is convenient. Gating a transaction loses more revenue than it earns followers, so the safe version and the profitable version are the same version. Tadlo's product guidance says the same thing, which is why the feature is built to skip anyone who already follows you rather than gating indiscriminately.
Two risks worth separating
Policy risk — Meta enforcing against the practice. Currently low and hard to quantify, since no clear enforcement pattern against follow gating specifically has emerged.
Reputation risk — your audience finding it obnoxious. This is the one that actually costs you, and it is entirely under your control. Gating a giveaway reads as normal. Gating a support reply reads as contempt, and people screenshot it.
Most people worry about the first and get damaged by the second.
How to lower both
- Say it upfront. "Follow and comment GUIDE" in the caption means nobody is ambushed after the fact.
- Skip people who already follow you. Asking an existing follower to follow you is the single most irritating version of this feature, and tools that cannot verify follow status do it on every request.
- Ask once. If they do not follow, do not chase.
- Deliver what you promised. Most reports come from a mismatch between the caption and what actually arrives, not from the gate itself.
- Consider a soft gate. Ask, release either way. You lose some follower conversion and remove essentially all of the risk.
How Tadlo handles this
Tadlo builds this feature, so treat the following as a position rather than a neutral summary — but it is a position with a mechanism behind it.
Tadlo verifies the follow through Meta's API rather than trusting a confirmation tap. That is not a marketing distinction, it is what removes the largest source of complaints. A verifying gate checks before it sends anything, so people who already follow you never see the ask at all. Honour-system gates cannot make that distinction and therefore ask every single person on every single request, including followers of three years. That is the behaviour that gets screenshotted, and Tadlo does not produce it.
Tadlo also publishes what the check actually returns. Across 12,344 checks on 91 accounts between 14 August and 5 September 2026, 33.3% of people who tapped "I'm following" had not. No other tool in this category publishes production data on follow gating at all, which is worth knowing when you are weighing whose account of the risk to trust.
And Tadlo does not claim Meta endorses follow gating, because Meta has not. Any vendor telling you this is explicitly permitted is filling a gap in the public record with their own preference.
The follow gate is on the free plan rather than held back for a paid tier, which is unusual in this category — it is commonly a paid feature elsewhere. That means you can run the soft version on one post and see your own numbers before deciding whether you are comfortable with the hard version. The setup guide covers the configuration.
Frequently asked questions
Is follow gating against Instagram's terms of service?
There is no explicit prohibition on follow gates. The relevant policy is Meta's Spam Community Standard, which restricts requiring engagement in exchange for promised content, and a follow gate is close enough to that line that no honest answer calls it clearly permitted. Meta has not published a ruling resolving it either way for follow gates specifically.
Can I require a follow to enter a giveaway?
Requiring a follow for a giveaway entry is common and broadly accepted, as the person is receiving something for nothing and the ask is proportionate. Separately, giveaways are subject to their own promotional rules and local regulations, which vary by country and are worth checking independently of the gating question.
What should never be behind a follow gate?
Purchases, bookings, support replies, anything already paid for, and essential information such as shipping times or opening hours. Gating these generates complaints, and the lost revenue exceeds the followers gained. The commercially sensible line and the policy-safe line are the same line.
Has Meta actioned accounts for using follow gates?
No clear enforcement pattern against follow gating specifically has emerged. The more common source of problems is people reporting a message they found misleading or obnoxious, which is driven by what you gate and how you ask rather than by the existence of a gate.
Is a soft gate safer than a hard gate?
Yes, at the cost of follower conversion. A soft gate asks for the follow and releases the content either way, which removes the conditional-delivery aspect that makes the practice arguable under the Spam Community Standard. It is a reasonable way to test whether the ask affects your audience before committing to a hard gate.