PROFOUND data discrepancy Between v1 and v2 API Responses

Which connector?: PROFOUND

Additional details: During an investigation into missing data for October 4–5, findings indicate that rows are not being dropped during the Snowflake sync process. Instead, the discrepancy stems from a fundamental structural difference in how the v1 and v2 APIs handle visibility data.

The v1 API appears to filter out rows where a brand is not visible, whereas the v2 API includes them.

Data Breakdown (Oct 4–5)

v1 API Response: Returns 152 rows (all rows have average_position = 1 and visibility_score = 1).
v2 API Response: Returns 1,390 rows (the additional rows have average_position = null and visibility_score = 0).

Root Cause Analysis

The v1 API endpoint excludes rows where the brand lacks visibility (visibility_score = 0 and average_position = null). Because the current sync relies on the v1 API, these rows are never delivered to Snowflake, creating the appearance of missing data.

Proposed Solution / Next Steps

To resolve this discrepancy long-term, the endpoint needs to be migrated to the v2 API.

Community

PROFOUND data discrepancy Between v1 and v2 API Responses

Comments