AppsFlyer Rich In-App Events - Windows Phone

AppsFlyer’s rich in-app events provide advertisers with the ability to track any post-install event and attribute it to a Media Source and campaign.

An in-app event is comprised of an event name and event parameters (see below lists of recommended event and parameter names)

The following in-app events are defined as part of the AFInAppEventType interface and are recommended: 

Event String Constant

Event String Name

LEVEL_ACHIEVED

af_level_achieved

ADD_PAYMENT_INFO

af_add_payment_info

ADD_TO_CART

af_add_to_cart

ADD_TO_WISH_LIST

af_add_to_wishlist

COMPLETE_REGISTRATION

af_complete_registration

TUTORIAL_COMPLETION

af_tutorial_completion

INITIATED_CHECKOUT

af_initiated_checkout

PURCHASE

af_purchase

RATE

af_rate

SEARCH

af_search

SPENT_CREDIT

af_spent_credits

ACHIEVEMENT_UNLOCKED

af_achievement_unlocked

CONTENT_VIEW

af_content_view

LIST_VIEW

af_list_view

TRAVEL_BOOKING

af_travel_booking

SHARE

af_share

INVITE

af_invite

LOGIN

af_login

RE_ENGAGE

af_re_engage

UPDATE

af_update

OPENED_FROM_PUSH_NOTIFICATION

af_opened_from_push_notification

The following section describes the recommended structure of each event type together with the parameters mappings to Facebook, Twitter and Criteo:

 

af_level_achieved

Description: Used to track game level events.

Recommended attributes: af_level, af_score

Facebook Mapped Event: fb_mobile_level_achieved

Twitter Mapped Event: LEVEL_ACHIEVED

Criteo Mapped Event: None

Attributes Mapping:

AppsFlyer

Facebook

Twitter

Criteo

af_level

fb_level

level

-

af_score

-

-

-

 

af_add_payment_info

Description: Used to track payment info configuration status.

Recommended attributes: af_success

Facebook Mapped Event: fb_mobile_add_payment_info

Twitter Mapped Event: ADDED_PAYMENT_INFO

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_success

fb_success

user_payment_info

-

 

af_add_to_cart

Description: Used to track add to cart events of specific items.

Recommended attributes: af_price, af_content_type, af_content_id, af_currency, af_quantity

Facebook Mapped Event: fb_mobile_add_to_cart

Twitter Mapped Event: ADD_TO_CART

Criteo Mapped Event: viewBasket

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_price

_valueToSum

price_micro*

price**

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

item_id

af_currency

fb_currency

price_currency

-

af_quantity

-

number_items

quantity

 

af_add_to_wishlist

Description: Used to track add to wishlist events of specific items.

Recommended attributes: af_price, af_content_type, af_content_id, af_currency, af_quantity

Facebook Mapped Event: fb_mobile_add_to_wishlist

Twitter Mapped Event: ADD_TO_WISHLIST

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_price

_valueToSum

price_micro*

-

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

-

af_currency

fb_currency

price_currency

-

af_quantity

-

number_items

-

 

af_complete_registration 

Description: Used to track user registration methods

Recommended attributes: af_registration_method

Facebook Mapped Event: fb_mobile_complete_registration

Twitter Mapped Event: SIGN_UP

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_registration_method

fb_registration_method

registration_method

-

 

af_tutorial_completion

Description: Used to track tutorial completions

Recommended attributes: af_success, af_content_id

Facebook Mapped Event: fb_mobile_tutorial_completion

Twitter Mapped Event: TUTORIAL_COMPLETE

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_success

fb_success

-

-

af_content_id

fb_content_id

content_id

-

 

af_initiated_checkout

Description: Used to track checkout events.

Recommended attributes: af_price, af_content_type, af_content_id, af_quantity, af_payment_info_available, af_currency

Facebook Mapped Event: fb_mobile_initiated_checkout

Twitter Mapped Event: CHECKOUT_INITIATED

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_price

_valueToSum

price_micro*

-

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

-

af_currency

fb_currency

price_currency

-

af_quantity

fb_num_items

number_items

-

af_payment_info_available

fb_payment_info_available

user_payment_info

 

 

af_purchase

Description: Used to track purchase events (and associate revenue to them).

Recommended attributes: af_revenue, af_content_type, af_content_id, af_quantity, af_currency

Facebook Mapped Event: fb_mobile_purchase

Twitter Mapped Event: PURCHASE

Criteo Mapped Event: trackTransaction

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_revenue*

_valueToSum

price_micro**

price***

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

item_id

af_currency

fb_currency

price_currency

-

af_quantity

fb_num_items

number_items

quantity

af_validated

-

-

-

af_receipt_id

-

-

-

* af_revenue will be counted as revenue in AppsFlyer’s platform

 

af_rate

Description: Used to track app/item rating events.

Recommended attributes: af_rating_value, af_content_type, af_content_id, af_max_rating_value

Facebook Mapped Event: fb_mobile_rate

Twitter Mapped Event: RATED

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_rating_value

_valueToSum

price_micro

-

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

-

af_max_rating_value

fb_max_rating_value

max_rated_value

-

 

af_search

Description: Used to track search events.

Recommended attributes: af_content_type, af_search_string, af_success

Facebook Mapped Event: fb_mobile_search

Twitter Mapped Event: SEARCH

Criteo Mapped Event: viewSearch

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_content_type

fb_content_type

content_type

-

af_search_string

fb_search_string

search_string

-

af_date_a

-

-

din

af_date_b

-

-

dout

af_destination_a

-

-

-

af_destination_b

-

-

-

af_success

fb_success

-

-

 

af_spent_credits

