Types of integration
Projects can integrate Fuul in different ways according to their own interests and resources
By default, the app will provide guidance to projects for integrating Fuul using the Hybrid solution. However, depending on the specific nature of the program, desired user experience, or available resources, projects may choose to integrate different Fuul components into their own website. The flexibility exists to tailor the integration approach based on specific needs and preferences.
| Fuul Hosted | Hybrid | Project hosted | |
|---|---|---|---|
Partners create their tracking links on .. | a Fuul hosted page | a Fuul hosted page | a custom project domain page |
End users click on tracking links and land on ... | a Fuul hosted page | the project's app | the project's app |
Devs will need to ... | implement SDK on the app | create a partner onboarding page and implement SDK on the app | |
Projects will use this solution if they ... | don't have available dev resources to integrate the SDK | want the best experience for the end users and don't want to dedicate too much into integrating Fuul | want the best experience for content partners and end users |
Projects can always change the implementation type and its necessary information on the settings section on the app
Last updated