.png)
davtech
Active Member
Hi everyone,
I'm trying to understand the relationship between two metrics that I believe should be equivalent, but I'm seeing a significant discrepancy in practice.
Our setup:
The discrepancy:
My understanding is that these two should be the same thing: ATT Status = Authorized = ATE Flag = True
In other words, when a user accepts the ATT prompt and AppsFlyer records att_status = authorized, AppsFlyer should be passing ATE = true in the ping it sends to Meta. Meta should then reflect this in its ATE True Status Rate.
My questions:
1. Is this understanding correct? Are ATT Authorized and ATE True genuinely equivalent?
2. If yes, what could cause a gap between the two? Could the Facebook SDK interfere with how the ATE flag is transmitted?
3. Could running campaigns under AEM (instead of SKAN) affect how the ATE flag is reported in Meta Events Manager?
4. Has anyone seen a 2% ATE rate with a significantly higher ATT Authorized rate, and what was the root cause?
Any insight from people who have dealt with this would be really appreciated. We're trying to understand if this is a configuration issue on our end, an AppsFlyer transmission issue, or a Meta reporting issue.
Thanks in advance!
I'm trying to understand the relationship between two metrics that I believe should be equivalent, but I'm seeing a significant discrepancy in practice.
Our setup:
- OS app running Meta App Promotion (A2A) campaigns via Advantage+
- AppsFlyer as MMP
- Both Facebook SDK and AppsFlyer SDK integrated in the app
- Campaigns running under AEM (Aggregated Event Measurement)
The discrepancy:
- ATT Status = Authorized in AppsFlyer ~40%
- iOS 14.5 ATE True Status Rate in Meta Events Manager → 2%
My understanding is that these two should be the same thing: ATT Status = Authorized = ATE Flag = True
In other words, when a user accepts the ATT prompt and AppsFlyer records att_status = authorized, AppsFlyer should be passing ATE = true in the ping it sends to Meta. Meta should then reflect this in its ATE True Status Rate.
My questions:
1. Is this understanding correct? Are ATT Authorized and ATE True genuinely equivalent?
2. If yes, what could cause a gap between the two? Could the Facebook SDK interfere with how the ATE flag is transmitted?
3. Could running campaigns under AEM (instead of SKAN) affect how the ATE flag is reported in Meta Events Manager?
4. Has anyone seen a 2% ATE rate with a significantly higher ATT Authorized rate, and what was the root cause?
Any insight from people who have dealt with this would be really appreciated. We're trying to understand if this is a configuration issue on our end, an AppsFlyer transmission issue, or a Meta reporting issue.
Thanks in advance!
