DEVELOPING DOCUMENT: This is a dynamic document that will be updated as Kochava adjusts to changes and updates that come from publishers/networks.
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.
For Meta specifically, Standard Analytics shows Facebook and Instagram when AMM terms are signed; otherwise Meta rows appear under the “Restricted” network.
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 (e.g., certain impression-based attribution for some partners, or when a partner’s terms require restriction; for Meta this depends on AMM terms).
Example:
After changes made to the Advanced Mobile Measurement (AMM) program, Facebook and Instagram view-through claims may be reported as Restricted when AMM terms are not signed; when AMM terms are signed, Meta traffic appears as Facebook and Instagram in Standard Analytics. 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.
NOTE: Android installs attributed via the Google Play Install Referrer remain visible as Facebook/Instagram regardless of AMM terms.
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 | |
| Comcast | ✔ | Redactions of row-level claims made as a result of Comcast clicks or impressions. | Aggregate reporting of click and impression-based installs and events is allowed after a specific threshold has been met. | |
| ✔ | 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 | ||
| ✔ | Row-level ad metadata for click- and impression-based claims may be redacted per Meta AMM policy. Aggregate/summary reporting remains available. | When AMM terms are not signed, Meta API‑sourced attribution rows are attributed to the “Restricted” network in Standard Analytics. When AMM terms are signed, Facebook/Instagram appear as distinct networks in Standard Analytics (not “Restricted”). Aggregate/summary reporting remains available. | ||
| Apple Search Ads | ✔ | None | None | |
| ✔ | 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 | |
| ✔ | 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 | |
| ✔ | Click: Timestamp (date only) Campaign Metadata (Campaign ID & Name, Ad Group ID & Name, Ad ID & Name are available) Impression: Timestamp (date only) Campaign Metadata | None | ||
| Snapchat | ✔ | Redact row level campaign details for impression based matches. | No restriction |
WARNING: In order to receive row level data from X, Advertisers must agree to X’s Advanced Mobile Measurement (AMM) program. For more information, refer to X’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.
NOTE: The table below describes values when a row is restricted. For Meta specifically, rows are restricted in Standard Analytics only when AMM terms are not signed. When AMM terms are signed, Meta rows appear as Facebook/Instagram and will not use the “Restricted” or “Default restricted” labels.
| Data Point | New Value |
|---|---|
| Ad Interaction Date | Install Time |
| Network Name | “Restricted” (Meta: only when AMM terms are not signed; when signed, network name is Facebook or Instagram in Standard Analytics) |
| Network ID | ID: 10263 |
| Campaign | “Default restricted” (applies only when a row is restricted) |
| Segment | “Default restricted” (applies only when a row is restricted) |
| Tracker | “Default restricted” (applies only when a row is restricted) |
| Attribution Module | “restricted” (applies only when a row is restricted) |
| Waterfall Level | “restricted” (applies only when a row is restricted) |
| All Ad Interaction Campaign Data | “- – -” (applies only when a row is restricted) |
NOTE: Date ranges spanning AMM acceptance: In Standard Analytics, rows before acceptance appear as “Restricted” and rows after acceptance appear as Facebook/Instagram for the same account.
NOTE: Android referrer exception: Android installs attributed via the Google Play Install Referrer are visible as Facebook/Instagram regardless of AMM terms.
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.
NOTE: For Meta specifically, these Kochava‑generated “restricted” campaign components apply only when AMM terms are not signed. When AMM terms are signed, Meta rows appear under Facebook/Instagram and do not use the “Default restricted” campaign/segment/tracker.
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.
NOTE: For Meta, postback content follows Meta’s AMM policy; Analytics visibility (Facebook/Instagram vs “Restricted”) does not change postback delivery.
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.
NOTE: For Meta, campaign detail continues to be available in summary/aggregate reporting regardless of AMM terms.
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. For Meta, this applies only when AMM terms are not signed; when AMM terms are signed, Meta traffic appears as Facebook/Instagram (not “Restricted”)
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.
Meta AMM Row-Level Reports
- Two new detailed reports are available when Meta AMM terms are signed for the app:
- Install (Meta AMM)
- Events (Meta AMM)