FB App Ads S2S Event Issue + Developer Account ID Conflict (Need Advice)

Linsen

Newbie
Joined
Mar 29, 2025
Messages
1
Reaction score
0
Hi guys,

We are running Facebook app campaigns with the following setup:

- App tracking: AppsFlyer
- Event tracking: S2S postback
- Optimization event: Purchase
- Traffic type: iOS + Android

Currently facing several issues:


1 . No Events Showing in Ads Manager

The Facebook Ads Manager front-end does NOT show any purchase events.
However:
- Events are visible in AppsFlyer
- Events are visible in Data Sources
- Total event count exists

It seems events are received but not attributed or not available for optimization.

-----------------------------------------------------

2 .Events Stopped Reporting After Pause

Previously, campaigns were running normally and purchase events were reporting correctly.

After pausing campaigns for some time:
- Unable to optimize for Purchase
- Events no longer show in Ads Manager
- Even after relaunching campaigns, still no reporting

Has anyone experienced event learning reset or event trust issue?

-----------------------------------------------------

3 . App ID Conflict Issue (Developer Account Problem)

We are using externally purchased Facebook developer accounts.

Sometimes those accounts get locked due to face verification,
and we lose access to the original App ID.

When creating a new App ID and reconnecting:

- Facebook shows ID conflict
- Events cannot be properly attributed
- Old App ID still linked somewhere

What is the correct way to migrate or replace an App ID without breaking event attribution?

-----------------------------------------------------

4 .Questions:

- Is this related to App ID trust score?
- Does S2S have lower priority compared to SDK?
- Is there a way to safely replace App ID?
- Could Aggregated Event Measurement be blocking reporting?
- Any blackhat workaround for low trust App ID?

Any insights would be greatly appreciated.
Thanks.
 
S2S always has lower trust than SDK on iOS, that's likely your core attribution problem. For the App ID conflict, there's no clean fix, you basically need a fresh developer account with a new app and rebuild the integration from scratch. Bought dev accounts are always a liability for exactly this reason.
 
Back
Top