In-app events postback configuration

In-app events enable advertisers to measure app engagement and user quality from different sources and to build an appropriate user acquisition strategy. Ad networks use in-app event information to optimize campaigns and run cost-per-action/event campaigns. Ad networks receive data of in-app events performed via postbacks. About rich in-app events

Postback in-app event selection

Advertisers select the in-app, events for which postbacks are sent using the settings described in this article.

In this article, in-app events include rejected events meaning in-app events blocked by Protect360 or events found to be non-compliant by target validation rules.

In-app event postback window

For example, if you're charged for events happening within 15 days of a user install, the window is configured as follows:

Postbacks after this period are not sent, and the network is not notified, but the events are still recorded in AppsFlyer and attributed to the network.

The postbacks are always sent based on the current window setting. See the following example:

Default settings

If you started using in-app event postbacks with a specific partner before July 30, 2019, the default setting for the window is Lifetime. This means that in-app event postbacks are always sent.

If you just started to set up the postbacks, the default window is automatically set to 180 days.

Who can configure postback windows

The window can be configured by:

• Advertisers
• Agencies, if they are given the Allow to configure in-app event postbacks permission
  Note: an advertiser and an agency working with the same ad network can configure postback windows separately from each other, based on their contract with the network.
• Ad Networks, if they are given the Allow to configure in-app event postbacks permission

Event mapping

Different advertisers can give different names to the events of the same type in their code. The names of the events used by the advertisers may also differ from the names given to them by media sources. For example, when a user purchases something through an app, one advertiser can call it a purchase, another one purchase_event. The ad network can pick a less informative ID, e.g. event5.

Most ad networks want to make sure that purchase is the same event as event5. Therefore, names must be mapped for each media source you work with.

Mapping methods

There are three possible methods of mapping the events. Each ad network has its own preference and you should discuss this with them. You can also give permission to the network to map the events on its own. See the next section to learn how to do that.

See Integrated partners, event mapping 

Sending options

For each event, you can choose in which case to send the postbacks:

• This partner only: send postbacks only when the event is attributed to the partner.
• Send all events: send postbacks for events attributed to any partner, as well as organic events.

If you choose to send all events "as they are", the sending option you select here also applies to all events.

Sending event data

You can choose which kind of event data you can share with the ad network in the postback. Select one of the following options:

• 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).

In postbacks, af_revenue and af_currency are written outside of the event_value JSON as monetary and currency and can be sent separately.

Note: When choosing the options with either no value or no revenue, the respective parameters are masked with N/A.

Conditional in-app event postbacks (beta)

Filter in-app event postbacks so that only events meeting filter conditions are sent to partners. Set filters based on event name, properties, and values.
Use this feature to optimize user segmentation, personalization, and retention.

Considerations

• AppsFlyer sends the event to the partner in the following scenarios:
  • Both the property and its value match the data on the event.
  • There were no conditions configured.
• In case there isn’t a match of the property or the value, the event won’t be sent. For example, if the data on the event is "event_value": "{\"level\":\"5\"}", and the property in the condition is “af_level”, then the event won’t be sent because the property doesn’t match (“level” on the event and “af_level” configured in the condition). In addition, if the data on the event is "event_value": "{\"level\":\"6\"}", and the value in the condition is 5, then the event won’t be sent because the values don’t match.
• Conditional in-app events can be configured for all partners including SRNs and analytics partners.
• Agencies are allowed to configure conditions for in-app events.
• The maximum number of conditions, which include a property and a value, is 5, per event.
• Currently, conditions can only be set to “equal”, and in case there are multiple conditions for a specific event, at least one of them needs to be met to send the postback.
• Complex structures such as arrays are not supported.
• It's recommended to test this feature with a test app or minor events to understand its impact on campaign optimization. 

To set up conditions for an event:

1. On the partner’s integration page, define and map the required in-app events to send to that partner.
2. Click the Add condition icon of the required event.
   

   

3. In the Property and Value fields, enter the property and its value for comparison.
4. Click Save Integration.

Editing multiple events

While mapping events, Sending option and Send event value fields can be edited for multiple events at once.

To edit multiple events:

1. Select the events to update
2. Click Bulk actions
3. Select the new setting to apply to all selected events:
   • Sending option (choose one option only)
     • This partner only
     • All media sources, including organic
   • Send revenue (choose one option only)
     • No values and no revenue
     • Values and no revenue
     • Values and revenue

Custom events

The list of events available for mapping shows only the events already reported by the SDK to AppsFlyer. If the event you want to map doesn’t appear in the drop-down list, this can happen for the following reasons:

• No user has performed the event yet.
• The event has been performed for the last time more than 2 weeks ago.
• If you have a large list of active events.

In either of these cases, in order to map the event to the ad network ID, you can do the following:

1. Type in the SDK name of the event.
2. Click Create custom

   

3. Map the event to the partner identifier.
4. Click Save to make sure the mapping is recorded.

Note that when you add the event in this way under a certain partner, this event is also added to the list of events in all other partner integrations you have. Meaning, you can see this event in the drop-down list under any partner’s integration, and map it normally.

Agencies and ad networks:

• Cannot add custom events
• Can view and/or map events if the advertiser added the event and grants the necessary permission

Event mapping by ad networks

Advertisers can also allow ad networks to map the events and disable postbacks on their own. To do so, an advertiser should give relevant permissions to the ad network:

1. On the Integrated Partners page find the partner you want to give permission to.
2. Under the Permissions tab switch the Allow to configure in-app event postbacks toggle to ON.

Once the ad network has received the permissions, it can map the events following the instructions in the Type Event ID Into Text Field.

Event mapping by agencies

To give the agency permission to configure in-app postbacks:

1. Find the agency in the list of integrated partners.
2. Select whether the agency can share or all events or only those attributed to the specific ad network.
3. Select whether the agency is allowed to send events revenue.
4. Select the specific events the agency is allowed to share.