Install and uninstall tracking

The Partner API emits an event each time a merchant installs or removes one of your apps, and an agent reads these as they arrive. It applies your rules to update the merchant record, mark the app active or churned, and start the onboarding or win back steps you have defined. Clean events tied to a known merchant are recorded without review. When an install and uninstall arrive out of order, an event references a merchant your records do not know, or a churn looks like an accidental reinstall loop, the agent flags the case for a partnerships owner to interpret before status is changed.

Charge and transaction events

As the Partner API reports app charges and transactions, an agent reads the amount, merchant, and app on each event and updates your revenue records. It applies your rules to attribute the charge, mark it collected or pending, and note refunds against the right merchant. Events that line up with an expected charge post on their own. When a charge amount differs from the plan on file, a transaction cannot be tied to a subscription, or a refund exceeds what was collected, the agent holds the event and routes it to a finance owner, who checks the difference before the ledger is updated.

Partner record updates

Merchant and app details change over time, and an agent keeps your partner records aligned with what the Partner API reports. It reads incoming fields, applies your rules, and updates plan, status, and contact information per merchant and app. Straightforward changes that agree with existing data are written through. When a new value conflicts with a record you already hold, an event arrives for an app you have retired, or required fields are missing, the agent stops short of writing and notifies a partnerships owner to confirm the change, keeping your directory of merchants and apps trustworthy for reporting.