Userflow
For end user flow looks like that:
Where:
- tracker: is an affilka tracker. You can attach different domains to it, also you have to register all landings as destinations in it.
- landing: this is marketing with marketing form
- api: this is API that landing should use for acquiring information about currencies, promo codes etc. And the main: this API used for user registration. This is crucial – if this API blocked, none of landings will work. Please be aware of that and keep an eye to use some domain that is not blocked for hosting API. If you can't – we can proxy requests to that API using landing itself, but it should be supported by API (to be discussed)
- rotator: some web app, that determines with of casino URL should be used by customer. I actually don't know why you need that, but it was requested to use it.
- casino: actually product
Caveats:
- api used for registration could have another domain rather final casino domain (which is obtained at rotator). Because of that, cookie authorization does not work (because cookies stick to issuing domain – API domain). That's why we have to request some additional JWT functionality. If we can use real casino domain as API domain – we can avoid passing JWT and cut of rotator part.
- we should implement integration with ReCAPTCHA to avoid API DDoS.
- we should implement affilka integration (it's a bit unclear how for now, because
/api/client/partner/track_stagseems like a method for casino, not landing)
