RevenueHogdocs← back to app

Setup guide.

connect app store connect, pull your revenue, and optionally route apple's real-time subscription events through revenuehog.

Connect App Store Connect

RevenueHog authenticates to Apple with an App Store Connect API key. Create one in App Store Connect under Users and Access → Integrations → App Store Connect API, then add it under settings → credentials.

  1. 1
    In App Store Connect, generate a key with a role that can read sales. Finance or Sales is enough. RevenueHog never needs write access.
  2. 2
    Download the .p8 private key file. Apple lets you download it once, so keep it somewhere safe.
  3. 3
    Note the Issuer ID (top of the Integrations page) and the Key ID (next to the key you created).
  4. 4
    Paste all three into Settings and save. Your private key is encrypted at rest and scoped to your organization.

Read-only is enough

Use a key with read-only sales access. RevenueHog only reads reports; it never modifies anything, unless you opt into S2S auto-wiring, which needs an Admin key to update your notification URLs.

Deeper dive: Create an App Store Connect API key (.p8, Issuer ID, Key ID) walks the whole thing with screenshots-level detail, role guidance and a JWT snippet to prove the key works.

Run your first sync

As soon as your credentials are saved, RevenueHog discovers your apps and pulls daily sales and developer proceeds. A sync runs automatically every day; saving credentials again also kicks one off.

The first sync can take a minute while it backfills recent history. When it finishes, your apps, net revenue, and unit counts appear on the overview.

Currency conversion

Non-USD revenue is converted to USD using daily ECB reference rates for each sale's date; a row is flagged estimated only when no published rate is available. Apple's own payout reports remain the source of truth for exact figures.

Wire Apple Server-to-Server notifications

Daily syncs cover revenue. To see subscription lifecycle events (new subscriptions, renewals, cancellations, billing issues) the second they happen, point Apple's App Store Server Notifications (V2) at RevenueHog. Each app has its own ingest URL on its app detail page.

  1. 1
    Open apps → your app and copy the apple ingest url.
  2. 2
    In App Store Connect, set that URL as the App Store Server Notifications V2 endpoint for both the Production and Sandbox environments.
  3. 3
    If you already send notifications to your own server, add your existing endpoint under forwarding endpoints. RevenueHog verifies each notification and forwards Apple's verbatim signed payload on to you, so you lose nothing.

Let RevenueHog wire it for you

The S2S configuration audit can read what App Store Connect currently posts to and re-point it at RevenueHog automatically, preserving your existing endpoint as a forward. It's free for every app, like everything else on the web (see the billing reference).

Deeper dive: App Store Server Notifications V2: the complete setup guide covers the JWS verification, every notificationType, and testing. Useful whether or not RevenueHog is the endpoint.

Verify the connection

Open your app's detail page and check recent events: each notification Apple sends shows up with its type, environment, and forwarding status. The S2S configuration audit also reports whether App Store Connect is pointed at RevenueHog. Live events stream into the feed, and subscription activity rolls up on metrics.

No events yet?

Apple only sends notifications when something happens (a purchase, renewal, or cancellation). To force one, make a Sandbox purchase in your app, or use the send test buttons on the app detail page.