- Published
- Oct 30, 2026
- Updated
- Nov 5, 2026
- Reading time
- 18 min read
Reddit Ads API vs UI: Reconcile Daily Reporting Gaps
Match Reddit Ads API and Ads Manager reports by timezone, units, filters, pagination and reporting maturity, with a practical discrepancy audit and example.

In this guide (13 sections)
If Reddit Ads API daily values disagree with Ads Manager, preserve both exports and compare the same reporting contract: account, entity IDs, fields, filters, time boundaries, timezone, monetary units and extraction time. Then trace raw response pages through your normalization code to the final table. Start with one completed day and a small known entity set before investigating an entire account history.
Two real older posts, a Reddit developer question and its bug-report counterpart, describe daily v3 Ads API values that differ from the UI. They come from the same author and describe substantially the same problem, so they are one demand signal, not two independent confirmations. The visible replies redirect the author rather than establish a technical cause.
The useful result is a bounded finding: a unit conversion is wrong, a page was omitted, a reporting boundary differs, or an unexplained remainder persists. Matching totals after an arbitrary adjustment is not that finding.
Freeze one comparison contract#
Use the same account and retain stable campaign, ad-group and ad IDs. Friendly names can change or collide. Save the Ads Manager export with its selected columns and settings, and retain the API request configuration without credentials.
| Contract item | Evidence to retain |
|---|---|
| Account and entities | Account ID and included entity IDs, kept private |
| Endpoint and version | Actual API route and client version |
| Date interval | Exact requested boundaries and UI-selected dates |
| Timezone | API parameter, UI setting and effective offsets |
| Fields | Exact API metric names paired with UI columns |
| Breakdowns | Every dimension and the intended row grain |
| Filters | Entity selection, status criteria and conversion-source scope |
| Conversion basis | Relevant action, attribution window and channel settings |
| Currency and units | Account/report currency and each field's normalization rule |
| Snapshot | Extraction timestamp and processing status or limitations |
Keep a copy of the normalization and aggregation logic used for that comparison. A dashboard label saying “Spend” does not establish whether its stored value has already been divided by a scale factor.
The broader platform comparison guide explains why similarly named totals can count different populations. This guide narrows that discipline to Reddit's reporting interface and the client processing its results.
Freeze the report contract for one completed day
Compare account, entities, fields, filters, timezone and extraction time before changing normalization. Discuss the API and UI evidence available.
Discuss a measurement questionA short inquiry to scope relevant options; no campaign access is needed.
Name the field before converting the value#
Reddit's v3 reporting metric reference lists the supported field names. Record the exact name instead of inferring meaning from a shared suffix such as value or cost. An event count, a monetary value and a calculated rate need different handling.
The Get A Report reference specifies different monetary scales: SPEND and listed cost metrics such as CPC, CPV and ECPM use a divisor of one million, while fields matching CONVERSION*TOTAL_VALUE use a divisor of 100. Follow the documented rule for the actual field, not one universal currency conversion.
Create an explicit normalization registry for the fields your client requests:
| Stored observation | Diagnostic treatment |
|---|---|
| Raw response value | Preserve unchanged with its field name |
| Documented scale | Store the rule and documentation version |
| Normalized value | Apply the rule exactly once |
| Currency | Retain the account/report currency separately |
| Presentation value | Round only for the intended display or export |
Do not divide impression or click counts by a monetary scale. Do not divide a value again if an upstream connector already normalized it. Preserve enough numeric precision before aggregation to avoid a cent-rounded row creating a different account total.
For rates, retain their numerator and denominator where available. An arithmetic average of several ad-level CPCs is not generally the account CPC: ads can have very different click volumes. Recalculate only when the underlying metric definitions and matching population support it.
Match the actual day, not just its printed label#
Reddit's adaptive timezone guide says reports default to UTC. It also states that time_zone_id is effective when the breakdowns include date details; without them, the request's time-boundary offsets can align the desired interval.
Check both the grouping day and the requested interval. Changing a timestamp's display after retrieval does not necessarily recreate a report originally grouped under another day boundary.
Hypothetical boundary example: an event at 23:30 UTC on 10 October falls at 05:00 on 11 October in Asia/Kolkata. Two correct daily labels can differ while referring to the same event. A report covering whole calendar days under those two zones can also include different boundary events.
Record the actual zone identifier and boundary timestamps. For daylight-saving regions, use the appropriate date-specific offset rather than a permanently hard-coded one. The API guide exposes timezone information including daylight-saving status; preserve the evidence applicable to the queried dates.
Confirm how each interface interprets its start and end boundaries. Do not assume that a UI's inclusive-looking date label and a client's timestamp interval select identical records. Use a small authorized boundary test or request clarification when the documented contract is unclear.
A difference concentrated around midnight is a timezone hypothesis. It becomes a finding only after the boundary and affected records support it.
Verify filters, conversion scope and row grain#
Reddit's filter guide distinguishes entity filters from conversion-data filters. It states that multiple entity filters follow OR behavior. A client that expects an intersection can therefore request a different population from the one its author intended.
Compare the resolved entity IDs with the selected Ads Manager scope. Also preserve any effective-status criteria. Do not silently assume that a currently inactive entity had no historical delivery or remove its rows during a historical reconciliation without establishing the intended scope.
For conversion metrics, the same guide points to the ad account's attribution window and permits filtering conversion data by channel through conversion_metrics and action_sources. Capture those settings without changing them to force agreement. A website-only selection and an app-inclusive total need not match.
Build a row key from the exact requested grain, such as date, ad ID and every additional breakdown. Verify that your loader preserves those dimensions. Joining a daily-ad row to multiple metadata rows can multiply its money without the API having returned duplicates.
Do not add separate report totals together merely because they have different breakdowns. The same delivery may appear once in a country report and once in a device report. Those are alternative views unless evidence establishes disjoint populations.
Check custom conversions at the request and parser boundary#
A custom-conversion column needs an event identity as well as a metric. Reddit's custom conversion reporting guide recommends the name-keyed structure: provide the exact, case-sensitive event name in conversion_custom_events, select its metrics and retain the relevant action sources. The guide uses Get Last Fired At to discover names. Its response example places returned values under the custom event's name, with each value carrying its metric type and, where applicable, action source.
Treat migration as two contracts: the request must select the intended event, and the parser must preserve the returned structure. Replacing an old field name while leaving a loader that reads only flat metrics can leave the dashboard empty even when the raw response contains useful values. That is a hypothesis to test against a saved response, not a diagnosis of the older forum question.
Use a small comparison receipt:
| Boundary | Evidence to preserve |
|---|---|
| Event identity | Exact emitted custom name, discovery evidence and destination account |
| Selection | Request object, metric types, action sources and dates |
| Raw response | Original nested event name and every returned value |
| Interpretation | Event name, metric type, source where present, and documented unit |
| Output | Stored row key, displayed label, missing-value policy and extraction time |
Keep conversion_custom_events beside fields in the request's data object, following the official example; do not insert it as a string field. The published replacement guidance distinguishes this structure from the legacy numbered fields. It says slot-based fields still return data while heading toward deprecation. That is different from assuming every legacy request is already rejected.
For a controlled comparison, choose one known custom event and one completed period. Save the legacy slot mapping if the old integration uses it. Compare the exact requested event and scope before deciding whether old and new outputs should agree. Keep the original response snapshots so a label lookup or parser change cannot erase the evidence behind an earlier report.
Hypothetical parser check: suppose a saved test fixture contains two source-qualified values of the same count metric: 8 for WEBSITE and 2 for APP. A loader that keeps only WEBSITE displays 8; one that correctly retains both has two rows. Their sum is 10 only under the explicit assumption that the selected metric and populations are additive. This is invented arithmetic, not a Reddit account result. It does not authorize adding different attribution methods or combining a rate with a count.
Do not turn every missing response member into numeric zero. Preserve separate states for an explicitly returned zero, an unreturned selection, a rejected request and a parser failure. If a requested event is absent, check its spelling, scope and raw structure before publishing a zero-conversion conclusion. If the raw value exists but the transformed value is missing, the investigation has reached your processing layer.
The Pixel and CAPI QA guide owns receipt and duplicate handling. This report check comes afterward: a properly received occurrence, a deduplicated occurrence and an attributed custom-conversion value still establish different things. A reporting migration should not rewrite the underlying business event merely to make a column populate.
Keep app-install attribution sources in the field mapping#
The same replacement notice says unified app-install fields such as APP_INSTALL_INSTALL_COUNT no longer return data and lists source-specific alternatives, including APP_INSTALL_MMP_INSTALL_COUNT, APP_INSTALL_REDDIT_INSTALL_COUNT and APP_INSTALL_SKAN_INSTALL_COUNT. Preserve which source the requested field represents. The notice's present-tense availability statement and its future effective date are separate documentation observations; neither is a live test of your account.
Create a migration map containing the old field, proposed replacement, event definition, attribution source, unit, parser destination and matching UI column. A replacement is not equivalent just because it ends in INSTALL_COUNT. Have the reporting owner confirm which source answers the original business question before changing the saved dashboard.
Avoid summing those attribution-source fields into a supposedly deduplicated install total without evidence that their populations are disjoint. Keep a definition change visible in the report history instead of silently joining the new series to an old line. Where an external store count is also involved, establish the store acquisition unit and first-launch boundary before interpreting the residual.
Prove that the response is complete#
Reddit's API introduction says list endpoints, including Get a Report, are paginated. Follow the returned pagination.next_url directly; its absence marks the final page. Do not invent the next request by manipulating a guessed page number or token.
Keep a small retrieval manifest: request fingerprint, page sequence, retrieval time, status, row count and whether a next URL was present. Record failure separately from a valid empty result. A successful first response does not establish that all pages were downloaded.
Inspect retries and persistence as well as retrieval. An interrupted run that restarts from the beginning can append repeated pages if the storage layer cannot distinguish them. Conversely, a failed later page can leave a plausible partial total that looks like an ordinary reporting gap.
Compare row counts and totals at three boundaries:
- Raw pages received from the API.
- Normalized rows after units, names and dimensions are interpreted.
- Final stored or displayed rows after joins and aggregation.
If raw pages reconcile but the dashboard does not, the next investigation belongs in transformation or presentation. If page retrieval is incomplete, do not explain the shortfall with attribution. Preserve the unmodified payload privately and redact tokens and sensitive identifiers from shared diagnostics.
Keep reporting maturity separate from a fixed defect#
The current Get A Report reference warns that metrics can take up to six hours to stabilize and describes daily refresh handling for late-arriving conversion data associated with earlier periods. That is a reason to preserve dated snapshots, not a guarantee that every mismatch disappears after one wait.
Retrieve the same completed period again after an appropriate processing interval, with the same fields and settings. Compare each source at comparable observation times. Keep the original files so later retrieval does not erase what the client initially reported.
Separate two questions: did the API and UI differ at the same snapshot age, and did a historical period change between snapshots? An early API export compared with a later UI export can combine both effects.
If spending differs while conversion counts agree, first inspect the monetary and population branches. If only conversions continue changing, inspect the specific conversion field, source, settings and maturity. Neither pattern independently proves a platform bug.
Worked example: units, missing pages and a remaining gap#
Hypothetical example. These invented figures assume a matching currency, completed day and entity scope. They are not Reddit account observations or customer results.
| Evidence | Raw amount | Normalized amount |
|---|---|---|
| Page 1 SPEND | 12,500,000 | 12.50 currency units |
| Page 2 SPEND | 7,500,000 | 7.50 currency units |
| Complete SPEND total | 20,000,000 | 20.00 currency units |
| A separate CONVERSION…TOTAL_VALUE field | 18,000 | 180.00 currency units |
A client that stops after page 1 displays 12.50 instead of the complete 20.00. A client applying the spend divisor to that conversion-value field displays 0.018 instead of 180.00. These are distinct processing defects under the example's assumptions; correcting one does not repair the other.
Now suppose the matched Ads Manager export shows spend of 20.30. Retrieving page 2 explains the missing 7.50 in the original API view, but it leaves 0.30 unexplained against the UI. Do not attribute that remainder to timezone, late events or invalid traffic without further evidence.
Keep a correction ledger: the demonstrated defect, affected metric and rows, original calculation, corrected calculation, verification and unresolved difference. A corrected client total is evidence about that client path, not proof that every account or metric now reconciles.
Prepare for the announced December reporting changes#
Reddit's v3 reporting notice, rechecked on 5 November 2026, gives 8 December 2026 as the effective date. Its hourly-window and breakdown restrictions require a request review before that date. They do not establish the cause of an older discrepancy or a completed rollout in a particular account.
Preserve the question when separating incompatible reports
Evaluate the actual breakdown arrays, including aliases. The notice permits no more than one of KEYWORD, COMMUNITY/SUBREDDIT, INTEREST and LANGUAGE. A member of that group cannot be paired with DMA/METRO, REGION, GALLERY_ITEM_ID/CAROUSEL_CARD, OS_TYPE or COUNTRY. It also limits a HOUR request to seven days, including a historical interval rather than only the latest week.
Inventory affected saved templates and their downstream charts. Keep the redacted old request, the requested row grain and the reason each dimension is needed. A successful replacement request establishes technical acceptance for that test. It does not establish that a dropped dimension was unnecessary to the business question.
If an audience and geographic view cannot be requested together, preserve them as two labeled reports. A join on date and campaign cannot recover their joint distribution. Suppose a hypothetical country report has two rows and an interest report has three rows for the same campaign-day. A cross-join creates six combinations, but none is evidence of country-by-interest delivery. Do not allocate delivery across those combinations or add both report totals into an account total.
Classify the requested output before implementing a workaround: a valid one-dimensional trend, two separate comparisons, or an unavailable cross-tabulation. Record that decision beside the dashboard. A clearly stated unavailable view is more defensible than a newly populated but invented joint report.
Build a coverage receipt before requesting longer histories
Hypothetical planning example: a team needs a 20-day hourly trend. A plan with windows of 7, 7 and 6 days covers 20 days only if the selected intervals meet without overlap or omission. Validate the endpoint's actual boundary semantics before translating that plan into requests. This is not a tested Reddit request or a promise that every hour returns a row.
Use a coverage receipt rather than relying on the number of successful calls:
| Receipt item | Check it enables |
|---|---|
| Intended reporting interval | Identifies the entire business period before splitting it |
| Reporting timezone and offsets | Keeps calendar boundaries interpretable |
| Window start and end | Exposes gaps or overlaps between planned selections |
| Unchanged fields, filters and grain | Prevents a later window from asking a different question |
| Page-chain completion | Separates a complete window from a successful first page |
| Persistence/run identity | Helps investigate a retry that appends an earlier window again |
| Raw and normalized totals | Locates a change introduced after retrieval |
| Retrieval and update times | Preserves snapshot age without labeling an update timestamp final |
Use authorized redacted fixtures containing known records just before, at and just after a selected boundary. Check which request receives each record under the documented contract. Include a deliberate repeated page and a failed later page so the review can distinguish duplicated persistence from an incomplete extraction. A fixture proves the tested client's behavior for that fixture; it does not validate Reddit's entire reporting service.
Do not deduplicate by date and campaign if the requested grain also contains ad ID or another breakdown. That can remove valid rows. Conversely, retain the window and page identity as retrieval evidence without pretending that two copies of the same logical reporting row represent distinct delivery. For overlapping snapshots, decide explicitly which snapshot the final report uses; do not sum old and refreshed versions.
Accept the changed definition and the changed client separately
Review both the saved request definition and its implementation. Preserve the existing custom-event and app-install mappings described above; splitting dates must not silently broaden an action source or replace an attribution source. For rates, compare underlying populations rather than averaging window-level rates. Keep unique-user or reach aggregation separate from additive event or delivery counts.
For one bounded completed period, retain the request diff, window receipt, parser version, row key, documented units and remaining variance. Re-fetch a matching period later where historical conversion refreshes matter. Approval should state which outputs are comparable and which requested view remains unavailable, rather than claiming every historical API/UI discrepancy has been fixed.
The notice's future schedule and the endpoint's current late-conversion freshness guidance remain separate observations. The documentation also labels v4 Preview; a discrepancy alone is not a reason to move an established v3 integration to a preview version.
Escalate with the first differing record#
A useful support packet contains the redacted request contract, complete retrieval manifest, raw and normalized sample rows, matching UI export, extraction times, field scales and a concise description of the remaining gap. State what you verified and what remains unknown.
If the question instead concerns clicks leading to hidden or short landing-page recordings, use the Reddit click-to-landing investigation. That browser-behavior task cannot settle an API monetary-unit or pagination mismatch.
For campaigns already measured in AdProof, keep a supported campaign-event or aggregate export with matching dates, timezone and filters alongside the independently obtained platform records. The anonymized fashion-retail quality case illustrates delivery evidence, not a Reddit API integration or an agreed refund. Discuss the available measurement scope before assuming any new platform field is independently covered.
Frequently asked questions#
Does splitting incompatible breakdowns recover the original cross-tabulation?
No. Separate audience and geographic reports remain separate aggregations. A join can repeat delivery and a sum can double-count it. Preserve each report's grain and state that the unsupported joint view has not been reconstructed.
Should every monetary field be divided by one million?
No. Use the documented field-specific scale. The cited v3 reference assigns a different divisor to CONVERSION…TOTAL_VALUE fields. Preserve raw values and check whether a connector already normalized them.
Does setting time_zone_id alone guarantee the same daily report?
No. Confirm the breakdowns, interval boundaries and UI setting. Reddit documents that the parameter is effective with date-detail breakdowns; other request shapes need their interval offsets checked.
Does HTTP 200 prove the account report is complete?
No. It establishes that request's success. Follow all returned report pages, preserve retrieval failures and verify that downstream processing neither omits nor repeats rows.
Do the December changes explain an older discrepancy?
The announcement alone does not establish that cause. Keep the future effective date separate from the actual request, response and settings recorded during the affected period.
Does a missing custom-conversion value mean zero conversions?
Keep an explicit zero separate from an absent value, rejected request or parser failure. Verify the exact event name and request scope, then compare the raw response with stored output. A filled receipt diagnostic does not independently establish attributed reporting.
Research and scope#
The original guide was reviewed 30 October 2026 and its custom-event and app-install continuation on 4 November 2026. The migration notice and added hourly-window/breakdown coverage worksheet were rechecked 5 November 2026. The linked older crossposts represent one unresolved author's report. Official sources support interface semantics and the dated announcement; the diagnostic sequence and worked example are original recommendations. No private account audit, platform-wide outage, billing adjustment or indexing outcome is claimed.
Freeze the report contract for one completed day
Compare account, entities, fields, filters, timezone and extraction time before changing normalization. Discuss the API and UI evidence available.
Discuss a measurement questionA short inquiry to scope relevant options; no campaign access is needed.
