> ## 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 Meta Ads data source.

## Conversions not showing on the dashboard

A common source of confusion: a conversion event shows up in the Meta Pixel dashboard, but not in the Adriel dashboard. The reason is that conversions only appear when **Meta Ad Manager itself receives them** — a Pixel-only event isn't enough.

### Quick checks

<Steps>
  <Step title="Confirm the event appears in Meta Ad Manager">
    In Meta Ads Manager, open the ad account, click **Columns** → **Customize columns**, and search for the conversion event. If it's not in the column list, Ad Manager isn't receiving it — fixing this on the Meta side comes first.
  </Step>

  <Step title="Check that at least 1 conversion has been recorded">
    Meta's API only exposes metrics that have recorded at least one event in the recent past. A brand-new conversion event with zero historical fires won't appear until it has data.
  </Step>

  <Step title="Wait for the next sync">
    Adding a custom conversion in Meta is reflected in Adriel on the next refresh, which can take several hours. See [Refresh strategies](/data-sources/how-data-works/refresh-strategies).
  </Step>
</Steps>

### Causes & fixes

<AccordionGroup>
  <Accordion title="The event is only on the Pixel, not on the Ad Account">
    The Pixel dashboard and the Ad Account dashboard track events separately. Adriel can only show events that the **Ad Account** has been configured to receive.

    Fix: in Meta Ads Manager, go to the ad account → **Columns** → **Customize columns**, find the event, and save it as part of the column preset. Once the event appears in the Ad Account's reporting columns, the next sync brings it into the dashboard.
  </Accordion>

  <Accordion title="The event is custom but hasn't been set up as a custom conversion">
    Standard Meta Pixel events (for example, `purchase`, `add_to_cart`, `lead`, `complete_registration`) come through automatically.

    Custom events — anything outside the standard set — need to be defined as a **custom conversion** in Meta Events Manager before they're queryable through the Ads API. The current Meta limit is 100 custom conversions per ad account.

    Reference: Meta's "Use custom conversions to filter events in Meta Events Manager".
  </Accordion>

  <Accordion title="The metric name doesn't match what's expected">
    Adriel exposes Meta conversion events at multiple attribution windows. For each event, look for metric variants like:

    | Variant        | Meaning                                          |
    | -------------- | ------------------------------------------------ |
    | (no suffix)    | Default attribution per the ad account's setting |
    | `(Click, 1d)`  | 1-day click attribution                          |
    | `(View, 1d)`   | 1-day view-through attribution                   |
    | `(Click, 7d)`  | 7-day click attribution                          |
    | `(View, 7d)`   | 7-day view-through attribution                   |
    | `(Click, 28d)` | 28-day click attribution                         |
    | `(View, 28d)`  | 28-day view-through attribution                  |

    Both a **count** version (e.g. "Purchases (Click, 7d)") and a **value** version ("Conversion value: Purchase (Click, 7d)") are available for each.
  </Accordion>

  <Accordion title="The widget is at the ad-account level">
    A few Meta metrics — for example, `omni_purchase` conversion value, `catalog_omni_purchase` conversion value, form leads, and Instagram profile visits — aren't available at the ad-account level. If a widget requests one of these at the ad-account level, the level is automatically elevated to **campaign** so the data can still load.

    Fix: drill into the campaign breakdown in the widget to see the data — the ad-account row may appear empty.
  </Accordion>

  <Accordion title="Custom conversion API limitations">
    For custom conversions specifically, Meta's Ads Insights API has limitations:

    * Product ID breakdowns are not supported.
    * Unique action counts are not supported.

    Widgets relying on either will return no data for custom conversions. Use standard event metrics instead, or report at a higher level.
  </Accordion>

  <Accordion title="Pixel was added but no conversion has happened yet">
    Meta's API doesn't return a conversion metric until at least one event has been recorded. A new Pixel needs at least one purchase, lead, or other tracked event before the metric appears in the column list.
  </Accordion>
</AccordionGroup>

If the issue persists after all of the above, email `support@adriel.com` with the Meta Ads ad account ID, the conversion event name, screenshots of the Meta Ads Manager column setup, and the affected dashboard URL.

## Common issues

<AccordionGroup>
  <Accordion title="Why aren't some Meta ad accounts or Pages available to connect?">
    The Facebook connection itself can be valid while individual ad accounts or Pages remain invisible in Adriel because the connecting user has no permissions on them in Meta Business Portfolio. Facebook Organic in particular requires the connecting user to have proper access on the specific Page.

    Add users and permissions to the missing assets in Business Portfolio, then those accounts become connectable in Adriel.
  </Accordion>

  <Accordion title="Why does a Meta widget with age, gender, country, platform, device, or placement return `INVALID_DIMENSIONS_COMBINATION`?">
    Meta's detail breakdowns (age, gender, country, platform, device, placement) are only supported up to the campaign level in the Meta API. Applying an ad-set filter alongside the detail breakdown triggers `INVALID_DIMENSIONS_COMBINATION`.

    Remove the ad-set filter to resolve the error. For placement specifically, switching a filter from **campaign name** to **campaign ID** uses a different data-fetch path that supports the combination.
  </Accordion>

  <Accordion title="Why doesn't Adriel's Meta Lead number match the Meta UI's Leads (Form) column?">
    Adriel's default Meta **Lead** metric maps to Meta Insights `action_type=lead`, which is a broader total that can include offsite Pixel / CAPI leads plus on-Facebook leads. Meta UI's **Leads (Form)** column corresponds to `leadgen_grouped` — Lead Ads instant forms only.

    To match the Meta UI, switch the metric (or the referenced metric in a custom-metric formula) to **Lead (Grouped)**.
  </Accordion>

  <Accordion title="Why did historical Meta data for deleted campaigns or ads disappear?">
    Meta report data is retrieved in real time, and Meta's API stops returning data for campaigns, ad sets, and ads once they transition to deleted or archived status — the historical rows disappear even though they existed during the active period.

    Adriel can enable the `useCache` flag on a data source so previously cached rows for deleted objects remain visible, at the cost of not picking up new data for them. Contact support to enable it.
  </Accordion>

  <Accordion title="Why does a Meta carousel show a different thumbnail than expected?">
    Adriel displays Meta creatives in the order the Meta Ads API returns them. For carousel ads (multiple creatives in one ad), Meta doesn't consistently indicate which asset is the primary preview, so the shown thumbnail may not match what a customer considers primary. All carousel assets are visible in the detail panel. This is a known Meta-side limitation.
  </Accordion>
</AccordionGroup>