AdColony campaign configuration

At a glance: AdColony, an AppsFlyer ad network integrated partner, is a premium video advertising network, providing advertisers and brands with an engaged and responsive audience and offers monetization solutions to publishers and developers. In addition to click-based mobile attribution, AdColony also offers cost, ad revenue, and view-through attribution, which you can record with AppsFlyer.

Setting up AdColony

To access AdColony settings:

  1. Go to Configuration > Integrated partners.
  2. Search for AdColony and select it.
  3. Update settings according to the following instructions.

Integration tab

The Integration Tab is divided into different sections as described below.

Activate partners

The partner must be activated by switching on the Activate partner toggle on the first visit, to enable its setup.

General settings

Enable View-Through attribution

Toggle this ON if you want to attribute view-through installs from AdColony. The view-through lookback slider is available on the Attribution link tab.

Default postbacks

AppsFlyer can send automatic postbacks to AdColony following installs and rejected installs. Use this section to define the source of the users for the postbacks.

Select This partner only for installs coming only from users attributed to AdColony.
Select All sources, including organic to have your entire user base available to be reported to AdColony.

Rejected installs can be sent for This partner only.

Launch postbacks

As of July 1, 2020, we no longer send launch postbacks to AdColony. If your integration was set up prior to this date, there may be changes to your configurations. The following table explains possible changes and your actions, where applicable:

Your configuration

Will be updated to

Your next actions

Send to AdColony all launches (from all media sources, including organic)

Send to AdColony:

  • all installs (from all media sources, including organic)
  • all af_app_opened events (from all media sources, including organic)

No further actions required. This update has no actual impact on the configuration.

Send to AdColony attributed first launches only

Send to AdColony installs attributed to AdColony only

If you wish to send af_app_open events as well:

  • In AppsFlyer, on AdColony integration page, configure sending the event under the In-app event postbacks section

Send to AdColony all launches (from all media sources, including organic)

BUT

No conversions have been attributed to AdColony in the 3 months prior to July 1, 2020

Send all installs

AND

For 30 days after July 1, 2020, all launches

If you wish to send af_app_open events as well:

    • In AppsFlyer, on AdColony integration page, configure sending the event under the In-app event postbacks section.

If done during the 30 days period, we will discontinue sending all launches and start sending all af_app_open events instead.

If done after the 30 days period, we will stop sending launches and won't send af_app_open events until configured otherwise.

In-app events settings

In this section, you can configure in-app event postbacks that are sent to AdColony.

To configure in-app event postbacks:

  1. Activate In-app event postbacks
  2. Click Add event to add an SDK Event to the list
  3. Parameter name Description
    SDK event name The name of the event, as received by AppsFlyer either from the SDK, or from server-to-server events.
    Tip: If you don't see the event you want in the list, activate this event on a device with a non-organic installation and recheck.
    Partner event identifier The unique name or ID of each event as defined on the partner's side. Select the most suitable pre-defined event for your SDK event.
    Sending option Select the sending option for the event:
    This partner only for events coming only from users attributed to AdColony.
    All sources, including organic to have your entire user base available to be reported to the partner
    Send event data
    • No values & no revenue: sends only the event itself without the event value.
    • Values & no revenue: sends all the parameters excluding the revenue value.
    • Values & revenue: sends all the event parameters, including the revenue value (if exists in the event).
  4. Click Save.

Attribution link tab

Generate and save attribution links and send them to the partner for attributing specific campaigns, ad sets, or single ads - both for UA and retargeting campaigns. You can use either a single-platform link or a OneLink.

Learn more about attribution link structure and parameters.

To generate an attribution link, follow these instructions.

Read more about how AdColony defines clicks and views.

Cost tab

AppsFlyer gets cost details by API. See the ad network cost integration table for full details on the supported dimensions, metrics, and features. Note: Cost data requires an Xpend subscription.

To enable the cost API:

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. 

 Warning

Once you set AdColony's cost do not change the name of any running campaign, ad set or single ad as it may cause serious discrepancies or missing cost data.

Ad revenue tab

This section is relevant if you are acting as a publisher, displaying ads of the partner to your users. As such, you would certainly like to measure the engagement of your users acquired from different sources, to find the most profitable sources for you.

To enable the ad revenue API:

Follow these integration instructions.

Permissions tab

In this tab, you can select the permissions to grant AdColony. Note that even if attribution is disabled for AdColony, the permissions tab is active and you can grant control to AdColony.

Use these toggles to give the ad network permissions to handle its own configuration for your app:

Ad network permissions

  • Allow to configure integration - permit the partner to set up the integration tab (except in-app event postbacks)
  • Allow to configure in-app event postbacks - permit the partner to setup in-app event postbacks mapping to itself on the integration tab
  • Allow access to your retention report - only to the partner's own retention data
  • Allow access to your aggregate loyal user data - only to the partner's own loyal user dataost data sync
  • Allow access to your aggregate in-app events data - only to the partner's own in-app events data
  • Allow access to your aggregate revenue data - only to the revenue data attributed to the partner
  • Allow access to your Protect360 dashboard - only to the partner's own Protect360 data, and providing the feature is enabled for the advertiser

Learn more about granting ad network permissions.