“Educational content performed best” sounds useful until you discover that one person labelled tutorials as Education, another used Tips, and a third filed the same posts under Reels. The spreadsheet has numbers. It does not yet have a reliable classification system.
That is where to start. At Dumpor, we recommend defining what each content pillar means before comparing results. A modest spreadsheet can support sound editorial decisions when its categories, measurement windows, and calculations remain consistent.
To track Instagram content pillars without paid analytics, create a pillar dictionary and a post log in a free spreadsheet tool such as Google Sheets. Give every published item one primary pillar, then record its format, objective, campaign, and paid status in separate fields. Add performance figures from your own native Instagram Insights at a consistent post age. Use filters, formulas, and pivot tables to compare publishing volume and results within similar groups. Keep missing data separate from zero, show sample sizes, and avoid summing post reach as though it were a unique audience total. Finish each review with a specific editorial action rather than a ranking of vaguely defined themes.
A content pillar is a recurring subject or area of audience value that guides what you publish. For measurement, it needs a practical definition: another person should be able to read it and classify a post in much the same way you would.
A format answers a different question. Carousel, Reel, single image, and Story describe how the material is presented. A campaign identifies a coordinated initiative, while an objective explains what the post should accomplish. Keeping these fields separate lets you ask whether a theme works across formats instead of confusing a topic with its packaging.
Start with a manageable set of categories. Three to five can be a useful starting point for a small account, but the right number depends on the work you actually publish. Adding more categories does not automatically produce more insight.
For each pillar, write its purpose, what belongs in it, what does not, and a borderline example. Use short, stable labels that fit comfortably in a dropdown menu.
| Pillar | Include | Exclude | Borderline rule |
|---|---|---|---|
| Product care | Cleaning, maintenance, storage, troubleshooting | Choosing between products | Classify by whether the main question arises before or after purchase |
| Buying guidance | Comparisons, compatibility, selection advice | Routine care instructions | A comparison stays here even when it uses a customer example |
| Customer applications | Real uses, projects, customer outcomes | General advice with no specific application | A customer quote alone does not determine the pillar |
| Company updates | Service changes, team news, milestones | Every post mentioning the brand | Use only when the company announcement is the main subject |
Most posts touch more than one theme. A customer story may teach a technique, and a product comparison may contain a promotional offer. Assign the primary pillar according to the main audience question or editorial promise, not every topic mentioned along the way.
If useful, add a secondary tag in another column. Keep it out of the main pillar totals unless you deliberately create a separate multi-label analysis. Counting a post under three pillars and then adding those counts overstates how much content you published.
Use four tabs: Pillars, Posts, Summary, and Decisions. The first holds definitions, the second holds the data, the third contains the analysis, and the fourth records what you will do with the findings.
For a straightforward starting system, record one standard performance snapshot per published item in the Posts tab. If you later want several checkpoints, create a separate Snapshots tab keyed to the post ID and collection window. Do not duplicate the entire post row and then count both snapshots as two posts.
A carousel counts as one published post in this setup. For Stories, decide whether your unit is an individual frame or a defined sequence. Record that choice and report Story units separately from feed posts. Do not add frame-level reach and call the sum a sequence’s unique audience.
The following layout supports the formulas later in this guide. Optional fields such as campaign, secondary tag, and contextual notes can follow column N.
| Column | Field | Entry rule |
|---|---|---|
| A | Post ID or URL | One stable identifier for each published item |
| B | Published at | A real spreadsheet date/time value |
| C | Primary pillar | Choose from the pillar dictionary |
| D | Format | Use a controlled list |
| E | Objective | State the intended audience action or value |
| F | Distribution | Organic, boosted, or another clearly defined status |
| G | Collected at | When the metrics were recorded |
| H | Observation window | For example, 7-day |
| I | Accounts reached | Numeric value, if available with this definition |
| J | Saves | Numeric value from matching post Insights |
| K | Comments | Numeric value from the same scope |
| L | Shares | Numeric value from the same scope |
| M | Collection status | Pending, Complete, or Missing |
| N | Save rate by reach | A calculated field |
Set data-validation dropdowns for primary pillar, format, distribution, and collection status. In Google Sheets, these can be created through the dropdown or data-validation controls. Source the pillar options from the dictionary so the approved labels remain easy to maintain.
Configure invalid entries to be rejected where appropriate. Otherwise, “Product Care,” “Care tips,” and “Maintenance” may become three categories even though the team intended one. Colours can make a sheet easier to scan, but the stored text value should carry the meaning.
Freeze the header row, turn on filters, and keep merged cells out of the data table. Protect calculated columns from accidental editing if several people contribute. Put explanations in notes or the dictionary rather than inserting extra title rows between records.
Use Insights available to the account you manage. Open the relevant post’s View insights screen or the account’s native dashboard, and record the figures that match your chosen fields. Meta Business Suite may provide another native collection route, depending on access and available views.
Do not compare a new carousel with a Reel that has accumulated results for six months. If the screen supplies cumulative figures, your seven-day measurement comes from capturing them at that age. A date filter elsewhere does not necessarily transform an individual post’s lifetime total into a seven-day result.
Use Pending for posts that have not reached the checkpoint and Missing when the required data cannot be obtained. A genuine zero belongs in a numeric cell; unavailable data does not. Keep a short reason for missing values in the notes.
You do not need a complicated scoring model. Start with publishing counts, content mix, and a rate relevant to the post’s purpose. The formulas below use English function names and commas; spreadsheet locale settings may require different separators.
With the column layout above, enter this in N2 to calculate saves divided by reach:
=IF(AND(ISNUMBER(I2),I2>0,ISNUMBER(J2)),J2/I2,"")
Format column N as a percentage and fill the formula down. A post with 30 saves and reach of 1,500 displays 2%. When the denominator is unavailable or zero, the formula leaves the result blank. When saves are genuinely zero and reach is positive, it returns 0%.
This calculation assumes both figures cover the same post, collection point, and distribution scope. The formula cannot check that for you. Filter by collection status and window before using the rates in a summary.
To count Product care posts published in September 2026, use:
=COUNTIFS(Posts!C2:C1000,"Product care",Posts!B2:B1000,">="&DATE(2026,9,1),Posts!B2:B1000,"<"&DATE(2026,10,1))
The exclusive upper boundary includes all publication times on 30 September. Replace the pillar text and dates with cell references when building a reusable summary, and extend the ranges as your log grows.
For a deeper explanation of the numerator and denominator, see our guide to evaluating Instagram carousel saves. A rate is useful only when its definition remains visible.
First build an output summary: how many published items belonged to each pillar, in each format, during the selected month? This shows what the team delivered, including recent posts whose performance checkpoint is still pending.
In Google Sheets, select the Posts data range and use Insert → Pivot table. Add Primary pillar as rows, Format as columns, and a count of Post ID as the value. Filter Published at to the desired period. Check that each source row represents one published item.
Then create a performance summary using only comparable collected records. Filter to the same observation window, the appropriate distribution status, and the format or formats you intend to compare. Include the number of measured posts alongside the results.
Do not interpret a pillar’s total saves without its publishing volume. A theme with 12 posts has more opportunities to accumulate saves than a theme with two. Per-post summaries help, but they still need context about audience, format, and purpose.
Consider this fictional review of organic carousels measured at the seven-day checkpoint:
| Pillar | Measured posts | Median saves per post | Median save rate by reach | Suggested next step |
|---|---|---|---|---|
| Product care | 6 | 42 | 2.1% | Test another practical reference format |
| Buying guidance | 5 | 35 | 1.6% | Review which questions attracted useful follow-ups |
| Customer applications | 2 | 18 | 0.9% | Collect more comparable examples |
Product care looks promising for saving behaviour in this example. That does not prove it is the best pillar for enquiries, purchases, or audience growth. Customer applications has only two observations, so its lower result is a reason to investigate rather than abandon the category.
Avoid summing post reach and calling it unique pillar reach. The same account can see several posts. Similarly, an unweighted mean of post-level rates and total saves divided by summed reach are different calculations. Name the method you use and keep it consistent.
Suppose every Product care post is a carousel and every Company update is a single image. A difference between the groups cannot be attributed confidently to topic alone. Format, audience interest, creative execution, and publication timing may all contribute.
Compare within formats when there are enough examples, or show a pillar-by-format table that makes the imbalance visible. Record collaborations and paid support as well. A boosted launch post should not quietly define the baseline for ordinary organic publishing.
Keep paid and organic measurement scopes aligned. If saves include promoted activity but reach excludes it, the resulting rate is not a clean comparison. Where the native interface does not provide the necessary split, disclose the limitation instead of manufacturing one.
Write the decision in a separate log: what you observed, what might explain it, what you will test, who owns the change, and when you will review it. Keep the hypothesis separate from the result.
For example: “Product care carousels had the highest median seven-day save rate in this group. We will publish two further reference guides, keeping the format and observation window consistent. We will review saves, reach, and relevant follow-up questions before changing the wider content mix.”
A short monthly check keeps the sheet usable:
The measurement data should come from your authorised native Insights. Dumpor is a public Instagram viewing service; it does not supply your account’s private saves, reach, or other owner-only performance figures.
Use a spreadsheet to connect those native figures to your own editorial taxonomy. This can be enough for a manageable publishing volume, provided someone maintains the records. The trade-off is collection time and discipline, not a requirement to purchase software before you can learn anything.
If you have a question about a public page displayed through our service, contact Dumpor with its address and a description of the issue. Keep private reporting files and account credentials out of the request.
FAQ
Start with a small set that covers your recurring work and can be applied consistently. Three to five may be manageable, but it is not a platform rule. Add a category when it represents a meaningful editorial distinction, not simply because a single unusual post does not fit. Test your definitions on existing content before expanding the list.
It can touch several themes, but assign one primary pillar for the main publishing and performance summary. Use a separate secondary-tag field when needed. If you analyse multiple labels, explain that posts may appear in more than one group and avoid presenting the sum of group counts as the number of unique posts published.
Yes. A free spreadsheet and the native Insights available to your account can support a manual tracker. You will need to enter or import the data, maintain category definitions, and collect comparable snapshots. Spreadsheet formulas organise those records; they do not automatically unlock private metrics or retrieve historical data that is no longer available.
Leave the numeric field blank and record the collection status and reason. Do not replace missing information with zero. Exclude incomplete records from calculations that require the missing field, and disclose the measured sample size. A pillar with eight published posts but only three complete snapshots should not be described as having eight measured results.
Only if the formula and purpose are appropriate, and even then it should not be the sole measure. A support guide, company announcement, and product comparison may serve different goals. State the numerator, denominator, and observation window. Review counts and context alongside rates, and do not compare differently defined engagement percentages as though they were identical.
Keep a change log with the old definition, the new definition, and the effective date. If practical, reclassify the historical posts used in the comparison according to the new rules. Otherwise, mark a break in the series and explain it. Retaining a stable pillar ID can help when only the display name changes, but it does not solve a change in meaning.
Look for repeated changes across comparable posts, using the same measurement window and distribution scope. Show the sample size and check whether a single standout drives the result. Consider format, paid support, and changes in audience before attributing improvement to the topic. Use the evidence to plan a controlled editorial test rather than declaring causation from one strong post.