Set up an integrated partner

At a glance: Enable attribution measurement, send postbacks to partners, and enable other integration features by setting up the partner connection with AppsFlyer.


Partners, media sources, and third-party platforms integrate with AppsFlyer by API. This article contains the generic instructions to activate and set up the integration, including generating attribution links for non-SRN ad networks.

  • This guide isn't applicable to SRNs. Use the SRN explicit article. 
  • Some ad networks have dedicated articles.
  • Before setting up the configuration, contact the partner and open an account with them. 

Partner types in the ecosystem

The image below contains the different partner types that form the attribution ecosystem.


Related reading: AppsFlyer Performance Index ranks mobile media sources by category and region.

Partner type  Description
Ad networks

Run campaigns on your behalf.

Agencies Use their expertise to get high-quality users by running campaigns on your behalf. You can have a transparent or non-transparent relationship. 
Marketing partners Marketing partners specialize in working with specific ad networks. Examples: Meta campaign management partners, Apple Search Ads marketing partners, X marketing partners.
Retargeting networks Ad networks specializing in running retargeting campaigns.
Third-party platforms Provide BI-related services like analytics and marketing automation platforms.
Fraud detection  External third-party anti-fraud systems which are not part of the AppsFlyer Protect360 anti-fraud solution.

Partners in the marketplace

All partners, media sources, and other platforms integrated with AppsFlyer are found on the marketplace page. You can find both your active and inactive partners, and search for new partners to connect with. 

To search and filter all partners, media sources, or other platforms in the Partner Marketplace:

  • In AppsFlyer, from the side menu, select Collaboration > Partner Marketplace. You can use the various search filters.

Invite new partners to AppsFlyer

If the partner you're working with isn't yet integrated with AppsFlyer, you can send them an invitation link.

Your active integrated partners

The Active Integrations page in the Partner Marketplace shows all your active integrated partners. From this page, you can learn about the partner and manage the integration.  


The list of partners shown on the Active integrations page varies according to the selected app (the last app that was selected before entering the Marketplace). You can see which partners are connected to other apps by clicking the app from the top-left corner and selecting a different app. 

To see all your active partners:

  • In AppsFlyer, from the side menu, select Collaborate > Active integrations.

See what you can do from the Active Integrations page.

About the partner configuration page

The page is structured as follows:

  • Header, containing:
    • Partner name
    • Link to a dedicated partner article. If no dedicated article exists, this article displays.
    • Integration status
    • Selected app
  • Settings tabs: The tabs available depend on the partner type and supported features.
  • Footer:
    • Back to list: Return to the Active Integrations list using the filtering options selected previously.
    • Status message: Current status of the tab data (for example, saving, saved, error, there are unsaved changes).
    • Discard Changes: Undo the last changes without saving.
    • Save: Save the settings of the current tab only.

Applicable settings tabs per partner type

  Settings tab  
Partner type Integration  Permissions Remarks
Media source Y Y

Additional tabs available: Cost, ad revenue, attribution link

Includes ad networks, affiliate networks, direct publishers, programmatic advertising, China domestic ad networks, and retargeting Networks.
For SRNs the attribution link tab is non-applicable.

Agency  N Y Stand-alone agencies that don't function as ad networks
Third-party platform Y N Analytics or marketing automation platforms
Marketing partner  Y N  

Set up a partner (non-SRN)

To access the settings and configure your campaigns with the partner:

  1. Search for and select your partner, either from the Partner Marketplace or from the AppsFlyer side menu select Collaboration > Active Integrations page.
  2. Complete the settings per tab, as required. See the following sections.


The General settings step in the Integration tab is mandatory for all partners. You must also complete the Attribution link tab for non-SRN ad networks. The remaining tabs are optional.

Integration tab

Partner integrations differ in their requirements and can contain a subset of all possible options described in this section. There are some differences between iOS and Android settings.


Complete the sections as required. 

Integration sections

The following table includes different sections of the integration page. Some sections are available to all, others are specific per integration.

Section Description

Activate partner

Before sharing attribution links with a partner, you must enable Activate partner and complete the remaining sections of the Integration tab. 

  • Don't use Activate partner to pause or turn off campaign attribution
  • Disabling partner integration can cause irreversible damage to active campaigns.
  • Learn more about partner activation and the impact of deactivating a partner.

