At a glance: Create email campaigns with integrated ESPs using OneLink branded links and deep linking for seamless user experiences that drive conversion.
About ESP integration
Email marketing is a simple, powerful, and effective way of engaging with customers and potential customers. Many marketers rely on email service providers (ESPs) to send large-scale email campaigns to their users. And while this should be a straightforward and simple process, delivering the perfect mobile user journey you envision, this is usually not the case.
What's the challenge?
The issues arise as a result of how the typical ESP handles its analytics, which tends to break deep links and negatively affect the mobile user experience. Deep linking refers to sending users directly to a specific location inside your app, which is a crucial functionality in effecting conversion. Providing a smooth deep-linking experience in email campaigns sent by ESPs is a real challenge as ESPs "wrap" the deep links for measurement purposes, which breaks the app-domain association required for iOS Universal links and Android App Links. This unfortunately results in:
- Routing users to mobile websites instead of deep linking them into the app
- Using the URI scheme deep-linking method which is less secure and provides a poor user experience
What's the solution?
To avoid these issues and provide mobile users with the best experience, click on your ESP in the section below and follow the specific integration instructions. Some ESPs are supported by an AppsFlyer integration solution that enables AppsFlyer to serve as an intermediary between the ESP server and your domain name. Its role as a proxy enables the provision of association files (AASA / asset links) which facilitates deep linking.
Supported ESPs
ESP email campaigns for mobile app users can cause attribution and deep linking issues. To avoid these issues, click on your ESP in the section below and follow the specific instructions in the link.
| Supported ESP list | Supports AppsFlyer beta integration |
|---|---|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No. Uses their own redirection method |
|
|
Yes |
|
|
Yes |
|
|
No. Uses their own redirection method |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No. Uses their own redirection method |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No. Uses their own redirection method |
|
|
Yes |
|
|
Yes |