Web Tidy
Blog

Instagram Follower Export Blank Fields: Null Does Not Mean No

Diagnose blanks across the 14-column Instagram follower CSV/XLSX without confusing unknown, false, partial tasks, or missing rows.

Aug 31, 2026Instagram
On This Page

A blank cell means the current Followers or Following response did not return that value. It is not No, and it does not by itself prove export failure. Identify the field class, check whether the blank affects one row or the whole column, then record confirmed rows and the task's final state. Do not rerun merely to fill optional cells, and do not guess values from another column, another account, or an AI model.

In SKU32, the three boolean fields must preserve Yes / No / blank. collectedAt is local normalization time, not accurate follow time. A partial state describes how the task ended; a blank describes the evidence for one value.

Disclosure: Web Tidy publishes this guide and develops INS Follower Exporter. Its 14-column and task-state facts come from the current local 1.0.5 runtime and writer. Two same-intent TopN pages and one different-URL step-by-step page were opened and read in full on August 31, 2026. Those guides do not define SKU32's exact three-state writer or recovery tree.

Freeze the 14-column contract first

Field classFieldsCurrent writer ruleAllowed conclusion when blank
Identityid, usernameStrings; id is the default deduplication keyUnexpected in a confirmed row; inspect the original file/conversion path
Optional platform identitypkPreserved only when returned; never synthesized from idUnknown/not returned
Profile displayprofileUrl, fullName, profilePicUrlOptional stringsThe relationship node did not return it; not proof of no name/photo or deletion
Three-state flagsisVerified, followedByViewer, requestedByViewertrue→Yes, false→No, undefined→blankUnknown/not returned; never automatically No
Export contextaudience, sourceProfile, sourceProfileUrlFollowers/Following direction and target provenanceCheck the untouched SKU32 artifact and secondary transformations
ProvenancecollectedAt, rowIndexLocal normalization time and final local orderNever fill with follow time or Instagram rank

CSV and native XLSX use the same column order. SKU32 does not output email, phone, bio, follower count, or JSON. A column that does not exist in this schema is not a “blank field.”

Seven-node field diagnosis tree

N1 Is the column in the fixed 14-column schema?
├─ No → It may be a derived column or another product's schema.
│       Action: return to the untouched SKU32 CSV/XLSX; do not call an absent column blank.
└─ Yes → N2
 
N2 Is id or username blank?
├─ Yes → Identity integrity is abnormal for a confirmed row.
│       Action: preserve the file and inspect import/conversion; never fill from fullName, pk, or rowIndex.
└─ No → N3
 
N3 Is it pk/profileUrl/fullName/profilePicUrl?
├─ One-row blank → Allowed conclusion: the relationship node did not return that optional value.
│                  Action: preserve blank; match with id + username.
├─ Whole-column blank → Confirm the untouched artifact and same run; report column coverage=0%.
└─ Otherwise → N4
 
N4 Is it isVerified/followedByViewer/requestedByViewer?
├─ Yes → Preserve Yes / No / blank.
│       One-row or whole-column blank means unknown/not returned; never convert blank to No.
└─ No → N5
 
N5 Is it audience/sourceProfile/sourceProfileUrl?
├─ audience/sourceProfile blank → Source context is insufficient.
│   Action: check target and Followers/Following; do not merge files until repaired.
├─ sourceProfileUrl only blank → sourceProfile can still identify the handle; keep URL unknown.
└─ Otherwise → N6
 
N6 Is it collectedAt/rowIndex?
├─ Yes → Inspect the original writer artifact.
│       Forbidden inference: collectedAt=follow time; rowIndex=Instagram rank.
└─ No → N7
 
N7 Check task state and distribution
├─ completed + confirmed rows → Apply the field rules above.
├─ partial + confirmed rows → Use confirmed rows; record the partial reason and never claim complete coverage.
├─ failed/attention + no exportable confirmed rows → Resolve access/source state before field statistics.
└─ displayed profile count > confirmed rows → This is a coverage/missing-row question, not a blank-cell question.

This tree covers pk, profileUrl, all three booleans, sourceProfileUrl, and collectedAt. It deliberately separates one-row blanks, whole-column blanks, partial tasks, and missing rows.

