Review Instagram Campaign Posts by Date Range
Review loaded Instagram campaign posts inside a disclosed date window without claiming complete history, conversion, or paid attribution.
On This Page
Review Instagram Campaign Posts by Date Range
Define the campaign From, To, timezone, sort field, and loaded boundary, then verify source posts on both ends of the window. Record public evidence only; public post counts cannot prove conversions, paid attribution, or complete campaign history.
INS Sorter can temporarily sort a supported profile's loaded set by Date, Likes, Comments, or Views and provides supported date presets. It has no arbitrary From/To control, campaign object, or attribution data. If a preset cannot express the exact campaign window, choose one that covers it and exclude outside posts manually.
Make the boundary testable
Use an inclusive interval with a timezone, such as 2026-08-01 00:00 America/New_York through 2026-08-14 23:59 America/New_York. State how the displayed Instagram date maps to that timezone.
This workflow reviews currently loaded public posts on one accessible profile. It is not an ad-account attribution, complete-history, reach, save, share, spend, click, or conversion report.
Copyable campaign-window template
CAMPAIGN:
FROM (inclusive):
TO (inclusive):
TIMEZONE:
SUPPORTED PRESET USED:
LOADED SCOPE: ___ currently loaded cards
SORT FIELD / ORDER:
Boundary check:
- first included source URL / displayed date:
- last included source URL / displayed date:
- nearest excluded-before URL / displayed date:
- nearest excluded-after URL / displayed date:
Post URL | In window? | Visible date | Visible field/value | Observation
VISIBLE CONCLUSION:
NON-ATTRIBUTION WARNING:
OWNER DATA NEEDED:If Instagram shows Aug 1 without a time, label it date_only_uncertain. If the covering preset includes Jul 31, retain that post as excluded_before rather than deleting the evidence.
Six-step review
- Record From, To, timezone, and inclusive/exclusive rules.
- Select the smallest supported preset that covers the window and disclose it.
- Record the loaded-card count before sorting by Date; unloaded posts are outside the evidence set.
- Retain first/last included and nearest excluded-before/excluded-after source URLs.
- Review qualified rows by one field. Likes, Comments, or Views shortlist candidates; missing stays unknown.
- Separate public conclusions from owner data. Move reach, conversions, spend, and attribution to owned analytics.
Verification checklist
- From, To, timezone, and inclusion rules are explicit.
- Preset and loaded scope are recorded; a preset is not presented as arbitrary filtering.
- Both boundary posts and nearest outside posts retain source URLs.
- Six sample rows are labeled in, out, or uncertain.
- Date-only evidence is not assigned a fabricated timestamp.
- Conclusions make no conversion, paid-attribution, or complete-history claim.
Limits
Profile cards may load late, virtualize, or expose date granularity only. Deleted, archived, and inaccessible posts are not restored. If the timezone is unknown or a boundary post cannot be checked, mark the result boundary_unverified.
Use campaign configuration, an ad platform, and owned Insights for a formal performance report. This public-page workflow produces only a content inventory and qualitative review.
Next step
Use the INS Sorter product page for date or metric sorting on one current loaded profile. After boundary verification, move reach, conversion, and paid-attribution questions to owned analytics. Other cluster pages are not public yet.
Frequently asked questions
Is Date sorting a date-range filter?
No. Sorting changes the order of loaded cards. Presets cover supported windows; arbitrary From/To boundaries still need manual verification.
Should From and To days be included?
They can be, but state that rule and interpret both ends in the same timezone.
Do visible Comments prove campaign engagement?
They show a public signal at observation time, not campaign causality, complete engagement, or conversions.
Why retain the nearest outside posts?
They are boundary counterevidence that exposes one-day drift.
Sources
- Sprout Social Influencer Support missing-post guidance
- Mydrop campaign-post audit workflow
- HubSpot published-social-post review
SKU10 boundaries were checked against the local runtime and product contract on August 31, 2026. No login, live campaign collection, deployment, or publication was performed.