Hi Alison,

Thank you for the update! After extensive digging with the Fivetran engineering team and reviewing Apple’s API documentation, here’s a summary of the specific challenge and our use case:

Currently, it isn’t possible to link financial line items to their corresponding apps when the sale is an in-app purchase (IAP) or subscription.

According to both the Connector ERD and Apple documentation, the intended join key is the Apple Identifier (app_id in Fivetran). However, this join only works reliably for paid apps—not for IAPs or subscriptions.

The key field, product_type_identifier, indicates whether a line item relates to an app purchase, IAP, or subscription (Apple reference). For product_type_identifier values corresponding to IAPs or subscriptions, the join to the app table yields no results.

Why this matters

Without a way to join financial data to app-level metadata, we can’t accurately report revenue, performance, or retention at the app level. We’ve had to rely on a manual SKU mapping table to infer relationships between IAPs/subscriptions and their parent apps — which is unscalable and error-prone, especially for publishers with multiple apps and complex IAP catalogs.

What would solve this

If the connector surfaced:

• an In-App Purchases Catalog table, and

• a Subscription Catalog table (if distinct),

we could join:

financial_report → in_app_purchase_catalog → app

and produce complete app-level reporting (e.g. Apple’s In-App Purchases Catalog Report).

This would enable comprehensive financial and performance reporting across all product types, not just paid apps.

Hi Dylan, I'll have our team look into seeing if this report can be supported. 

Frank