# Custom Activation Flow : What's the best practice?

**URL:** <https://devforum.okta.com/t/custom-activation-flow-whats-the-best-practice/1440>\
**Category:** OAuth/OIDC\
**Created:** [March 15, 2018, 4:18pm UTC](https://devforum.okta.com/t/custom-activation-flow-whats-the-best-practice/1440 "2018-03-15T16:18:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tom](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/tom/32/24_2.png) [@tom](https://devforum.okta.com/u/tom)\
**Post date:** [March 15, 2018, 10:46pm UTC](https://devforum.okta.com/t/custom-activation-flow-whats-the-best-practice/1440/3 "2018-03-15T22:46:48Z")

</div>

Gave a little more information here:

> [@Redirect to Login or Application After Activation](https://devforum.okta.com/t/redirect-to-login-or-application-after-activation/783/7):
>
> This is getting a lot of heat. Let me talk about how you can do this today. I should have put this information in here before, I left out the information on what you need to do to the email. There is another email macro you can use, I think y’all are aware of ${activationLink}, there is also ${activationToken}. With this, you can modify the activation email to point to your own application: https://myapplication.com/activate?token=${activationToken} After your application gets the token, y…

---

_[View the full topic](https://devforum.okta.com/t/custom-activation-flow-whats-the-best-practice/1440)._