---
title: Correcting Week Dimension Data in Dataslayer with Google Ads Connector
description: When utilizing the Week Dimension (starting on Sunday) with the Google Ads connector in Dataslayer, you may encounter a situation where the returned date appears to reference the previous week, rather
---
[Skip to content](https://support.dataslayer.ai/correcting-week-dimension-data-in-dataslayer-with-google-ads-connector#main-content)
- [English](https://support.dataslayer.ai/correcting-week-dimension-data-in-dataslayer-with-google-ads-connector)
- [Español](https://support.dataslayer.ai/es/corrección-de-datos-de-dimensiones-semanales-en-dataslayer-con-google-ads-connector)
English
Show submenu for translations
[](https://www.dataslayer.ai/)
Open main navigation
Close main navigation
- - [English](https://support.dataslayer.ai/correcting-week-dimension-data-in-dataslayer-with-google-ads-connector)
- [Español](https://support.dataslayer.ai/es/corrección-de-datos-de-dimensiones-semanales-en-dataslayer-con-google-ads-connector)
English
Show submenu for translations
Hello. How can we help you?
- There are no suggestions because the search field is empty.
1. [Knowledge base](https://support.dataslayer.ai/?hsLang=en)
2. [Data Sources](https://support.dataslayer.ai/data-sources?hsLang=en)
May 7, 2024
# Correcting Week Dimension Data in Dataslayer with Google Ads Connector
### Overview
When utilizing the Week Dimension (starting on Sunday) with the Google Ads connector in Dataslayer, you may encounter a situation where the returned date appears to reference the previous week, rather than the current one. This document provides a guide to address and correct this discrepancy.
### Understanding the issue
The root of this issue lies in the difference between date formats used by Google. Specifically, Google differentiates between the ISO format (YYYY-MM-DD) and the American format (MM/DD/YY). When the Google API returns dates in the American format, it may lead to inconsistencies with the week dimension data.
This behavior is related to the interaction with Google Ads and is external to Dataslayer.
> ### Solution: Correcting the Date
Should you encounter this discrepancy, the following steps will guide you in correcting the week's dimension data:
To understand the example, first, let's clarify with the attached calendar how Google understands weeks.
Google associates the week from 12/31 to 1/6 as another week in the year 2023 and that is why we get a week 53 when it should be week 1 of 2024.
To correct the date:
1\. Upon loading your query, you might notice that the Year-Week dimension (starting on Sunday) **displays incorrect dates**. This is illustrated in the accompanying screenshot:
2\. To adjust and obtain the correct week data, **apply the following formula within your spreadsheet** and drag it down to cover all weeks:
```
=IF(IF(VALUE(RIGHT(A:A;2))=53;1;VALUE(RIGHT(A:A;2)))=D1;IF(VALUE(RIGHT(A:A;2))=53;1;VALUE(RIGHT(A:A;2)))+1;IF(VALUE(RIGHT(A:A;2))=53;1;VALUE(RIGHT(A:A;2))))
```
- *The range to select (A:A in the formula above) depends on the specific column where your week's dimension data is located. Adjust accordingly to match your data setup.*
By applying this formula, you can ensure that your Year-Week dimension data accurately reflects the intended time period, thereby enhancing the reliability of your data analysis within Dataslayer.
You can also obtain this issue with the **Week (starting on Sunday)** dimension, although we recommend using the Year-Week dimension proposed above.
As always, please contact us via our live chat on our [website](https://dataslayer.ai/es/) or via [email](mailto:info@dataslayer.ai) if you still have doubts or questions. We are happy to help!
- [General](https://support.dataslayer.ai/general?hsLang=en)
- [Billing & Pricing](https://support.dataslayer.ai/billing-pricing?hsLang=en)
- [Data Sources](https://support.dataslayer.ai/data-sources?hsLang=en)
- [Blended Connectors](https://support.dataslayer.ai/blended-connectors?hsLang=en)
- [Google Sheets](https://support.dataslayer.ai/google-sheets?hsLang=en)
- [Microsoft Excel](https://support.dataslayer.ai/microsoft-excel?hsLang=en)
- [Spreadsheets](https://support.dataslayer.ai/spreadsheets?hsLang=en)
- [Looker Studio](https://support.dataslayer.ai/looker-studio?hsLang=en)
- [Big Query](https://support.dataslayer.ai/big-query?hsLang=en)
- [API Query Manager](https://support.dataslayer.ai/api-query-manager?hsLang=en)
- [Power BI](https://support.dataslayer.ai/power-bi?hsLang=en)
- [Amazon S3](https://support.dataslayer.ai/amazon-s3?hsLang=en)
- [Amazon Redshift](https://support.dataslayer.ai/amazon-redshift?hsLang=en)
- [Snowflake](https://support.dataslayer.ai/snowflake?hsLang=en#main-content)
- [Marketplace](https://support.dataslayer.ai/snowflake?hsLang=en#marketplace)
- [Google Cloud Storage](https://support.dataslayer.ai/google-cloud-storage?hsLang=en)
- [Database](https://support.dataslayer.ai/database?hsLang=en)
- [Azure SQL](https://support.dataslayer.ai/azure-sql?hsLang=en)
- [Azure Storage](https://support.dataslayer.ai/azure-storage?hsLang=en)
- [Dataslayer Atlas](https://support.dataslayer.ai/dataslayer-atlas?hsLang=en)
- [Morpheus](https://support.dataslayer.ai/morpheus?hsLang=en)
- [AI Looker Studio Analyzer](https://support.dataslayer.ai/ai-looker-studio-analyzer?hsLang=en)
- [Dataslayer MCP](https://support.dataslayer.ai/dataslayer-mcp?hsLang=en)
- [Dataslayer GPT](https://support.dataslayer.ai/dataslayer-gpt?hsLang=en)
- [Dataslayer AI Chat](https://support.dataslayer.ai/dataslayer-ai-chat?hsLang=en)
[](https://dataslayer.ai/)
Dataslayer.ai: Digital Marketing Reporting Made Easy
Copyright © 2026, DATASLAYER SL