To activate the Snapchat Ads integration:

1. In AppsFlyer, from the side menu, select Collaborate > Partner Marketplace.
2. Search for Snapchat and select it.
3. Click Set up integration. You're directed to the Active Integrations setup page.
4. In the Integration tab, turn on Activate Partner. The toggle must stay on for as long as you work with the partner.
5. Pixel ID: Enter the Pixel ID. You can generate it or retrieve it from your Snapchat Ads Manager by following the instructions in the Snapchat Ads documentation.
6. Access token: Enter the access token. To create or retrieve it, follow the instructions in the official Snapchat Ads documentation.

You can define which web conversion events AppsFlyer sends to Snapchat Ads by mapping AppsFlyer events to Snapchat Ads events. These postbacks can be viewed in Snapchat Ads Manager. Snapchat uses the mapped events for campaign optimization and reporting.

To set in-app event postbacks:

1. Turn on In-app event postbacks.
2. If required, set the in-app event postback window. Read more in In-app event postback configuration.
3. Click Add event to add an event to the list.
4. In the AppsFlyer event column, select the event name from the list. AppsFlyer receives the event name either from the Web SDK integrated on your website or from server-to-server (S2S) events you send to AppsFlyer.
5. In the Mapped to Partner Event column, select the most suitable predefined partner event from the list.
6. In the For Users From column, select the appropriate option:
   • This partner only sends events attributed to Snapchat Ads.
   • All media sources, including organic sends all events regardless of attribution source.
7. In the including column, select whether to send events with their revenue values. See Data to include in the postbacks.
8. [Optional] Click the Add condition icon to set conditions for an event.

   Note

   • If you are setting a purchase event, set the including column to Values and revenue. Selecting any other option causes the postback to fail.
   • Currently, you can set only the purchase event to include revenue.
9. Click Save integration.

If you also run the Snap Pixel on your website, send the same event ID to both AppsFlyer and Snapchat so AppsFlyer can deduplicate the events:

• Include af_customer_event_id in the event payload you send to AppsFlyer. For the Web SDK, send it inside eventValue. For the S2S (server-to-server) API, send it either as a top-level field or inside event_value.
• Send the same value in the corresponding Pixel event.

AppsFlyer forwards this value to Snapchat as the event ID. Snapchat then uses it to deduplicate the server-side event it receives from AppsFlyer against the Pixel event, so AppsFlyer counts the conversion once.

If you don't send af_customer_event_id, AppsFlyer generates an event ID automatically. This ID won't match your Pixel events.

For more information, see [Beta] Integrate AppsFlyer Web SDK.

You can choose any predefined in-app event sent from AppsFlyer as your campaign goal. Select a campaign objective that aligns with your website conversion goals, for example, driving traffic to your website or optimizing for on-site conversions.

1. Under Destination, in the Website URL field, enter the URL of your website, the page where users land after clicking your ad. Website URL is the main destination option. Users click the ad and land directly on your website to complete conversion events.
2. [Alternative] AF attribution link (OneLink): If you want to redirect users to the mobile app with a fallback to the website, you can use an AF attribution link (OneLink) as the destination URL instead.
3. Click Build a URL parameter to add the URL parameters to the destination URL.
4. Under Custom parameters, click Add parameter.

5. Map the AppsFlyer parameters to their Snapchat values:

   AF parameter	Mapped Snapchat value
   pid	snapweb_int
   c *	{{campaign.name}}
   af_c_id	{{campaign.id}}
   af_adset	{{adSet.name}}
   af_adset_id	{{adSet.id}}
   af_ad	{{creative.name}}
   af_ad_id	{{ad.id}}
   af_channel	{{site_source_name}}

   * To simplify campaign analysis, include the campaign type (web or mobile) as a prefix or suffix in the campaign name, for example, campaign-name_web.

   For best practices on URL parameter configuration and traffic source resolution, see About traffic source resolution.

   An example of the resulting URL:

   https://www.example.com?pid=snapweb_int&c={{campaign.name}}&af_c_id={{campaign.id}}&af_adset={{adSet.name}}&af_adset_id={{adSet.id}}&af_ad={{creative.name}}&af_ad_id={{ad.id}}&af_channel={{site_source_name}}