AppsFlyer — export Lytics audiences as in-app conversion events

The new AppsFlyer integration lets you drive AppsFlyer in-app conversion events straight from a Lytics audience, without waiting for the event to fire on a user's device. Send events like af_purchase, af_complete_registration, or a custom name — backed by the cross-channel behavior, data science scores, and content affinities that power your Lytics audiences — and they land in AppsFlyer's reporting to feed attribution, retargeting, and analytics.

What's new

• Activate audiences as server-to-server events. Any Lytics audience can drive AppsFlyer in-app events, so the segments you already build for email and display can also power mobile attribution and retargeting.
• Match on the right mobile identifier. Map your Lytics fields to AppsFlyer identifiers (IDFA/IDFV for iOS, GAID/OAID/Android ID for Android, plus uid/cid) and the export picks the platform-appropriate one per user.
• Enrich events with revenue and product context. Map fields to AppsFlyer event_value keys (af_revenue, af_currency, af_content_id, and more) to send purchase and conversion detail alongside each event.
• Stay current automatically. Trigger on audience enters, exits, or both - and optionally on changes to up to 75 user fields — with a one-time backfill of existing members on start.

How it works

The integration uses AppsFlyer's S2S in-app events bulk endpoint with a per-app Dev Key authorization. The Dev Key signs each batch (HMAC-SHA256) and is never sent in plaintext or logged. Note that this export sends post-install events only. AppsFlyer reserves the install and launch counters for on-device SDK events, and it handles iOS ATT / limited-tracking users per AppsFlyer's zero-UUID spec.

See AppsFlyer for the full authorization and configuration walkthrough.