

# Chronometrica vs Aolmo Instagram Reels: Which Fits a Posting-Cadence Report?

Choose Chronometrica when your posting-cadence report must count observed public images, carousels, and Reels together. Its documented inputs cover these formats, and its output includes `mediaType` and `publishedAt` when public. Chronometrica publishes this Actor. An Actor is a hosted collection program. [Chronometrica Instagram Metrics Scraper](https://apify.com/chronometrica/instagram-metrics-scraper)

Choose Aolmo when you need the latest public Reels and its new-Reel flag on scheduled runs fits your task. [Aolmo Instagram Reels](https://apify.com/aolmo/instagram-reels)

The choice starts with what your report must count. A sample of Reels can answer a question about Reel posting. It cannot, by itself, show how often an account publishes across several post formats. Support for those formats also does not prove that a collector found every post in a month.

For either tool, define the report first. Then check whether the returned rows meet that definition. Keep manual checks for dates, formats, and sample boundaries.

This comparison uses product documentation checked on October 20, 2026. No new collection run or matched performance test was made for it. The recommendation concerns the documented workflow, not measured speed, accuracy, reliability, or cost.

## Match the collector to the report

The reader need comes from an Instagram competitor-analysis discussion. The author described tracking posting cadence, engagement rate, and content themes, then asked how others combine tools and manual work. That is a workflow question, not a vendor endorsement. [Reader discussion](https://www.reddit.com/r/InstagramMarketing/comments/1sr2v99/how_are_you_doing_competitor_analysis_on_instagram/)

This article takes one defined version of that need: a cadence report that includes images, carousels, and Reels. That mixed-format scope is our chosen use case. It is not a quotation from the reader.

Posting cadence means how often an account publishes posts over time. Before choosing a collector, decide whether “posts” means every required format or only Reels. The same export can be useful for one definition and insufficient for the other.

The table shows the documented fit and the checks that matter. The linked Actor pages support the product details. [Chronometrica documentation](https://apify.com/chronometrica/instagram-metrics-scraper), [Aolmo documentation](https://apify.com/aolmo/instagram-reels)

| Decision point | Chronometrica Instagram Metrics Scraper | Aolmo Instagram Reels |
| --- | --- | --- |
| Required input | Public profile or content inputs; use `mode` and `startUrls` | Known profile inputs |
| Required output unit | One post record for the required image, carousel, or Reel | Reel rows |
| Needed fields | Keep `mediaType` and `publishedAt` when public | Check returned date fields; exact names are not established here |
| Missing-data rule | Separate undated rows; preserve unknown metrics | Dates can be absent outside the latest profile-page posts; error rows are free |
| Main limit | Mixed-format support does not prove complete history | Up to 12 latest Reels per profile |
| Condition that changes the choice | The report needs several post formats | Latest Reels and scheduled new-Reel detection meet the need |

Choose the smaller collection scope when it fully answers the question. More formats do not improve a report that needs only one format. Conversely, a convenient export does not justify leaving required formats out of the report.

## Write a clear report definition before collection

A useful definition names the accounts, the formats, the period, and the counting rule. It also states what you will do when a row lacks a date.

For a mixed-format cadence report, the unit is one published post. A carousel remains one post even when it contains several slides. Counting each slide would raise the post total without adding a publication event.

Use these steps before you start:

1. Name the public accounts. Keep the same account list for collection and review. Record any account that you could not inspect.
2. List the required formats. State whether the report includes images, carousels, Reels, or a smaller set.
3. Set the date window. Choose its start and end before you examine the result. Use one time convention when you place posts on dates.
4. Define the counting unit. Count each post once. Do not count carousel slides as separate publications.
5. Set the missing-date rule. Keep undated records, but exclude them from calculations that require a date.
6. Define the coverage check. Decide how you will compare the sample with the public profile before making claims about quiet periods.

These rules stop the report from changing meaning after collection. If the export contains only one required format, review the collection scope. Do not quietly redefine the report around the available rows.

Also separate cadence from engagement. A dated post can contribute to a posting count even when an engagement metric is unknown. A post with visible metrics but no date cannot establish which day it was published.

## Use a bounded observed sample

A bounded observed sample is the set of records you collected under stated limits. Those limits can include the selected accounts, collection date, formats, and row cap. A row cap is the maximum number of records requested.

Treat the sample as evidence of what you observed. Do not treat it as proof of everything the account published.

A requested calendar window and a collection limit serve different purposes. The window defines the dates your report needs. A row cap limits how many records collection can return. Reaching that cap does not prove that the result covers the full window.

For example, if the oldest dated row is still inside your requested period, you have not shown that the sample reaches the period’s start. Check the public profile and the collection settings before you describe the whole period.

The same care applies to an empty day in a chart. It may mean that the sample contains no dated post for that day. It does not automatically prove that the account published nothing.

Neither source establishes a guaranteed complete historical calendar. Keep manual coverage checks in the process. This report does not cover Stories, private Insights, or sentiment. Those require separate evidence from the public posts used here. [Chronometrica documentation](https://apify.com/chronometrica/instagram-metrics-scraper), [Aolmo documentation](https://apify.com/aolmo/instagram-reels)

## Work through a fictional collector choice

The following example is fictional. It is not a test, a customer result, a live dataset, or a measured cost comparison.

An analyst must prepare a September report for a brand. The report must compare all observed post formats. The fictional source sample contains six Reels, four images, and two carousels.

The arithmetic is:

`6 Reels + 4 images + 2 carousels = 12 posts`

Each carousel counts once. Its slides do not increase the number of published posts. These twelve posts form the fictional sample. They do not establish a complete September calendar.

A Reel-only export would contain six of those twelve observed posts. That export could support an analysis of the observed Reels. It would leave the image and carousel publication events out of the mixed-format cadence report.

The analyst therefore chooses a mixed-format collector. Chronometrica fits this requirement because its documentation supports the required formats. That is a fit decision. It does not prove that a future run will recover this fictional sample or every historical post. [Chronometrica documentation](https://apify.com/chronometrica/instagram-metrics-scraper)

Next, the analyst checks the returned dates. Any undated record stays in a separate group until its publication date can be established. Its existence still matters to the coverage review, but the analyst cannot place it on the September calendar by guesswork.

If the brief changes to recent Reels only, Aolmo fits that narrower scope. [Aolmo documentation](https://apify.com/aolmo/instagram-reels)

The example shows why the report definition must come first. A smaller export can be sufficient for a smaller question. It becomes insufficient when the question requires publication events that the export does not represent.

## Start with the saved Task and apply the checked input

A Task is a saved input preset for an Actor. Chronometrica has a public starting Task for Instagram profile content performance. Its page was checked, but that check does not establish the input currently saved on the page. Apply the input below before a run. [Profile content performance Task](https://apify.com/chronometrica/instagram-metrics-scraper/examples/instagram-profile-content-performance)

```json
{
  "mode": "profileUrls",
  "startUrls": [
    "https://www.instagram.com/natgeo/"
  ],
  "maxItems": 25
}
```

Start with the saved Task and apply the checked input

Replace the example profile with the intended public source. The example does not show that the profile is available now or that it will return a particular result.

The input passed a static check against the saved public schema. A schema defines the accepted input structure. A static check checks that structure, including field names, allowed values, and numeric bounds. It does not collect records or test source availability.

Here, `mode` selects profile input. `startUrls` holds the source list. `maxItems` sets an optional total limit on returned metric rows across direct content and profile discovery. The value `25` is a collection bound, not a promise of 25 posts or a complete month. [Chronometrica input documentation](https://apify.com/chronometrica/instagram-metrics-scraper)

Start with a sample you can inspect. Review its rows before expanding collection. A larger request does not fix an unclear format definition, an incorrect source, or a missing-date rule.

If you collect several profiles together, remember that the stated cap applies across the collection. Check what each account contributed before comparing account totals.

## Check the result before you calculate cadence

Use a short acceptance check after collection. The result is ready for a cadence calculation only when you understand its post units, usable dates, and coverage limits.

1. Confirm the sources. Check that records belong to the intended public accounts. Keep failed or unresolved inputs visible in your working notes.
2. Check the formats. Review `mediaType` where available. Compare the observed formats with the report definition. A missing format needs investigation; it does not prove the account never used it.
3. Remove duplicate post records. If collection overlaps or you combine exports, make sure the same post contributes only once.
4. Review publication dates. Keep `publishedAt` where public. Put missing dates in a separate group. Do not substitute collection time for publication time.
5. Apply the date window. Include dated records only when they fall inside the chosen period. Keep records outside the period separate from the calculation.
6. Review the collection boundary. Check whether the sample reached its row cap and whether it reaches the start of the requested window.
7. Inspect public coverage manually. Compare the sample with visible profile content. Focus on the window boundaries and places where a required format appears to be missing.
8. Label the result accurately. State that it describes observed, dated posts unless your checks support a stronger claim.

Do not convert unknown values to zero. A missing date is not a date with no activity. A missing engagement metric is not evidence of no engagement.

Keep separate counts for records collected, dated records inside the window, undated records, and records outside the window. These groups explain why the number used in a chart may differ from the number returned by collection.

Once the sample passes these checks, count the included posts by date and format. You can then compare the distribution of observed publication events across the period. If coverage remains uncertain, state that beside the chart. Keep the claim within the checked sample.

For the full analysis method, use [How to Audit Instagram Content Formats and Posting Cadence](/en/articles/ig-format-cadence-map/). If you later compare views from posts published in a period, use the separate [publication-cohort view contribution guide](/en/articles/instagram-publication-cohort-view-contribution/). That question requires its own inclusion rules.

## Give tools and manual work clear roles

Use collection to produce records that you can sort and inspect. Use manual work to check whether those records answer the report question.

Manual review matters most where an error would change the conclusion. Check for a missing required format, an unclear publication date, a duplicate post, or a sample that stops before the reporting window begins.

Do not spend equal effort checking every field when the report needs only a few. For cadence, publication date, format, source, and post identity matter first. Other metrics become necessary only when the report asks another question.

Keep a short coverage note with the report. State the collection date, requested period, required formats, collection bound, and number of undated records. Explain any unresolved gap that could change how a reader understands the result.

If the sample cannot support the original question, revise the collection or narrow the conclusion openly. For example, a report can describe observed dated posts without claiming a complete posting calendar. The label must match the evidence that remains after the checks.

This division of work gives the reader a practical answer to the tools-versus-manual question. Use the collector for repeatable record gathering. Use focused manual checks to confirm scope and resolve uncertainty.

## Start the mixed-format report

For a report that must count observed public images, carousels, and Reels together, open the [profile content performance Task](https://apify.com/chronometrica/instagram-metrics-scraper/examples/instagram-profile-content-performance). Apply the checked input, replace the example source, and choose a collection bound that you can review. Keep undated records separate from date-based calculations.

Chronometrica publishes the owned [Instagram Metrics Scraper Actor](https://apify.com/chronometrica/instagram-metrics-scraper). Use it when its checked mixed-format support matches your report. Before expanding collection, confirm that the first sample contains the required post units and usable dates. If the report needs only recent Reels, reconsider the narrower choice described above.

## Sources

- [Chronometrica Instagram Metrics Scraper: public documentation and input schema; checked October 20, 2026; supports the stated format and input facts, with no new collection run or proof of complete history](https://apify.com/chronometrica/instagram-metrics-scraper)
- [Aolmo Instagram Reels: public documentation; checked October 20, 2026; supports the stated workflow limits, with no new collection run or matched performance test](https://apify.com/aolmo/instagram-reels)
- [Chronometrica Instagram profile content performance Task: page availability and intended title reported in the October 20, 2026 source brief; separate page-check date not supplied; the page check does not prove the current saved input](https://apify.com/chronometrica/instagram-metrics-scraper/examples/instagram-profile-content-performance)
- [InstagramMarketing discussion about competitor-analysis workflows: reader evidence included in the October 20, 2026 source brief; separate check date not supplied; supports the workflow need, not a vendor endorsement or a claim that the reader requested mixed formats](https://www.reddit.com/r/InstagramMarketing/comments/1sr2v99/how_are_you_doing_competitor_analysis_on_instagram/)
- [How to Audit Instagram Content Formats and Posting Cadence: related analysis guide identified in the October 20, 2026 source brief; separate check date not supplied; provides the broader method rather than comparative test evidence](https://chronometrica.com/en/articles/ig-format-cadence-map/)