To activate an integrated partner:

  1. In AppsFlyer, from the side menu, select Collaborate > Active integrations.
  2. Search for and select the partner. You're directed to the partner configuration page.
  3. Turn on Activate partner.
  4. Click Save Integration.
  5. [Optional] To allow the partner to view the data attributed to them, make sure to turn Ad network permissions in the Permissions tab.   
Advanced Privacy

For iOS apps only:
When Advanced Privacy (for iOS 14.5+ and later) is turned on, you can control what data to share with the partner via postbacks and reports. This limits the sharing of user identifiers with the partner. Note that when Aggregated Advanced Privacy toggle is turned on in App Settings, Advanced Privacy (for iOS 14.5+ and later) is turned on and locked. 

Transaction ID

For iOS apps only:
When Share SKAN transaction ID is turned on, you're sharing the transaction ID of SKAdNetwork postbacks with the partner. By doing so, the partner could decode your SKAdNetwork Conversion Values.

General settings

Partner ID—Credentials
Some partners require credentials for AppsFlyer to integrate with them. Partners refer to this ID as app ID, account ID, user ID, or network ID. If this field displays, get the ID from the partner dashboard and enter it in the field.

Non EU Users

Decide whether or not to turn on Non EU users.

Install attribution

Set attribution windows to attribute new installs (first launches) of users who viewed or clicked your ad. The attribution lookback window is the maximum time from a click or a view of your ad to the install for which installs may be attributed to the partner.

  • Install click-through lookback window: Set the maximum time after a click-to-app that an install can be attributed to the click.

Install view-through attribution: Turn on to start attributing new installs by users who viewed your ad but didn't click it.

  • Install view-through lookback window: Set the maximum time after a view-to-app that an install can be attributed to the view.

Learn more about lookback windows.

Re-engagement attribution

Turn on and set the lookback windows to start attributing re-engagements of your existing users. For non-SRNs, this setting is available either in the Integration tab or in the attribution link tab. 

  • Re-engagement click-through lookback window: Set the maximum time after a click-to-app that the app launch can be attributed to the click as a re-engagement.

Re-engagement view-through attribution: Turn on to start attributing re-engagements of your existing users who viewed your ad but didn't click it.

  • Re-engagement view-through lookback window: Set the maximum time after a view-to-app that an app launch can be attributed to the view as a re-engagement.

Learn more about lookback windows.

Re-engagement window

Set the time window during which in-app events are primarily attributed to the re-engagement conversion. Learn more.

Ignore active users for retargeting

Set an inactivity window period to prevent recording retargeting conversions for active users within the specified time frame. See more about the Retargeting inactivity period.

For SRNs:

  1. From the Integration tab, turn on Re-engagement attribution.
  2. Turn on Ignore active users for retargeting.
  3. Set the Inactivity window

For non-SRNs:

  1. From the Attribution link tab, turn on Retargeting settings.
  2. Turn on Ignore active users for retargeting.
  3. Set the Inactivity window
Cross-platform attribution

When Cross-platform equal attribution priority is turned on, cross-platform impressions during the selected time frame have equal priority for attribution.

Preload attribution

When Preload attribution is turned on, installs are attributed to preload campaigns. Set the Preload lookback window to determine how long after device activation a preload install can be attributed to the partner.

Preload equal attribution priority

When Preload equal attribution priority is turned on, preload engagement during the selected lookback window has equal attribution priority as deterministic clicks.

Advanced Data Sharing

When Advanced Data Sharing is turned on, additional data is shared with the partner via the attribution link.
Note: This sharing option is different from the Meta ads AEM Advanced data sharing.

Default postbacks

When the partner integration is turned on, default postbacks are sent to partners relating to user actions occurring before the app launch, such as installs, rejected installs, and re-engagements.


  • Rejected events are in-app events blocked by Protect360 or events found to be non-compliant by target validation. In the case of rejected events, confirm with the partner that they have enabled reject event integration with AppsFlyer.
  • Tech partners receive default postback for installs. In some cases, they can also receive in-app event postbacks.

To configure default postbacks for the partner, define the source of users for sending postbacks:

  • This partner only: Send postbacks only when the event is attributed to this partner—meaning, the user who performed it came from this partner.
    Note: In the following cases, default postbacks are always defined as This partner only:
  • All media sources including organic: Send postbacks for events attributed to any partner and for organic events—meaning, the user who performed it came from any media source.
  • Off: Don't send default postbacks to this partner.

In-app event postbacks 

