@kapa.ai I am trying to pull bing keyword performance daily data but spend number are not matching

Based on the information provided in the knowledge sources, it appears that there have been issues with data mismatches in the Bing Ads connector for Airbyte, particularly related to performance reports. While the exact issue you're experiencing isn't explicitly mentioned for Bing Ads, there are some relevant points and troubleshooting steps you can consider: 1. Data Mismatch: There have been reports of data mismatches between the API results and what's shown in the Bing Ads UI. This has been observed in other advertising platform connectors like Facebook Ads, which might indicate a similar issue could occur with Bing Ads [Link to GitHub issue](https://github.com/airbytehq/airbyte/issues/38154). 2. Field Exclusion: In some cases, excluding certain fields from the API request has resolved data discrepancies. For Bing Ads, you might want to check if removing any non-essential fields from your request improves the accuracy of the spend numbers. 3. Timezone Issues: One user suspected that timezone differences might be causing discrepancies in cost/spend values [Link to GitHub issue](https://github.com/airbytehq/airbyte/issues/2508). 4. Lookback Window: Ensure that your "Lookback window" setting is appropriate for your needs. This setting affects how far back the connector looks for data, which could impact the accuracy of your reports [Bing Ads Setup Guide](https://docs.airbyte.com/integrations/sources/bing-ads#step-2-set-up-the-source-connector-in-airbyte). 5. Version Check: Make sure you're using the latest version of the Bing Ads connector, as updates may have addressed known issues [Bing Ads Migration Guide](https://docs.airbyte.com/integrations/sources/bing-ads-migrations#bing-ads-migration-guide). 6. Custom Reports: If the standard reports aren't providing accurate data, you might want to try setting up a custom report to see if it yields more accurate results [Custom Reports Documentation](https://docs.airbyte.com/integrations/sources/bing-ads#custom-reports). If these steps don't resolve the issue, you may want to: 1. Double-check the date range and any filters applied to ensure they match between your Bing Ads UI and the Airbyte connector settings. 2. Reach out to Airbyte support or create a GitHub issue with specific details about the discrepancies you're seeing. Remember that the Bing Ads API has rate limits, which could potentially affect data retrieval in some cases [Limitations & Troubleshooting](https://docs.airbyte.com/integrations/sources/bing-ads#limitations--troubleshooting). If the problem persists, it would be helpful to provide more specific details about the discrepancies you're seeing and the exact configuration of your Bing Ads connector in Airbyte to get more targeted assistance.