> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/data-integrations/setup-guides/digital-integrations/google-ads/important-notes.md). # Important Notes ## No ad or ad group data for Performance Max and Smart Shopping campaigns Our Google Ads extractor pulls ad-level data, but there are two exceptions: Performance Max and Smart Shopping campaigns. These types of campaigns do not contain any ad or ad group objects, so there will be no data for them in the `adwords.ads` or the `adwords.adgroups` tables. However, all details and performance metrics for these types of campaigns *are* available in the `adwords.campaigns` table. This means that if you aggregate data from the `adwords.ads` or the `adwords.adgroups` tables, you will not see spend or any other performance metrics from Performance Max or Smart Shopping campaigns in your aggregations. In our Google Ads transformation code, we blend performance data from the `adwords.ads` and the `adwords.campaigns` tables so that you can get ad-level performance data when possible, and campaign-level performance when it's not. [Learn more about Google Performance Max campaigns](https://support.google.com/google-ads/answer/10724817?hl=en) ## Cost in raw data is in microdollars Unlike in most marketing data sources, the `cost` values in the `adwords` schema tables are represented in microdollars — not dollars. This means you if you are doing custom development using the raw data, you will need to divide `cost` by 1,000,000 to get the dollar value. `conversion_value` and other currency amounts in the `adwords` tables, however, are *not* in microdollars and do not need to be divided by 1,000,000. Google Ads data transformed into the `ums` tables using our standard transformation code has already been converted from microdollars, and you will not need to divide by 1,000,000. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.daasity.com/core-concepts/data-integrations/setup-guides/digital-integrations/google-ads/important-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.