Map AppsFlyer events with the partner's events via postbacks. If postback sending is enabled, this includes rejected in-app events (events blocked by Protect360 or events found to be non-compliant with target validation rules).

To configure in-app event postbacks: 

  1. Set the Partner ID (if required).
  2. Enable In-app event postbacks.
  3. Set the In-app event postback window, if required (read more about in-app event postback window configuration).
  4. Click Add event to add an SDK or server-to-server event to the list.
  5. Complete the required parameters according to the mapping method.
  6. [Optional] Clickconditional-iae-postbacks-icon.pngto set conditions for sending certain in-app events to the partner.
Parameter name Description
AppsFlyer event

The name of the event, as received by AppsFlyer either from the SDK integrated into your app or from server-to-server events.
Tip: Don't see the event you're looking for?

  • Make sure to activate the event on a device with a non-organic installation, and recheck.
  • Type it in AppsFlyer event, then click Create custom. Read more about custom event mapping.
mapped to partner event

The unique name or ID of each event, as defined on the partner's side. Possible mapping configurations are:

  • Text field: Get the corresponding event ID from the partner.
  • Drop-down box: Select the most suitable pre-defined partner event.
  • As is: Send the events as they are, without mapping the event name.
for users from

Select the sending option for the event:

  • This partner only: Send postbacks only when the event is attributed to this partner—meaning, the user who performed it came from this partner.
  • All media sources including organic: Send postbacks for events attributed to any partner and for organic events—meaning, when the user who performed it came from any media source.

Select which event data to share with the partner in the postback:

  • No values & no revenue: Send just the event itself without any parameters (values or revenue).
  • Values & no revenue: Send all the parameters excluding the revenue value.
  • Values & revenue: Send all the event parameters, including the revenue value (if exists in the event).


  • Events mapped in the Integration tab for a specific partner are applicable both for standard and SKAN postbacks.
  • Postbacks are sent to partners in real-time. 
  • The AppsFlyer event name can either be selected or typed in.
    Typed values are permitted to have underlined spaces (low dashes) before or after the name of the event. Use underlined spaces only if the event name being sent from AppsFlyer has the same underlined spaces.

  • Important: Event names are case-sensitive. To avoid discrepancies, make sure you use the correct event name for all media sources and app versions.
  • If the In-app event postbacks section doesn't exist in the Integration tab, it means that the partner has not yet set up in-app event recording with AppsFlyer in its preliminary configuration. The partner can contact AppsFlyer using the partner assistant widget to finish the integration.

  • To prevent advertisers from sharing too much information with third-party platforms unintentionally, we have removed the Send all events (excludes uninstalls, sessions, and af_ad_revenue) option for third-party platforms, as of March 2019. Third-party platforms configured before this, still retain this setup option.

Related reading:

Save integration

Click Save Integration after making the changes. 

Connect more apps (optional)

After saving the integration, while remaining on the configuration page, you can integrate more of your apps with the partner.

  1. From the top-left corner, under the partner name, click the app name to open the list of apps. 
  2. Select a different app from the drop-down list.
  3. Repeat the integration steps for the selected app.

Attribution link tab

Generate and save attribution links for the use of click (non-SRN) ad networks, and send the attribution link to the partner to attribute specific campaigns, ad sets, or single ads.

Note: SRNs don't implement advertiser-generated attribution links so this tab isn't relevant to SRN campaigns.

To generate an attribution link:

  1. Select either Use a single-platform link or Use OneLink.

    Select Use a single-platform link if any of the following apply:

    • You plan to use only URI schemes to open the app.
    • You don't need to deep link with the URL.

    Select Use OneLink if any of the following apply:

    • You want a single link for both Android and iOS apps.
    • You want to use Android App Links or iOS Universal Links to open the app.
    • You want deep linking capabilities.

    Note: Selecting OneLink changes the click recording link from app specific to a OneLink URL.

  2. If you selected Use OneLink

    1. Select which OneLink template you want to use to open the app (and potentially deep link).
    2. [Optional] Enter the Deep link value.
    3. [Optional] Enter the Additional deep link value.
  3. Add parameters for Android and iOS, as needed.
  4. [Optional] Select additional attribution parameters.

Attribution link parameters


Adding parameters to the attribution link enables you to perform thorough drill-down analyses. Parameters that are already defined on the attribution link can be edited by adding them and their new values here. When saving the attribution link, all the parameters configured in this tab are saved.

Select which parameters you want to add to the attribution link.

Attribution link parameters

