Best Practices

Recommended setup

Use page IDs instead of aliases

Numeric page IDs (e.g., 123456789) are more reliable than public aliases. If you have multiple pages, store their IDs in a spreadsheet for easy reference and to avoid typos.

Verify "Followers and Public Content" settings

Before connecting a page, go to page settings and confirm that "Followers and Public Content" is set to public. This is required for any data to be exported — even if the page is otherwise public.

Start with one page, then scale

Test your first data flow with a single page ID to confirm the setup works. Once you're confident, add multiple page IDs (one per line) to consolidate all your pages into one data flow.

Data refresh and scheduling

Schedule daily or weekly, not hourly

Facebook's API updates data on a delay (usually 1–3 hours). Hourly refreshes waste quota and return the same data. A daily or weekly schedule is sufficient for most use cases.

Refresh posts with a rolling window

For "Public posts statistics", use a date range that covers the last 7–30 days instead of fetching all-time data. This keeps refresh times fast and avoids duplicate rows from posts you've already imported.

Performance optimization

Combine multiple pages with Append transformation

If you're importing from many pages, enter all page IDs in one data flow, then use an Append transformation to stack them into a single table. This is faster than running separate data flows for each page.

Use Join to correlate with other data

Combine post statistics with campaign or revenue data in Google Sheets or BigQuery using a Join transformation. Match by date to understand the relationship between organic Facebook engagement and business outcomes.

Common pitfalls

Do

• Use numeric page IDs when possible

• Set a reasonable date range for post data (7–30 days)

• Test with one page before adding multiple

• Schedule refreshes daily or weekly, not hourly

• Confirm page settings are fully public before connecting

Don't

• Use full Facebook URLs or display names instead of page IDs

• Try to import data from personal profiles (only pages work)

• Run multiple data flows for the same page simultaneously

• Expect real-time data (allow 1–3 hours for Facebook to update)

• Leave date ranges too broad for post data (very old posts slow down imports)

Do not share your full page URL or access token in public. While Coupler.io uses OAuth (so your password is never stored), keep your Coupler.io data flow URLs private to avoid accidental exposure of your page data.