Terminology & FAQ

Naming conventions and attribution models are subject to a partner's preference and marketing strategy and can thus vary from partner to partner.

We have decided to share the following clarifications to ensure alignment between the different parties concerning the exchanged information and expected performance. Below you should find insight into AppsFlyer vs. Remerge specific terminology, followed by answers to the most frequently asked questions.  

Terminology

AppsFlyer 

Click - AppsFlyer counts clicks each time a tracking link hits AppsFlyer's server or an app-open via a universal link in one of the following ways:

• Server Hit - A click tracking link hits AppsFlyer's server before redirecting the user to the app. Accordingly, the click is registered immediately and thus counted pre-app-open. Three potential server-hit scenarios: 
  
  
  • A standard tracking link, located behind your ad and clicked upon ad click.
  • A mobile device user of a device that does not contain the app in question clicks on a universal link. This scenario can occur when the user either deletes the app or switches to a new device.
  • A wrapped universal link (placed between multiple redirecting click tracking links).
    
    
• App-Open via a Universal Link - To count a click via this method, ensure that you have either implemented the continuteUserActivity or the openURL method to inform AppsFlyer's SDK of an app-open via AppsFlyer's universal link. In this case, AppsFlyer counts the click post-app-open.

Re-Engagement - App re-open.

Reattribution - App re-install.

Retargeting Conversions - Sum of re-engagements & reattributions.

Dashboard - Attribution, windows, and reporting:

• Attribution - You are most likely to run with multiple ad networks or agencies. Additionally, AppsFlyer utilizes the last-click attribution model. Consequently, AppsFlyer attributes re-engagement and more advanced in-app events to the partner whose marketing efforts have triggered your user's last click. 
  
  
• Windows - AppsFlyer differentiates between two types of attribution windows:
  
  
  • Click Lookback - A post-click window that represents the allotted conversion timeframe. AppsFlyer counts a conversion if the user installs (User Acquisition) or re-installs/opens (Retargeting) the app within this timeframe.
  • Re-Engagement - A window that starts immediately post the conversion event and represents the allotted attribution timeframe for subsequent in-app events to the same media source. AppsFlyer attributes all in-app events to Remerge for the complete duration of the re-engagement window (employed for Retargeting).
    
    
• Reporting - AppsFlyer's dashboard offers two levels of data visibility, available upon clicking either the Retargeting or User Acquisition tabs of the dashboard:
  
  
  • Retargeting Tab:
    
    
    • The displayed event data (conversions or otherwise) correspond with the selected retargeting date.
    • The displayed click data will contain the is_retargeting=true parameter appended to the attribution tracking link.
      
      
  • User Acquisition Tab - The displayed event data corresponds with the install date.

Remerge

Click - Remerge counts one click per an OpenRTB impression ID. In case of an issue with an operating system, SDK implementation, or a double ad click on behalf of the user, we deduplicate the click and count it once ONLY. 

Re-Engagement - First post-click in-app activity (e.g., app-open, session, search or view item). Please note: When it comes to re-engagement, Remerge DOES NOT differentiate between an app re-install or lack thereof preceding the first in-app event. 

Conversion - Conversion event of the campaign, as discussed and agreed upon with your Remerge Account Manager (e.g., purchase, booking, or other).

Dashboard - Attribution, windows, and reporting:

• Attribution - You are most likely to run with multiple ad networks or agencies. However, Remerge does not have visibility or insight into any other campaigns you could potentially be running with other partners. We consider ALL clicks triggered by Remerge. Accordingly, you can see the full effect of your Remerge campaign activity.
  
  
• Reporting - The displayed event data correspond with the timeframe in which the events took place. In other words, a specific timeframe grants visibility to ALL conversions that took place within said timeframe, regardless of the time lapse between the event and the re-engagement with which they are associated.
  
  
• Windows - Remerge's algorithm replicates AppsFlyer's windows, thus ensuring the accuracy of performance. We apply all windows on all Remerge clicks to their fullest extent.
  
  Please note: The Remerge dashboard considers ALL of our retargeting activity. All post-click Remerge activity is attributed to Remerge by Remerge. Our attribution windows match AppsFlyer's windows. The only difference between our and AppsFlyer's attribution windows lies in that we apply the windows on all Remerge's clicks as we do not have visibility on any of your other potential partner activities.
  
  

Frequently Asked Questions 

1. Do I require App Links for the Android tracking link?

No, you do not. Although it is possible to create App Links with AppsFlyer's Onelink solution, the standard Android tracking link (with the raw deep-link attached) is more than enough to run a campaign with Remerge. 

2. What should I do if I have a Universal Link?

If you have a universal link in place, please provide us with your iOS standard tracking link. For a step-by-step guide on iOS tracking link creation, visit our iOS Tracking Link Generation article.

Once you provide us with the tracking link, we append the &redirect=false parameter to the standard tracking link and use it to send AppsFlyer the click information server-side. You will still have visibility of this data in your AppsFlyer dashboard.

Please note: AppsFlyer's SDK is informed of both click and app-open via AppsFlyer's Onelink solution simultaneously, which by default means that attribution starts immediately. However, in case that click and app-open data are sent to AppsFlyer server-side, AppsFlyer has to periodically check if an app-open can be attributed to the last click. This information is processed slower than with AppsFlyer's Onelink solution, resulting in a delayed attribution to Remerge.

3. Do you also support mobile-web-based attribution?

Remerge can receive postbacks on web conversions. Even though we currently cannot utilize a mobile-web-based solution, we encourage you to provide us with your mobile web conversions via our Event Tracking API. Additionally, please append your mobile Device ID (IDFA, IDFV, GAID) to your postback.