Description: Used to track credit spend events.

Recommended attributes: af_price, af_content_type, af_content_id

Facebook Mapped Event: fb_mobile_spent_credits

Twitter Mapped Event: SPENT_CREDITS

Criteo Mapped Event: trackTransaction

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_price

_valueToSum

price_micro*

price**

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

item_id

 

af_achievement_unlocked

Description: Used to track achievement unlocking events.

Recommended attributes: af_description

Facebook Mapped Event: fb_mobile_achievement_unlocked

Twitter Mapped Event: ACHIEVEMENT_UNLOCKED

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_description

fb_description

description

-

 

af_content_view

Description: Used to track content view events.

Recommended attributes: af_price, af_content_type, af_content_id, af_currency

Facebook Mapped Event: fb_mobile_content_view

Twitter Mapped Event: CONTENT_VIEW

Criteo Mapped Event: viewProduct/viewListing

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_price

_valueToSum

price_micro*

price

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

item_id

af_currency

fb_currency

price_currency

-

 

af_list_view

Description: Used to track listings view events.

Recommended attributes: af_content_type, af_content_list

Facebook Mapped Event:

Twitter Mapped Event:

Criteo Mapped Event: viewListing

Attributes Mapping:

AppsFlyer

Facebook

Twitter

Criteo

af_content_type

-

-

-



af_content_list

-

-

product

 

af_travel_booking

Description: Used to track travel booking events (and associate revenue to them).

Recommended attributes: af_revenue, af_destination_a, af_destination_b, af_class, af_description, af_customer_user_id, af_content_type, af_content_id, af_date_a, af_date_b

Facebook Mapped Event: fb_mobile_purchase

Twitter Mapped Event: PURCHASE

Criteo Mapped Event: trackTransaction

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_revenue*

_valueToSum

price_micro**

price***

af_customer_user_id

-

-

cid

af_content_type

fb_content_type

content_type

-

af_content_id

fb_content_id

content_id

-

af_class

-

-

-

af_date_a

-

-

din

af_date_b

-

-

dout

af_destination_a

-

-

-

af_destination_b

-

-

-

af_success

fb_success

-

-

* af_revenue is counted as revenue in AppsFlyer’s platform

 

af_share

Description: Used to track sharing events.

Recommended attributes: af_description

Facebook Mapped Event: None

Twitter Mapped Event: SHARE

Criteo Mapped Event: None

Attributes Mapping:

AppsFlyer

Facebook

Twitter

Criteo

af_description

-

description

-

 

af_invite

Description: Used to track invite (social) events.

Recommended attributes: None

Facebook Mapped Event: None

Twitter Mapped Event: INVITE

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_description

-

description

-

 

af_login 

Description: Used to track user login events.

Recommended attributes: None

Facebook Mapped Event: None

Twitter Mapped Event: LOGIN

Criteo Mapped Event: None

 

af_reengage

Description: Used to track user re-engagement events.

Recommended attributes: None

Facebook Mapped Event: None

Twitter Mapped Event: RE_ENGAGE

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_description

-

description

-

 

af_opened_from_push_notification 

Description: Used to track app opens from push notification events.

Recommended attributes: None

Facebook Mapped Event: None

Twitter Mapped Event: None

Criteo Mapped Event: None

 

af_update

Description: Used to track update events.

Recommended attributes: af_content_id

Facebook Mapped Event: None

Twitter Mapped Event: UPDATE

Criteo Mapped Event: None

Attributes Mapping: 

AppsFlyer

Facebook

Twitter

Criteo

af_content_id

-

content_id

-

 

Optional Parameters:

In addition to the recommended parameters that can be passed with each event, the parameters below are defined as part of the AFInAppEventParameterName interface and can be sent as part of the event dictionary value:

 

Parameter String Constant

Parameter String Name

Recommended Value Type

REVENUE

af_revenue*

Float

PRICE

af_price

Float

LEVEL

af_level

Int

SUCCESS

af_success

Boolean

CONTENT_TYPE

af_content_type

String

CONTENT_LIST

af_content_list

Array of strings

CONTENT_ID

af_content_id

String

CURRENCY

af_currency

String

REGISTRATION_METHOD

af_registration_method

String

QUANTITY

af_quantity

Int

PAYMENT_INFO_AVAILABLE

af_payment_info_available

Boolean

RATING_VALUE

af_rating_value

Float

MAX_RATING_VALUE

af_max_rating_value

Float

SEARCH_STRING

af_search_string

String

DESCRIPTION

af_description

String

SCORE

af_score

Int

DESTINATION_A

af_destination_a

String

DESTINATION_B

af_destination_b

String

CLASS

af_class

String

DATE_A

af_date_a

String

DATE_B

af_date_b

String

EVENT_START

af_event_start

Unixtime

EVENT_END

af_event_end

Unixtime

LATITUDE

af_lat

Int

LONGITUDE

af_long

Int

CUSTOMER_USER_ID

af_customer_user_id

String

VALIDATED

af_validated

String

RECEIPT_ID

af_receipt_id

String

PARAM_1

af_param_1

String

PARAM_2

af_param_2

String

PARAM_3

af_param_3

String

PARAM_4

af_param_4

String

PARAM_5

af_param_5

String

PARAM_6

af_param_6

String

PARAM_7

af_param_7

String

PARAM_8

af_param_8

String

PARAM_9

af_param_9

String

PARAM_10

af_param_10

String

* af_revenue is the only parameter that is used for revenue calculations. Use it for events that actually represent revenue generation in your business logic. You can use af_price as a monetary parameter that are not counted as revenue (such as in an “Add to Cart” event).

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk