Hi Khushboo,

This is Yuanyuan from the Amplitude Support team - happy to assist!

Is the discrepancy you are referring to for attribution events from AppsFlyer to Amplitude, or for the event stream connection from Amplitude to AppsFlyer? As you mentioned AppsFlyer IDs, I believe the issue is with event stream connection from Amplitude to AppsFlyer. Let me know if I am wrong.

For this connection, AppsFlyer requires that all events have an **AppsFlyer ID** present. If you have selected any events to send to AppsFlyer that may not have an **AppsFlyer ID**, add a filter to send only events where the **AppsFlyer ID** is present.

You can set up two separate AppsFlyer connections for iOS and Android. During the setup, you can add a filter 'platform = iOS' for the ios connection and choose the Amplitude user property that corresponds to your **AppsFlyer ID** **for iOS.** You can then set different formats of AppsFlyer IDs on Amplitude for iOS and Android.

Is this along the line of what you are looking for? Please let me know.

Best,
Yuanyuan


P.S. Checkout upcoming events and user meetups on our events page.

---

Hi Yuanyuan,

After following the steps you suggested, how can we set up different AppsFlyer IDs for iOS & Android on Amplitude?

---

Hi Khushboo,

Thanks for following up!

The AppsFlyer ID can be any custom user property you sent to Amplitude. It is not set by Amplitude but by your dev team that sends the data to Amplitude. Let me know if this answers your questions. Happy to clarify further if there is anything I am missing.

Best,
Yuanyuan


P.S. Checkout upcoming events and user meetups on our events page.

---