Restricted Media Sources

Developing Document: This is a dynamic document that will be updated as Kochava adjusts to changes and updates that come from publishers/networks.

Feature Summary: You may notice Restricted as a network name across the Reporting/Query/Analytics tools. This indicates cases where user-level data is restricted and cannot be surfaced. This impacts campaign detail fields in row level reporting, while summary reports will continue to surface campaign detail with the same level of granularity. Attribution also remains un-impacted.

Before proceeding to the rest of the document, review the following definitions which will be used specifically to this document:

Redaction: The row level record is still attributed to the publisher, however all of the ad metadata is masked/removed/redacted from client availability. The ad metadata that was redacted at the row-level is/will be available when the client pulls summary/aggregate reporting where data is not associated to any specific device.
Restriction: The row level record is attributed to network designation called “Restricted” and those row level records will not be differentiable from the other publishers/networks who require Kochava to do this (ex. FB impressions and TT impressions).

Example:

After changes made to the Advanced Mobile Measurement (AMM) program, Facebook and Instagram view-through claims will be reported as Restricted. After April 22, 2020, advertisers no longer receive non-aggregated view-through data via Mobile Measurement Partners (MMPs). Attribution continues to be performed on Facebook view-through claims and full campaign detail will be available in aggregate reporting.

Data Handling by Network

Name	SAN	Non-SAN	Redactions	Restrictions
Amazon		✔	Row level data from the ad exposure, but it is allowable to be associate-able to all row level conversion data.	None
Google	✔		Redactions of campaign data on events if the ad interaction that won attribution is more than 180 days old, and the install or reengagement event happened after mid April of 2021.	None
Facebook	✔		Redactions of row-level claims made as a result of a FB click and impression: aggregate reporting of click and impression based installs is allowed after a specific threshold has been met.	Restriction of row-level claims made as a result of a FB click and impression: aggregate reporting of click and impression based installs is allowed after a specific threshold has been met.
Apple Search Ads	✔		None	None
Pinterest		✔	Redact row level data by default, but with VP level or higher approval, it can be made available, by advertiser.	None
TikTok		✔	Device-level ad exposure data for view-through conversions.	None
Twitter	✔		Device-level ad exposure data.	None
Pandora		✔	Redact row level data by default. With VP level or higher approval may be made available by advertiser.	No restriction
Snapchat	✔		Redact row level campaign details for impression based matches.	No restriction

WARNING: In order to receive row level data from Twitter, Advertisers must agree to Twitter’s Advanced Mobile Measurement (AMM) program. For more information, refer to Twitter’s support documentation.

Fields Impacted in Row-Level Reporting

BEST PRACTICES: Please ensure any recurring row-level data pulls from Kochava ingested into your internal Business Intelligence (BI) tools are accounting for these changes.

Data Point	New Value
Ad Interaction Date	Install Time
Network Name	“Restricted”
Network ID	ID: 10263
Campaign	“Default restricted”
Segment	“Default restricted”
Tracker	“Default restricted”
Attribution Module	“restricted”
Waterfall Level	“restricted”
All Ad Interaction Campaign Data	“- – -“

Campaign Manager

Restricted data will be associated with a campaign, segment, and tracker generated by Kochava, which will be viewable in Campaign Manager. See the above table for exact naming of these components.

Postbacks

Postbacks will continue to be sent when the delivery method is set to all, but will be subject to the data redaction shown in the table above.

Aggregate Reporting Available

Network Summary and Campaign Summary reports will surface the full ad interaction detail and provide insights into attributed counts overlaid with campaign data.

Summary Reports Can Be:

Pulled as One-Time or Recurring, through the dashboard or the API.
Delivered in CSV or JSON format to an email address or S3 bucket.
Adjusted for timezone.
Filtered by install date range, network name, campaign, tracker, country.
Grouped By:

Hour/Day/Week/Month/Year
Network
Campaign
Segment
Tracker
Site

Facebook’s Campaign Group Name, Campaign Name, Campaign ID
For Campaign Data Mapping for other media sources, refer to our Self-Attributing Networks Campaign Data Mapping support documentation.

Creative

Facebook’s Ad Group Name, Ad Group ID
For Campaign Data Mapping for other media sources, refer to our Self-Attributing Networks Campaign Data Mapping support documentation.

Country
DMA
State
City

NOTE: A count of 0 may also indicate x <100 records. 0 is surfaced in place of NULL to avoid breaking data ingestion when sourcing data from Kochava to populate external BI tools.

NOTE: Due to the device ID export feature in Analytics, campaign-level detail is not shown for restricted data and counts reported are aggregated under the Restricted network.

Custom Reports

Custom report requests containing restricted data are subject to the same process; row level restricted data can only be made available with data redaction applied. Aggregate reporting on restricted data is available and can include the full campaign detail.

As mentioned above and if your account allows, Custom Reporting can also be facilitated through the Kochava Query tool; please reach out to your dedicated Client Success Manager or support@kochava.com with additional questions.