Name Description Attribution link parameter
Campaign Required parameter.
Compare different campaigns running with the media source.
Adset Compare different ad sets within specific campaigns of the media source. af_adset
Ad Name Compare different creatives within specific ad sets within specific campaigns of the media source. af_ad
Site ID and Sub Site ID

Required parameter.

Set Site ID to attribute installs to specific publishers.

The site ID must be passed to AppsFlyer in the attribution link because it:

  • Provides clarity and transparency about the publisher
  • Is used by AppsFlyer to identify and eliminate fraudulent publishers, and other traffic clusters.

Note that a missing Site ID won't affect attribution. Learn more about the Site ID parameter.

If there are many publishers, we advise limiting the number of used site IDs and using the subsite ID parameter, to avoid exceeding the site ID limitations.

af_siteid and af_sub_siteid
Subscriber Parameters Use any of the 5 subscriber parameters to insert useful values. Note that these parameters get parsed and appear in the raw data report, which makes them very handy for performing data aggregation or filtering. af_sub1, af_sub2, af_sub3, af_sub4, af_sub5

You can add other parameters to the attribution link by typing it in a new parameter box. You can use all AppsFlyer available URL parameters. Note that only URI scheme and OneLink parameters are encoded on the attribution link.

Retargeting settings

When retargeting is on: AppsFlyer recognizes a link as a retargeting attribution link, rather than a user acquisition link, by adding the &is_retargeting=true to the attribution link.
Attribution link parameter: is_retargeting

To use your link for retargeting:

  1. Turn on Retargeting settings.

  2. [Optional] Enter a URI scheme if you want a URI scheme to open the app.
    • URI schemes are recommended as a fallback method to open the app if Universal Links or App Links fail.
    • If you add a URI scheme here, it overrides any other URI schemes already in your OneLink template settings.
    • URI scheme is added to the link in the af_dp parameter.
  3. [Optional] Turn on Ignore active users for retargeting.
  4. Set the inactive window to determine which users are considered active and inactive.
  5. Set the re-engagement window to determine the time period following the re-engagement, where the user's in-app events are attributed to the retargeting media source.

    • You can set the value in days (1-90), hours (up to 23), or even lifetime.
    • The re-engagement window is added to the link in the af_reengagement_window parameter.

Click-through attribution

Use the setting to set the maximum time from click to install. Only installs (first launches) that take place within the lookback window are attributed.

Permitted range: 1-23 hours or 1-30 days.

Attribution link parameter: af_click_lookback

Learn more about the click lookback window.

Click attribution link


This is the attribution link that contains all the set up information you have set for it. You can save the link for future reference by clicking Save attribution link.

To copy the click attribution link:

  1. Click Save attribution link.
  2. Copy the generated link.

Send the link to the partner to be activated when your leads click on a corresponding ad.

View-through attribution lookback window

Set the maximum time from impression to install. Only installs (first launches) that take place within this lookback window, following an ad impression, are attributed to the partner, providing there was no other relevant ad click.

You can customize this value to 1-24 hours.

Attribution link parameter: af_viewthrough_lookback

Learn more about view-through attribution.

Impressions attribution link


The impression attribution link contains similar attribution data to the click recording link (besides the different lookback window). You can save the link for future reference by clicking Save attribution link.

Click Save attribution link and then copy the generated link.

To copy the impressions attribution link:

  1. Click Save attribution link.
  2. Copy the generated link.

Send it to the partner to be activated when a corresponding ad is watched, usually for 1 second or more.

Cost tab 

  • Cost data is reported by your integrated partners on the click or by Cost API.
  • The best practice is to implement Cost API (ROI360 subscription required).
  • Cost API includes clicks and impressions reports. See the ad network cost integration table for full details on the supported dimensions, metrics, and features.


If an advertiser uses an agency to run their campaigns, the agency, and not the advertiser, should integrate with the relevant partners. Otherwise, if both the advertiser and agency integrate with a partner using the same credentials for the same app, cost data is duplicated.

Enabling cost data by API

To enable the cost API:

Cost data sync status

View your cost API status and the last time AppsFlyer managed to pull matching cost data in either the cost (and ad revenue) integration status dashboard, or in the individual ad network dashboard.

Ad revenue tab

If you act as a publisher displaying ads in your app, the ad revenue function enables you to attribute ad revenue to the media source that brought the user. About ad revenue attribution. 

