FAQs

​

Why is the most recent day incomplete?

Moloco report data is served from scheduled snapshots rather than live calls to Moloco. Dashboard values are composed from the last snapshot, so the most recent few hours of activity are not yet reflected and the current day can look low until later snapshots catch up. Values settle as subsequent snapshots land. For the snapshot schedule, see the Moloco data reference.

​

Why might reach look too high over a long date range?

Metrics based on uniqueness, such as reach, can be overvalued across date ranges longer than one day. Because report data is composed from daily snapshots, a person reached on more than one day is counted on each of those days, and summing across the range inflates the total. To read reach accurately, narrow the widget to a single day, or treat multi-day reach as an upper bound rather than an exact unique count.

​

Why can’t I break down Moloco data by country, device, or placement?

Moloco reports support only the ad account, campaign, ad set, and ad hierarchy, plus date groupings (daily, weekly, monthly). Audience, device, geographic, and placement breakdowns are not part of what Moloco returns to Adriel, so they cannot be selected on a widget. For the full list of available breakdowns, see the Moloco data reference.

​

Why do installs and conversions have a different metric prefix than other connectors?

Installs and conversions from Moloco are grouped under a Moloco-specific conversion label rather than the generic conversion metrics shared across connectors. This keeps Moloco’s attributed installs and post-install conversions distinct from other sources when several connectors report on the same dashboard. When searching the metric picker, look for the installs and conversions entries under Moloco’s naming rather than the standard conversion metric names.

​

Why do wide ad-level date ranges take longer to load?

Ad-level (per-creative) reports are retrieved in smaller date chunks than the account, campaign, and ad-set levels, because the Moloco API enforces a tighter range limit for creative-level detail. As a result, a wide date range at the ad level takes more requests to assemble and can be slower to load than the same range at a higher level. Reporting at the campaign or ad-set level, or shortening the date range, returns results faster.

​

Related