AppsFlyer, Adjust and Singular: Write the Attribution Test Before Comparing Vendors

A mobile team buying attribution software can waste a whole demo comparing dashboards that answer different questions. Before scheduling the next one, draw the journey the vendor will have to explain: ad click, store visit, install, first open and first purchase. Mark which events the team controls and which arrive from a partner.

AppsFlyer, Adjust and Singular appeared in all four opening paragraphs for the mobile-attribution question in Nir Levi’s October Perplexity pilot. The English openings also named Tenjin twice. The Hebrew openings named Airbridge once. Counting the names makes those differences visible; reading the sentences reveals that some products were introduced only for a particular team or use case.

Write a test the vendor can fail

For a web-to-app journey, ask what record the analyst receives if the app is already installed, then repeat with a fresh install. Where can the analyst see the timestamps? What happens to the event if the user declines an optional permission? Can the team tell a missing event from a recorded event with an unknown source? Leave the expected answers blank until the demonstration and ask for a documented explanation of each discrepancy.

An Israeli app company can circulate the same event diagram in Hebrew and English, with its own event names left unchanged. Ask the acquisition lead to sign off on the decision it supports and the engineer to sign off on what is observable. The resulting test is much more useful to a procurement meeting than another list of popular platforms.

Study and archived answers: https://nirlevi.com/en/research/israeli-geo-hebrew-english/