Enable ad revenue attribution

  1. Check to see which method, aggregate or user-level attribution, the partner supports.
  2. Follow the appropriate method in the ad revenue integration guide. 

Ad revenue API status messages

Status Remarks/action required
Active The connection is live and pulling data.
No data to pull was found. The connection was successful. The partner did not have any data related to this app.
Partner API not responding. Contact AppsFlyer support. The partner's server isn't responding to AppsFlyer.
Invalid credentials. Enter updated credentials.  
Something went wrong. Contact AppsFlyer support. There is a technical problem.
Partner data not yet ready. If the problem persists, contact AppsFlyer support.  
Data is being processed and will be available soon. We are currently processing the data received from the partner. The data will be available in the dashboards and reports.
Data was never successfully pulled If this status persists for a further hour contact AppsFlyer support. 

Permissions tab

Grant ad networks and agencies specific permissions to access your data and perform various actions.

  • You don't need the integration with a partner to be turned on to grant them permissions. 
  • Ad network set up by an agency: When partner setup is performed by an agency, the advertiser can view neither the ad network activation status nor the permissions granted. 
  • If your association with the partner is solely as an agency, use the Agency permissions instead of the Ad network permissions.
  • Permissions are granted for the currently selected app.

Ad network permissions

Turning on Ad network permissions allows the ad network access to your dashboard and enables granting additional permissions, as detailed in the table below.


Any access permissions are restricted to data owned by the ad network.

To grant permissions to an ad network and their team members:

  1. Turn on Ad network permissions.
  2. Grant permissions to ad network team members:
    • To grant specific team members permissions, you need to add them using their email addresses.
      To add a team member:
      1. Click Add team member.
      2. Enter the email of the ad network team member.
      3. Click Add.
  3. Select additional permissions to grant to the ad network:


    Capability granted

    Configure integration

    The ad network can change parameters in the integration tab, except for configuring in-app event postbacks.

    Configure in-app event postbacks

    The ad network can configure in-app event postbacks. This means they can create, define (map), and change postback settings.

    Caution! When both this permission and Configure integration are enabled simultaneously, the ad network has access to all events. This includes organic traffic and non-organic traffic from all media sources. 

    Access retention report

    The ad network can access the retention report involving their retention data only.

    Access aggregate loyal users data

    The ad network can access its own loyal users metric. 

    Access aggregate conversions data

    The ad network can access their aggregate conversion events metric reports. This includes installs, re-engagements, re-installs, and re-attributions. Example: Aggregated campaign performance for ad networks report

    Access aggregate in-app events data

    The ad network can:

    • Access in-app event data aggregate reports. The access includes all in-app events data of the selected app, including Protect360 in-app events data. This means they can access not just the events mapped in the postback configuration.
    • Access ad monetization data aggregate reports,  which may include ad monetization events from other media sources.

    View validation rules

    The ad network can view validation rule details.

    Access aggregate revenue data

    The ad network can access aggregate reports of in-app and ad revenue data attributed to users brought by the ad network. Note: This permission doesn't directly identify the ad revenue partner. However, if you've set the monetization event name to include the partner name, you may inadvertently disclose the identity of the monetization network.

    Use ad spend ingestion

    The ad network can:

    • Access the Ad Spend Ingestion window. This window displays only the apps they have permissions for.
    • Send ad spend files for ingestion. 

    Access Protect360 dashboard & raw data

    The ad network can:

    • Access their Protect360 dashboard (including ProtectLITE).
    • Access Protect360, Validation Rules, and raw data if they are part of the subscription plan. ProtectLITE doesn't include access to raw data.

    Note: When you have a Protect360 subscription, the ad network can see the full dashboard. Without a Protect360 subscription, they can see the lite dashboard. 

    Access ad revenue raw data

    The ad network can access their ad revenue data to use for UA optimization.
    Note: This permission is only available for apps with an ROI360 subscription.

Agency permissions

Read all about what agencies can do when granted permissions.

Caution: Agency installs occurring while the control is disabled are not attributed to the agency and don't show up on the agency's dashboard and data. Learn more about agency activation.

