Integration identifiers are the bridge between AppActor customers and external tools. They are not general customer attributes. They are provider-specific IDs that help downstream destinations match subscription events to the right user or device.

​
What to send

Use the narrowest API. That keeps AppActor able to route, clear, merge, and deliver each data type correctly.

​
Matching model

When AppActor sends subscription events to a partner, integration identifiers help that partner connect the event to its own user or device graph. Campaign attribution adds marketing context to the same customer and purchase timeline. For example:

​
Event context

AppActor can attach attribution and integration context to subscription lifecycle events such as purchases, renewals, cancellations, and refunds. This is why ID and attribution setup should happen before or near the monetization flow whenever possible. If identifiers arrive after a purchase, future events can still use them, but earlier events may already have been delivered without that partner ID.

​
Clearing

Use explicit clear paths:
  • unsetIntegrationIdentifier(...) for provider IDs
  • unsetAttribute(...) for custom attributes
  • attribution helper clears or typed attribution payloads for campaign fields
Avoid using empty strings as deletes unless a specific SDK method documents that behavior.

​
Identity merges

If an anonymous customer later logs in, AppActor preserves attribution and integration context through the customer identity flow where possible. The exact merge behavior is server-side so SDK code should keep sending the current known IDs after login.

​
Privacy

Only send identifiers you are allowed to collect and share. Device and advertising identifiers can affect App Store or Play Store privacy disclosures.

Attribution System

Choose the right surface for customer attributes, integration IDs, campaign attribution, Apple Ads, and Install Referrer.