# Google Ads returns large values for Micro Columns

**URL:** <https://community.cdata.com/t/google-ads-returns-large-values-for-micro-columns/1019>\
**Category:** Data Sources\
**Tags:** micro-columns, article, api, google-ads\
**Created:** [February 12, 2025, 10:53pm UTC](https://community.cdata.com/t/google-ads-returns-large-values-for-micro-columns/1019 "2025-02-12T22:53:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bergi\_M](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/bergi_m/32/1926_2.png) [@Bergi\_M](https://community.cdata.com/u/Bergi_M)\
**Post date:** [February 12, 2025, 10:53pm UTC](https://community.cdata.com/t/google-ads-returns-large-values-for-micro-columns/1019/1 "2025-02-12T22:53:23Z")

</div>

When working with the Google Ads API, we often encounter discrepancies between the numeric values returned by the API and the values displayed on the Google Ads UI. This difference arises because the API returns certain metrics and fields scaled by a factor of 1,000,000. To match the values visible in the Google Ads UI, these API responses need to be divided by 1,000,000.

Link to the google forum: [Cost metric in Google ads api](https://groups.google.com/g/adwords-api/c/-LwPXdn1oNk)

**Explanation of the Scaling**

The scaling mechanism is a deliberate design choice made by Google Ads API. It is used to represent monetary values and other metrics with greater precision, avoiding issues with floating-point arithmetic. However, this also requires developers to apply appropriate scaling adjustments when interpreting API data.

For example:

- If the API returns a value **of 1000000 for** a metric like  **Cost** , the actual value displayed on the Google Ads UI will be  **1.00**.

- Similarly, a value of  **250000**  returned by the API for  **Conversions**  will correspond to  **0.25**  when viewed on the UI.

The scaling by 1,000,000 in Google Ads API ensures high precision for monetary and other critical metrics. By dividing the returned values by 1,000,000, you can accurately map the API responses to the corresponding values in the Google Ads UI. Incorporate this scaling adjustment into your application logic to ensure consistency and accuracy when reporting or analyzing Google Ads data.

To give you a clearer understanding of the situation, let me use the **Campaign** view as an example.

When we query through the driver to retrieve data for a campaign, the API returns values that are scaled **1 million times larger** than their actual values.

 ![3f9690a9-4338-4fbd-a37b-93e9b72c09e0.png](https://us1.discourse-cdn.com/cdata/original/2X/6/6d7bb9028d2bca4f562de84622ef46c211360e96.png)

However, when viewing the same data in the **Google Ads UI,** the values are displayed correctly and remain fixed at their real values.

 ![4e11a147-15c7-4807-ac72-7f46720b028a.png](https://us1.discourse-cdn.com/cdata/original/2X/6/6a782144ecc64377d1f17e170b9baf1829cda856.png)

Additionally, to accurately observe the difference, I am providing a test that displays the calculated value in the result set.

The query used:

SELECT CLICKS, AllConversions, CampaignName, CostPerAllConversions, (CostPerAllConversions / 1000000) AS Real\_Cost\_Per\_Convestion, CostMicros, (CostMicros /1000000) AS Real\_Cost FROM “CData”.“GoogleAds”.“Campaign”

Result set:

 ![a5414760-c8c1-44bf-948f-7569a92cc290.png](https://us1.discourse-cdn.com/cdata/original/1X/d0dab8f9ee335eb67e655d1a9b64037ec0b0faa1.png)

Meanwhile, the values displayed in the UI:

 ![00d3c8fe-77f3-4dfb-9c0e-6f3325513b6c.png](https://us1.discourse-cdn.com/cdata/original/1X/db45ceb99ad32d7530d9a712a2fd397e07aa4900.png)

Please reach out to [support@cdata.com](mailto:support@cdata.com) if this does not resolve the problem for you.