To grant permissions to an agency:

  1. Turn on Agency permissions.
  2. Select the permissions to grant to the agency:
    Permission Capability granted
    Change Advanced Privacy configuration

    The agency can change an ad network's Advanced Privacy data sharing setting. 
    This permission isn't applicable to TikTok for Business and Snapchat. For these integrations, the Advanced Privacy setting is grayed out, reflecting the advertiser's setting.

    Access retention and cohort reports The agency can access retention/cohort data created by the users brought by the agency only.
    Access aggregate organic data The agency can access aggregate organic data

    View validation rules

    The agency can view validation rule details.

    Add validation rules

    The agency can add and edit validation rules. Available when View validation rules is turned on. 
    Note: Agencies can't edit rules created by advertisers.

    Access raw-data reports

    The agency can access raw data reports for traffic attributed to the agency. Advertisers can't limit events an agency can view in the reports. 

    Access Protect360 dashboard & raw data

    The agency can:

    • Access your Protect360 aggregate dashboard
    • Access Protect360, Validation Rules, and raw data if they are part of the subscription plan

    Note: For advertisers that work with ad networks through an agency, in order for both the ad network and agency to access data, the advertiser must integrate both the agency and ad network in AppsFlyer and grant them both permission to access data. If only the agency is integrated and granted permission, the ad network does not have access to the data.

    Configure in-app event postbacks

    The agency can configure in-app event postbacks of specific events you select: 

    • Add event: From the drop-down menu, select events you approve granting the agency permission.

    The following options apply to the events you selected:

    • Send events revenue: When turned on, the agency can configure sending events including their monetary value.
    • Sending option: 
      • This partner only: When selected, the agency can configure sending postbacks only for events attributed to their own brought traffic
      • All media sources, including organic: When selected, the agency can configure sending postbacks for events attributed to all other media sources, agencies, and organic users.

Learn more about working with agencies.

Test the integration

After completing the partner integration, and before you start running campaigns with the newly added partner, it's important to test the integration. Mistakes are most likely to occur during setup. Testing in advance avoids the risk of spending considerable resources, only to discover your attribution data is missing or wrong. 


Before testing the integration, make sure to first test the app for basic SDK integration, including organic and non-organic installs.

Test the attribution link for non-SRNs

Non-SRN ad networks, which consist of 99.5% of integrated ad networks, use AppsFlyer attribution links. Similarly, owned media attribution is performed by using AppsFlyer OneLink links.

Since correct attribution depends on the parameters of the attribution links, test these links before you start to run a campaign with a non-SRN ad network or a custom attribution link.

To test attribution links:

  1. Create an attribution link.
  2. Send the new attribution link to your registered test device (via email or QR code).
  3. Click on the link, make sure you're redirected to the app store.
  4. Install the app.
  5. Launch the app.
  6. Check if the install appears in the AppsFlyer dashboard under the partner's media source name. Allow up to 30 minutes for the install to appear in the dashboard.
  7. Drill down to the campaign level (by selecting the partner in the Media source filter on the top of the overview page) to check the install appears under the correct campaign name.
  8. If necessary, continue to drill down and check the ad set and single ad levels too.

Test the SRN integration

SRNs such as Meta ads, Apple Search Ads, and Google Ads don't rely on external attribution links for attribution purposes. Instead, SRNs receive queries from AppsFlyer, attribute themselves, and return the answer. Therefore, it isn't feasible to test the integration separately from the network's system as with regular ad networks. You must separately test the integration with each SRN you work with.

To test SRN integration:

  1. Perform the full SRN setup on AppsFlyer in accordance with the specific SRN setup guide.
  2. Run a new low-budget campaign with the SRN partner.
  3. When the partner dashboard displays new installs check if they appear in the AppsFlyer dashboard under the partner's media source name.
  4. In the Overview dashboard, drill down to the campaign level, by selecting the partner in the Media source filter, to check that the install appears under the correct campaign name. Allow up to 30 minutes for the install to appear in the dashboard.
  5. If necessary, continue to drill down to check the adset and single ad levels.

If all is well you can start running new high-budget campaigns with the partner. It is sufficient to test integration once per SRN partner. Meaning, there's no need to test on a per campaign basis.

Test the raw data

If your subscription plan with AppsFlyer includes access to raw data, you should test raw data.

To test raw data:

  1. After performing the test mentioned previously, go to ReportsExport Data.
  2. Select the tested media source.
  3. Allow up to 15 minutes from the install and then download the Installs report.
  4. Check the install records from the partner exist and include parameters such as the media source, campaign name, touch time and type, device ID (if applicable), agency name (called "Partner" in the report), and so on.


Some ad networks require special actions to enable the collection of raw user-level data.

If you see a new install on the dashboard but don't see it in the raw data, consult the specific Help Center guide for the ad network, for example - X Ads.