At a glance
| Field | Detail |
|---|---|
| What | Set up and validate server events alongside an existing app measurement integration. |
| Who it matters to | App advertisers adding Snapchat conversion signals. |
| Where | Mobile app events sent using a Snap App ID. |
| When it applies | When implementing or reviewing an app event connection; this is an evergreen setup guide. |
| Action | Review ownership, event mappings and test results before evaluating campaign reporting. |
Snapchat Conversions API setup should begin with an inventory of the events your mobile measurement partner (MMP) already sends. Snap recommends using CAPI alongside an MMP integration. Our suggested approach is to establish the existing route, configure the additional connection and verify its behavior before interpreting campaign results. Snap’s API documentation supports that distinction.
Choose the implementation route
Snap documents direct and partner integrations. Direct implementation requires developer involvement; a supported partner integration may reduce that requirement. Choose according to the systems your team can configure and maintain. Snap’s getting-started guide describes these options.
| Approach | Documented capability | Limit or dependency | Suggested check |
|---|---|---|---|
| Direct CAPI | Send app events through Snap’s app endpoint. | Requires development work and authorized access. | Identify who owns implementation and maintenance. |
| Partner CAPI | Implement through a supported partner. | Depends on the partner integration. | Confirm support for your intended app event flow. |
| Adjust integration | Forward mapped app events and selected revenue data. | Revenue sharing requires relevant event mapping. | Review mappings and sharing options. |
| AppsFlyer integration | Configure Snapchat attribution and in-app event postbacks. | Activation, event selection and sharing settings affect the connection. | Review the selected app and postback configuration. |
App Ads Kit needs a separate evidence check. Snapchat’s public iOS repository identifies the SDK and directs readers to sign up for access, but its README does not provide initialization or event logging instructions. Current installation requirements and account eligibility are not specified in the cited documentation. If considering that route, obtain applicable implementation guidance before planning the work. Snap App Ads Kit repository.
Establish ownership and prerequisites
For CAPI, Snap requires Business Manager and uses a Snap App ID for mobile app events. Its recommended long-lived token can be generated by an Organization Admin through Business Details in Ads Manager, under Conversions API Tokens. The token can send events only for assets belonging to the organization that generated it. Snap’s prerequisites.
| Prerequisite | What to establish |
|---|---|
| Business Manager | Identify the organization responsible for the connection. |
| Snap App ID | Confirm the mobile app asset receiving events. |
| Access token | Confirm authorization and matching organization ownership. |
| Implementation route | Assign the developer or partner responsible for sending events. |
Keep the ownership record with your event definitions so later troubleshooting starts from the same configuration.
Configure the existing measurement connection
For Adjust, open Campaign Lab, select Partners, add Snapchat and choose the app. Review data sharing, map each intended Adjust event to the applicable Snapchat event, then complete Setup review and enable the integration. Adjust says detailed in-app revenue sharing requires mapping a revenue event. It also documents parameter mapping separately, so event forwarding alone should not be treated as confirmation that every desired parameter is included. Adjust setup documentation.
For AppsFlyer, select the app in Partner Integrations, find Snapchat and activate the partner. Copy the Snap App ID from Snap Business Manager into the integration. Then enable and configure in-app event postbacks, including the mapped event, which users’ events are sent and whether values or revenue are included. AppsFlyer documents those as separate choices. AppsFlyer setup documentation.
These are alternative vendor configurations. Review the instructions for the vendor actually supplying your events.
Construct and validate the additional events
Snap’s app request uses the Snap App ID. Its documentation requires app data, matching information and event fields; purchase events also require currency and value. It recommends consistent event identifiers across integrations and accurate timestamps for deduplication. Our suggested check is to trace a shared event through each sender and compare its identity and meaning. Snap’s request and deduplication guidance.
Snap provides an app validation endpoint, test logs, test statistics and Events Manager visibility. These tools check event construction and receipt without sending production events. Treat that evidence as a setup check, then review campaign attribution separately. Snap’s verification documentation.
| Problem or observation | Suggested check or documented remedy |
|---|---|
| Token cannot send to the app asset | Compare the token’s organization with the asset owner. |
| Validation rejects an event | Read the returned errors and correct the reported fields before retesting. |
| AppsFlyer event is missing from mapping choices | Follow its documented options to trigger the event on a non-organic installation or enter a custom mapping. |
| Adjust revenue forwarding is incomplete | Review revenue sharing and the mapped revenue event. |
What to review
- Compare event definitions across the app, measurement partner and additional sender.
- Check ownership and authorization before investigating payload errors.
- Review sharing scope and revenue settings explicitly.
- Keep validation results separate from attribution conclusions.
Use the measurement data-path review to document these checks and the evidence supporting each connection.



