> ## Documentation Index > Fetch the complete documentation index at: https://docs.adriel.com/llms.txt > Use this file to discover all available pages before exploring further. # FAQs > Common questions, expected behaviors, and troubleshooting for the Google DV360 Report data source. ## Why doesn't my DV360 report show up when I connect? For a saved DV360 report to appear in the connection setup list, it must meet two conditions. Its title must begin with `Adriel` (the match is not case-sensitive, so `Adriel_campaign` and `adriel_campaign` both qualify), and it must be saved in **CSV** format. Reports saved in any other format, or whose title starts with anything else, are filtered out of the list. To make an existing report selectable, rename or duplicate it in the DV360 UI so the title starts with `Adriel`, confirm the output format is CSV, and reopen the connection setup. A report that has been saved but never generated in DV360 also returns no rows until it has run at least once. ## Why are the metrics in my Adriel widget different from another DV360 report I ran? Each Adriel data source is bound to exactly one saved DV360 report. The columns available in Adriel are whatever that specific report was configured to output. A different DV360 report, built with a different set of metrics and breakdowns, produces a different set of columns. Because the shape of the data comes from the saved report rather than from a fixed Adriel schema, two reports rarely expose identical fields unless they were configured identically in DV360. To compare like for like, confirm both reports use the same metrics, breakdowns, and date settings on the DV360 side. This report-file variant differs from the standard entity-based connector, which uses a fixed metric and breakdown catalog — see the [Google Display & Video 360 data reference](/data-sources/g-n/google-display-video-360-dv360/data-reference). ## Can I change the columns after connecting? The available metrics and breakdowns cannot be changed from inside Adriel, because they are defined by the saved DV360 report. To add or remove a column, the change is made in DV360 first: edit the existing saved report (or create a new one) to include the wanted metrics and breakdowns, keep the title starting with `Adriel`, and keep the format as CSV. Once the report is updated in DV360, the new columns flow into Adriel on the next sync. Removing a column in DV360 removes it from Adriel the same way. ## Why is my report empty for the most recent day? Data for a given day only reaches Adriel after the DV360 report that covers it has finished generating on Google's side. If the saved report has not completed for the latest day before the connector's refresh window runs, the most recent day can appear empty until the following refresh brings it in. This is expected timing behavior rather than missing data. For the refresh schedule that governs when new rows arrive, see the [Google DV360 Report data reference](/data-sources/g-n/google-dv360-report/data-reference). Note also that this data source does not carry data for elements deleted in DV360 — once an element is removed on the platform, its historical rows are no longer provided. ## Do I need a separate connection for each DV360 report? Yes. One Adriel data source corresponds to one saved DV360 report. To bring in a second report — for example, a campaign-level report alongside a creative-level report — a separate connection is added for each, and each is selected from the setup list independently. Reports cannot be merged into a single connection. Widgets can still combine the resulting data sources on one dashboard using blended data. ## How do I combine DV360 Report data with other data sources? Because the columns are user-defined, this data source behaves as a generic (free-format) source. Its data displays in a generic table, and it does not automatically share breakdowns with other connectors. To report on it next to another data source, the two are combined with a blended data setup that maps a shared breakdown (for example, date or campaign) across both. Matching the DV360 report's breakdown names and date granularity to the other source makes the blend align cleanly. ## Related Metrics, breakdowns, refresh cadence, and limits for the report-file variant. Step-by-step setup for the saved-report connection. The standard entity-based DV360 connector, with a fixed field catalog. How Adriel imports, caches, and refreshes data source data.