Sources & Feature Verification

Social media tools can differ in ways that are easy to overlook. A feature may be available only on a particular plan, work with certain account types, or require a manual step. Locomu aims to provide enough context for readers to understand those differences and check the information that matters to them.

This page explains the sources we may use and how we approach the verification of product features, pricing, integrations, and other details.

Our Approach

Locomu prepares tool profiles, comparisons, and guides for creators, bloggers, freelancers, and small teams. We aim to use relevant evidence for factual claims, distinguish provider documentation from firsthand testing, and explain meaningful uncertainty.

The sources and checks appropriate for one product may differ from those needed for another. A pricing claim, for example, may require a different source from a statement about how a feature works in practice.

Sources We May Use

Depending on the claim, relevant sources may include:

• Official product websites: Product descriptions, feature pages, and provider information.
• Pricing pages and plan details: Published prices, billing conditions, usage limits, and available plans.
• Help centers and documentation: Instructions, account requirements, supported formats, and known limitations.
• Release notes and official announcements: Information about new, changed, or discontinued features.
• Social media platform documentation: Rules and requirements that affect accounts, integrations, and publishing.
• Direct testing: Observations from a feature or workflow examined by Locomu under identifiable conditions.
• Other relevant sources: Independent reporting or specialist material that provides context or helps identify a question requiring further investigation.

We aim to link to important sources where practical. A provider’s description can explain what the provider offers, but marketing claims are not necessarily independent evidence of performance or results.

How We Check Feature Claims

When evaluating a feature, we aim to identify the conditions that matter to the reader. Depending on the product, these may include:

1. Feature and purpose: What the tool says the feature does.
2. Platform and account type: Which network and account types are relevant.
3. Content format: Whether the feature applies to posts, stories, videos, carousels, or another format.
4. Method: Whether an action occurs directly or requires a notification or manual step.
5. Plan or access: Whether the feature requires a particular subscription or additional purchase.
6. Other conditions: Applicable region, permissions, integration, or usage limits.
7. Evidence and date: The source consulted and when the relevant information was checked.

A product’s support for a social media platform does not necessarily mean that all functions work with every account type or format. Where such distinctions matter, we aim to explain them.

Documented, Tested, and Unconfirmed Information

We aim to distinguish the basis for important claims:

• Documented: The information is supported by a source, such as official product documentation. It has not necessarily been tested firsthand by Locomu.
• Tested: A specific feature or workflow has been examined directly under identifiable conditions.
• Unconfirmed: Available evidence is insufficient, unclear, or conflicting.

These descriptions apply to the particular claim or feature. Testing one part of a tool does not mean every feature, plan, platform, or integration has been tested.

When firsthand testing is practical, we aim to record the date, plan, account type, feature, and relevant conditions. A test reflects the version and access available at that time; it cannot establish how a product will work for every user.

Pricing and Plan Verification

When reporting pricing or comparing plans, we aim to check the provider’s published information and explain relevant assumptions. These may include the currency, billing period, number of users or channels, plan requirements, and possible additional charges.

A monthly equivalent advertised for an annual subscription should be identified as such. We aim to distinguish a product’s starting price from the cost of a particular reader’s intended setup.

Pricing, promotions, taxes, and availability can vary or change. Readers should check the provider’s current pricing and terms before subscribing or purchasing.

Conflicting or Missing Information

Documentation may be incomplete, contain conflicting details, or lag behind a product change. Information can also differ by plan, region, account type, or date.

When evidence is insufficient, we may seek clarification, identify the uncertainty, omit the claim, or mark it as unconfirmed. A feature should not be described as unsupported solely because we could not find information about it.

Providers may offer corrections or additional documentation. We assess those submissions against the available evidence and retain editorial responsibility for Locomu’s content.

Updates and Corrections

Features, prices, and integrations can change after publication. We aim to revisit information as appropriate and prioritize changes that could materially affect a reader’s decision.

A last checked date applies to the information identified on the page. It does not mean that every claim, plan, or integration was checked or tested on that date. Material factual errors are handled under our Corrections Policy.

Suggest a Source or Report an Error

If you find an outdated claim, broken source, or relevant official document, please contact us through Locomu’s Contact page. Include the Locomu page URL, the detail in question, and a link to the source when available.

Please do not send passwords, access tokens, payment details, or other sensitive account information.