Sorry, we don't support your browser.  Install a modern browser

Feature Request – Support for Using Calculated Fields as Filters for Deduplicated Reach (Looker Studio Facebook Connector)#1559

I

Description:
We would like to request support for using calculated fields as filters when retrieving deduplicated reach within the Looker Studio Facebook Connector.

Current Status:
Based on the latest update, deduplicated reach is supported when applying multi‑level filtering using default Meta fields (e.g. Campaign Name, Ad Set Name, Ad Name). This allows for deduplication across multiple dimensions when those fields are used directly.

Feature Request:
We would like to explore the feasibility of extending this support to calculated fields created within Looker Studio. These calculated fields are derived from Meta’s default dimensions and help users group campaigns and ads into custom hierarchies for reporting purposes.

Examples of calculated fields we use:

  1. Parent Campaign: Derived from the default Campaign field
    Example formula: REGEXP_EXTRACT(Campaign, ‘^(?:[^\]*\){6}([^\_]*)’)

  2. Audience: Derived from the default Ad Set field (e.g. grouping into “2PAR”, “Banking”, etc.)

  3. Creative: Derived from the default Ad Name field (e.g. grouping into “Creative A”, etc.)

Request Summary:
We would like to explore the feasibility to support deduplicated reach calculations when filters are applied using calculated fields, not only default Meta fields.

13 hours ago