#Missing media meta install
When an install without an advertiser ID was attributed to Meta ads using the Google Play install referrer, AppsFlyer doesn't report it back to Meta ads. You can change the time zone set for the app in the app settings page to match the time zone defined in Meta ads Manager. Make sure to change it in Meta ads Manager to match the app time zone defined in the app settings in AppsFlyer.ĪppsFlyer's default app time zone is UTC+0. Meta ads default reporting time zone is PST. Meta ads attributes its users that click and install on different devices, for example, iOS/Android/desktop.ĪppsFlyer attributes single devices, which perform both the engagement and the install Meta ads self-attributes installs regardless of other media sources.ĪppsFlyer uses last-click attribution (more information about AppsFlyer attribution available here) Make sure to set to 7 days with Meta ads.ġ day (Note that there are some specific cases where the default is different).ġ day by default, but can be configured to be 1-48 hours (keep this default value) Differences in attribution models Causeħ days (Note that there are some specific cases where the default is different).ġ-30 days. If the number of events varies significantly, there may be a discrepancy. Detect a discrepancy between AppsFlyer and Meta adsĬompare events listed in Meta ads Event Manager to those in AppsFlyer reports. While we work closely with Meta ads to minimize these discrepancies, advertisers should be aware of the following causes for them. This may cause discrepancies to occur between Meta ads and AppsFlyer dashboards. Meta ads discrepancies with AppsFlyerĪs any two major players in the mobile user acquisition eco-system, AppsFlyer and Meta ads differ in their attribution models. At a glance: Learn about the differences in attribution models between Meta ads and AppsFlyer.
0 kommentar(er)
