User Acquisition Post-Install Specification 1.0

This specification describes the new post-install integration for Native Platform API partners and developers. The integration enables post-install events for conversions that are attributed by a 3rd Party Data Provider to a previously self-attributed app install claim or an in-app claim.

The spec is intended for 3rd Party Mobile Measurement Providers (3PMMP) who wish to integrate with Native Ad Platform via S2S, and is aimed at Data Providers, like Kochava, AppsFlyer, Adjust, Apsalar, CyberZ/FOX and others.

Once you sign up with Verizon Media, you’ll be able to directly attribute post-installs to a previous claim of your choice as a validated arbitration result.

Requirements

To take advantage of this new offering, you must meet the following requirements:

As a partner, you must integrate with Verizon Media’s Processor API. This is how Verizon Media will inform partners when Verizon Media users invoke their data subject rights granted to them under GDPR.

You must sign a contract to commit to Verizon Media that you will implement all aspects of GDPR in good faith, including deleting any data received from Verizon Media when the processor API instructs you to do so.

Typical Workflow

This is the workflow sequence that occurs when a user clicks on an ad that results in an app install or re-engagement, claim, arbitration result, and later when a post-install is recorded.

  1. A user clicks an ad, downloads an app, and opens the app.

  2. Data providers make the app-install claim request with the required details to Verizon Media. Verizon Media responses with a claim for the app-install claim request. The data provider then makes another arbitration request with the required details to Verizon Media. Verizon Media now stores the arbitration result if winner.

  3. The user may click a re-engagement ad, open the app, and may take further action.

  4. Data providers make the in-app claim request with the required details to Verizon Media. Verizon Media responses with a claim for the in-app claim request. The data provider then makes another arbitration request with the required details to Verizon Media. Verizon Media now stores the arbitration result if winner.

  5. If no one makes a claim, the post-install is awarded to the last claim of the owner.

  6. The Data Provider sends Verizon Media’s previously-awarded claim to the arbitration endpoint along with an indication that it’s a post-install.

  7. Verizon Media reports the post-install after joining with the current claim request and the previous claim request.

Endpoint

POST https://sp.analytics.yahoo.com/spp_ar

The request body should contain the claim response JSON, i.e., the previous response from the

https://sp.analytics.yahoo.com/spp_sa

endpoint

Request URL Parameters

Shown in the table below:

Key

Description

Example values

Type

Required?

Allow empty value?

dp

Native 3P provider ID, provided to 3P from a Native Ad Platform contact.

For example: Kochava

string

Yes

No. Must be non-empty and valid.

ai

Apple store ID”

Android: com.yahoo.mobile.client.android.mail iTunes: 577586159

string

Yes

No. Must be non-empty and valid.

mi

Google Ad ID, iOS IF.

Accepted ad IDs are: iOS IFA: 67247000-921f-41a1-ab22-b98b50716 40f Google Ad Id: 38400000-8cf0-11bd-b23e-10b96e400 00d

string

Yes

No. Must be non-empty and valid.

ar

Abitration result for post-install.

postinstall

string

Yes

No

arid

Post-install arbitration GUID.”

2eb97002-b91c-424b-9274-a9708fdafd00

string

Yes

No

id

Post-install id which was sent with the new claim request.

1234172534

string

Yes

No

et

In-app event time, in milliseconds, which was sent with the new claim request.

1453497859

int

Yes

No

Note

The id and et parameters are only required if the ar status is postinstall.

If the Data Provider chooses to provide a post-install status when Verizon Media has no current claim and the previous claim was not awarded, the ar status can be set to not_accepted.