At a glance
| Field | Detail |
|---|---|
| What | Choose how app events reach Meta: SDK logging, a measurement partner, or Conversions API. |
| Who it matters to | App advertisers and developers selecting an event integration or adding server events. |
| Where | iOS and Android app event integrations; partner requirements differ. |
| When it applies | During implementation or a change in event ownership, rather than a new rollout. |
| Action | Identify the sender for each event before adding another connection. |
Meta SDK vs Conversions API is a decision about event collection, delivery, and ownership. The options can work together: Apphud's documented Conversions API setup still requires the Facebook SDK and device attribution data for App Events. Our suggested starting point is to inventory the existing implementation before choosing another sender. Apphud's integration guide establishes that dependency.
Choose the responsibility you need
The SDK also serves app features beyond advertising measurement. Meta's iOS repository lists Login, Sharing, and App Links among its features. Review those dependencies before deciding whether the SDK can be removed. Meta's SDK repository documents its installation and features.
| Approach | Source-backed capability | Limitation | Suggested check |
|---|---|---|---|
| Facebook SDK in the app | Logs app events; Meta's iOS SDK also includes Login, Sharing, and App Links. | Removing event logging and removing the SDK are different changes. | Inventory the app features using the SDK. |
| Singular measurement integration | Singular says its SDK handles Meta attribution and event forwarding without requiring the Facebook SDK for measurement. | Parallel SDK logging can duplicate events. | Check which integration owns measurement. |
| Apphud Conversions API integration | Sends subscription and purchase events to Meta's servers. | App Events require SDK-derived device attribution data. | Confirm the device-to-server handoff exists. |
Singular recommends disabling automatic Facebook SDK event logging when Singular handles measurement and forwarding. That is a configuration recommendation for its integration. It does not establish how every Conversions API partner operates. Singular's coexistence guide explains the distinction.
Prepare the selected route
For Conversions API, Meta requires a dataset linked to the app before app events are sent. Its documentation requires action_source to identify app events as app. Meta's app events documentation provides the direct integration requirements.
| Prerequisite | Scope | What to verify |
|---|---|---|
| Linked dataset and app | Meta Conversions API app events | The destination dataset is linked to the intended app. |
| Device attribution data | Apphud App Events integration | Data is passed after both SDKs initialize. |
| App data enabled | Segment's Conversions API destination | Set use_app_data to Yes and configure its App Events Fields. |
| Tracking permission | Apple tracking rules | The intended data use respects the user's permission. |
For Apphud, the documented sequence is to install the SDKs, prepare the dataset and access token, configure the connection, and map Apphud events to Meta standard events. Missing device attribution prevents subscription events from being forwarded as App Events. Treat this as the Apphud route, rather than a universal installation recipe.
For Segment, app event support requires an explicit opt-in and its app field mappings. Its documentation distinguishes those requirements from the destination's website configuration. Follow the selected connector's app instructions when preparing the payload. Segment's destination documentation describes these settings.
Decide how repeated events are handled
Meta documents deduplication across Conversions API and existing app event integrations using event_name and event_id. Incorrect identifiers can cause events to be wrongly deduplicated. If the same action intentionally travels through multiple routes, review the identifier handoff across those routes. Use Meta's app-specific requirements for this design.
Our suggested distinction is to document whether a second sender supplies a different event or another copy of the same action. That makes the implementation decision reviewable before anyone interprets a change in reported conversions.
Verify delivery and eligibility separately
Segment documents checking Events Manager for events whose Connection Method is Server. It also provides a test event code setting that should be removed when sending real traffic. Apphud separately instructs iOS advertisers to check App Events Promotion eligibility for the selected event. Event receipt and event eligibility therefore deserve separate checks.
| Problem | Suggested review |
|---|---|
| Apphud subscription events do not arrive as App Events | Check the required device attribution handoff. |
| Events appear twice with Singular and Facebook SDK logging | Review Singular's guidance on disabling automatic Facebook logging. |
| Segment traffic remains configured as test events | Remove the test event code before sending real traffic. |
| An event arrives but cannot support the intended iOS setup | Review Apphud's documented eligibility check. |
Keep permission in the design
Apple requires App Tracking Transparency permission for tracking as it defines it, including linking app data with other companies' data for targeted advertising or advertising measurement. It also makes developers responsible for describing third-party SDK data practices. Our interpretation is to review the data use across the full route, including server delivery, when choosing the implementation. Apple's privacy guidance explains the scope.
What to review
- Check which SDK features the app still needs before changing its dependencies.
- Compare each event's intended sender with the actual logging and forwarding configuration.
- Review shared event identifiers wherever multiple routes carry the same action.
- Check delivery, test settings, and event eligibility independently.
- Keep event ownership and reporting definitions together in a measurement data-path review.



