---
title: "How to use the \"Page time period\" option for Facebook Insights connector"
description: Learn how to use the "Page time period" option in Dataslayer to get accurate Facebook Insights metrics and avoid duplications in unique users.
---
[Skip to content](https://support.dataslayer.ai/how-to-use-the-page-time-period-option-in-dataslayer-for-facebook-insights#main-content)
- [English](https://support.dataslayer.ai/how-to-use-the-page-time-period-option-in-dataslayer-for-facebook-insights)
- [Español](https://support.dataslayer.ai/es/cómo-usar-la-opción-page-time-period-para-el-conector-de-facebook-insights)
English
Show submenu for translations
[](https://www.dataslayer.ai/)
Open main navigation
Close main navigation
- - [English](https://support.dataslayer.ai/how-to-use-the-page-time-period-option-in-dataslayer-for-facebook-insights)
- [Español](https://support.dataslayer.ai/es/cómo-usar-la-opción-page-time-period-para-el-conector-de-facebook-insights)
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)
January 20, 2026
# How to use the "Page time period" option for Facebook Insights connector
## Learn how to use the "Page time period" option in Dataslayer to get accurate Facebook Insights metrics and avoid duplications in unique users.
When analyzing your Facebook Page performance, one of the biggest challenges is avoiding **duplicated unique users** and ensuring your totals are reliable. If you’ve ever seen inflated numbers when adding up daily data, you’ve probably run into this issue.
To solve it, Dataslayer’s **Page time period** option lets you control how metrics are grouped (daily, weekly, last 28 days, or totals), making your Facebook Insights reports far more accurate.
### Why Page Time period option matter?
By default, Facebook Insights provides Page metrics on a **daily basis**. But not all metrics make sense to sum up per day. For example:
- **Total Reach** or **Followers** can be duplicated if you simply add daily values.
- With the **Page time period** option, you can request the totals directly in a clean way, avoiding inconsistencies.
#### Which metrics are affected?
This option applies **only to Page-level metrics**, such as:
- *Total Reach*
- *Page Followers*
- *Total Likes*
- *Page Reactions*
**Post-level metrics**, such as *Post impressions* or *Post name*, are **always reported as lifetime values**. This means they do not support time-period grouping, and the Page time period option will not have any effect on them.
**Video metrics** also work primarily with lifetime values. A few of them allow daily breakdowns, but in most cases, they are **fixed to lifetime** and therefore are not influenced by the Page time period setting.
#### Available options
When setting the **Page time period**, you can choose:
- **By day (default)** – Metrics grouped daily.
- **By week** – Metrics grouped weekly.
- **Last 28 days** – Metrics grouped in a rolling 28-day period.
- **Total over range** – Aggregate totals for the full date range you select.
Meta’s API only allows totals for up to 90 days. Going beyond that may return *inconsistent* *results*.
#### Using Page time period with dimensions
The Page time period controls **how metrics are aggregated**, while your query’s dimension controls **how data is displayed**.
- If you choose **time dimension = day** but set **Page time period = week**, Dataslayer will ignore the mismatch and keep “day”.
- If you want weekly grouping, use **dimension = week** together with the Page time period = week.
Aligning the dimension and the Page time period will return consistent results.
#### What if different metric types are mixed in the query?
The **Page time period** option only applies to **Page-level metrics**. If your query includes metrics or dimensions from different endpoints, such as combining **Page metrics** (e.g., *Total Likes*, *Page Followers*) with **Post metrics** (e.g., *Organic Post Reach*, *Post name*), the request will not work because each type of metric is retrieved from a different Facebook endpoint.
In practice:
- Queries that include only **Page metrics** will respect the Page time period you select.
- Queries that include only **Post metrics** will always return lifetime values.
- If you try to combine them, Dataslayer will return an error since Facebook does not allow mixing endpoints in the same request.
Running separate queries for Page metrics and Post metrics will avoid errors and ensure accurate results.
### How to set the Page Time Period option in Dataslayer
- **Google Sheets/Excel extension**
Once you've selected the accounts and the data table information, scroll down in the fourth section called **OPTIONS**. You’ll find the **Page time period** option at the end of the list.
-Jul-29-2025-12-42-14-6471-PM.png?width=688&height=252&name=Browser%20template%20(5)-Jul-29-2025-12-42-14-6471-PM.png)
- **Looker Studio**
Once you have chosen the Hub Account and the relevant Accounts in the connectors configuration, simply scroll down to the bottom of the list to locate the option:.png?width=688&height=344&name=Troubleshooting%20LS%20(11).png)
- **Web Destinations**
Once you have selected the accounts, metrics, and dimensions, simply scroll down to the Options section, where you will find the "Page time period" option listed at the bottom:**.png?width=688&height=378&name=NEW%20UI%202025%20-%20About%20the%20Hub%20%20refresh%20credentials%20(2).png)**
### Common Issues and their solutions
In using the "Page time period" option, you may encounter a few common issues. Here are some explanations and solutions to help you navigate these challenges effectively.
| **Issue** | **Fix** |
| --- | --- |
| *Page followers' metric value is not correct* | Select "Total over range" under **Page Time Period** option |
| *Inconsistencies in the "Reach" total* | Limit queries to periods of **up to 90 days** |
The **Page time period** option in Dataslayer is a simple but powerful way to get **more accurate Facebook Insights data**, avoid duplicated unique users, and create cleaner reports.
By aligning your dimensions and using the right time period, you’ll save time and ensure your reports truly reflect what’s happening on your Facebook Page.
As always, please contact us via our live chat on [our website](https://dataslayer.ai/?__hstc=205882892.609c93ea8042b8239c499e224c18b52a.1712818507477.1713181287827.1713258274101.5&__hssc=205882892.27.1713258274101&__hsfp=3856379180) 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