Our methodology
Every stat, benchmark, and feature comparison we publish follows a documented process. Here is exactly how we collect data, run tests, and decide what to write.
Real account data
Every performance claim is derived from anonymised, aggregated data across active PostEngage.ai accounts — not sandbox simulations. We only publish metrics we can reproduce.
Controlled experiments
When comparing two approaches (e.g. keyword trigger vs story mention trigger) we run the variants on accounts with similar follower counts, post frequency, and niche to minimise confounders.
How we compute DM open rates
DM open rate = (unique reads ÷ delivered DMs) × 100. "Delivered" means the Meta API returned a success status. "Read" means the platform confirmed the recipient opened the thread.
Comparison table criteria
Competitor feature claims are verified by: (1) reading the competitor's own documentation, (2) testing a free or trial account where available, (3) cross-checking community reports (Reddit, G2, Trustpilot). We re-verify quarterly or when a competitor ships a major update.
Compliance claims
Any statement about Meta API compliance refers to the official Instagram Messaging API and Graph API. We do not use third-party scraping, browser automation, or unofficial endpoints. Compliance status is accurate as of the published date and subject to Meta policy changes.
Update cadence
Blog posts display a "Last updated" date. We revisit near-ranking posts (position 8–20 in Google Search Console) every 90 days, and update pricing/feature tables within 7 days of a confirmed competitor change.
Limitations we acknowledge
- Sample bias: Our data skews toward engaged, active users. Dormant accounts are excluded from rate calculations.
- Platform variability: Instagram delivery rates vary by account age, follower count, and posting cadence. Your results may differ.
- Competitor access: We use publicly available plans for competitor testing. Enterprise or custom tiers may have undisclosed features.
- Policy changes: Meta updates its policies frequently. Any compliance statement carries the caveat “as of the published date.”