Identified - Issue: We have identified on October 3rd, 2024 a issue with Meta Facebook Ads where Spend data discrepancies are impacting customers connected to the Facebook Ads Instant Connector.
Impact: Only Spend metrics are affected; all other metrics are operational as expected. Cause:
Facebook is aware of this issue and is actively working to resolve it. Resolutions and action currently is waiting for the Facebook Ads team.
Resolved -
Summary: We have successfully resolved the issue identified with Simpli.fi reports generated between November 18th, 4:30 PM (CST) and November 22nd, 12:00 PM (CST).
Resolution Details: TapClicks has ran a refetch of all impacted data from Simpli.fi. Reports for the affected timeframe now reflect Simpli.fi corrected data for the following data sets:
New Ads Geo-Fences Audience/Segments
What You Should Do: If you previously pulled reports during the affected timeframe, we recommend re-generating those reports to ensure accuracy. If you encounter any discrepancies, please contact our support team for further assistance.
We appreciate your patience and understanding while we worked to resolve this issue.
Nov 26, 23:39 UTC
Identified -
Simpli.fi has notified us of a potential discrepancy in the API dataset that affected select reports between November 18th, 4:30 PM (CST) and November 22nd, 12:00 PM (CST). During this period, some reports may have yielded incomplete or missing data for the following data sets:
New Ads Geo-Fences Audience/Segments
This issue is specific to campaigns where new Ads, Geo-Fences, or Audiences/Segments were added during the affected timeframe AND reports were generated for these campaigns.
Simpli.fi has taken action to correcting this dataset. TapClicks will proactively initiate a refetch of all impacted data from Simpli.fi to ensure accurate and complete reporting.
What You Should Do: If you have concerns about specific campaigns or reports generated during the impact window, please feel free to reach out to our support team.
We will update this notice once the refetch is completed.
Thank you for your understanding and patience as we address this issue.
Nov 25, 21:22 UTC
