# Segment Tracking Theme Component

**URL:** https://meta.discourse.org/t/segment-tracking-theme-component/133335
**Category:** Theme component
**Tags:** end-of-life
**Created:** [November 13, 2019, 8:10pm UTC](https://meta.discourse.org/t/segment-tracking-theme-component/133335 "2019-11-13T20:10:59Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [August 10, 2021, 12:08am UTC](https://meta.discourse.org/t/segment-tracking-theme-component/133335/10 "2021-08-10T00:08:36Z")

</div>

> [@paigen11](#):
>
> Additionally, though after speaking to others in my org, we may end up just waiting until we have Oauth set up so that our users will have to use the same ID logging in to our system and the Discourse system.

This seems like the ideal approach. The Segment theme component could be updated to add an option to include the `provider_uid` that is supplied by your Auth provider.

I’m glad you brought this up. The Segment tracking component currently has an option to add the user’s `external_id` for site’s that are using [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true). Looking at it now, I see that it is using the old settings name for for [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) - it is checking to see if the `enable_sso` setting is enabled. That needs to be changed to `enable_discourse_connect`. I’ll get that fixed tomorrow.

---

_[View the full topic](https://meta.discourse.org/t/segment-tracking-theme-component/133335)._