Calculate coverage per field

nonblank_coverage(f) = nonblank confirmed rows for f / confirmed rows × 100%
identity_usable = rows with nonblank id AND username / confirmed rows × 100%

If confirmed rows = 0, report coverage as N/A, not 0% or 100%. Do not average optional columns into one “file completeness” score. Identity, profile display, flags, context, and provenance answer different questions.

Example: a completed Followers file has 900 confirmed rows. All 900 have id+username, 760 have profilePicUrl, and 810 have a known Yes/No isVerified value:

identity_usable = 900 / 900 = 100%
nonblank_coverage(profilePicUrl) = 760 / 900 = 84.4%
known_coverage(isVerified) = 810 / 900 = 90.0%
blank isVerified = 90 / 900 = 10.0% unknown, not No
terminal_state = completed

This does not prove the 900 rows are the complete profile list, and it does not prove 90 accounts are unverified. It describes field evidence within this bounded file.

Different symptoms require different actions

SymptomCheck firstWhat remains usableStop line
One optional profile blankSame-row id,username, untouched fileIdentity matching and returned fieldsDo not visit profiles to “fill” the row
Whole optional column blankUntouched SKU32 artifact and same runReport 0% column coverageDo not claim every account lacks the attribute
Three-state flag blankOriginal writer vs secondary importYes/No/blank groupingDo not convert blank to No
Context/provenance blankTarget, audience, sourceProfile, final stateConfirmed rows with adequate provenanceDo not merge/attribute when source cannot be restored
Partial fileConfirmed, partial reason, selected ceilingConfirmed rows and per-field coverageNever claim complete; rerun is not the default fix
Fewer rows than displayed countAudience, ceiling, confirmed, dedupe, stateCurrent confirmed snapshotMove to coverage diagnosis; do not fill fields

Six-step verification

  1. Preserve the untouched CSV/XLSX and clean a copy.
  2. Record target, Followers/Following, selected ceiling (100/200/500/1,000), confirmed rows, and final visible state.
  3. Verify the exact 14-column order; treat deleted columns from secondary conversion separately.
  4. Calculate identity usability and per-optional-field nonblank coverage.
  5. Preserve Yes/No/blank and the original meanings of collectedAt and rowIndex.
  6. Consider a new run only when identity/context is unusable or the original artifact is damaged. Optional blanks alone are not a rerun reason.

Limits and forbidden inferences

  • Blank does not prove No, unverified, no photo, private, deleted, or failed.
  • partial does not mean every field is blank; completed does not make optional fields nonblank.
  • Confirmed rows, selected ceiling, and displayed profile count are not interchangeable.
  • Followers and Following files must not be interpreted as the same direction.
  • collectedAt is not follow/unfollow time; rowIndex is not platform rank.
  • SKU32 only allows 100/200/500/1,000 rows. It promises neither a full list, unlimited rows, nor background monitoring.
  • This guide does not bypass private access, login, challenge, rate limit, or unavailable states.
  • Blanks do not authorize contact enrichment, CRM sync, or outreach.

A qualified next step

If the current-session target, Followers/Following choice, 100/200/500/1,000 ceiling, fixed 14-column CSV/XLSX, confirmed-row contract, and partial boundary fit your job, review Instagram Follower Exporter. If you need enrichment, JSON/API, unlimited rows, or monitoring, it is not the right route.

Frequently asked questions

Does blank isVerified mean the account has no blue badge?

No. Blank is unknown/not returned. Only explicit No is false.

Can I copy id into a blank pk?

No. Use id as the comparison key, but preserve pk only when returned.

Can a blank profilePicUrl column prove that no account has a photo?

No. Report 0% nonblank coverage for this file, then verify the untouched artifact.

Do optional blanks make a task partial?

Not by themselves. Blank is field evidence; partial is a task termination state with confirmed rows.

When should I rerun?

When the original artifact is damaged or identity/source context is unusable and access permits another run—not merely because optional values are blank.

How should I report 760 image URLs in 900 rows?

Write “900 confirmed identity rows; profilePicUrl nonblank coverage 84.4%.” Do not call the file 84.4% complete.

Does collectedAt tell me when the account followed?

No. It is local normalization time, not historical follow time.