Authdog

Segment

Last updated Oct 4, 2026
View as Markdown

Segment receives hosted authentication events for one environment: sign-in, sign-up, and waitlist. Authdog sends them with the write key you store here. Your Segment destinations then fan those events out. You do not install the Segment snippet on the hosted pages yourself.

Copy the write key

In Segment, open the source that should receive auth events and copy its Write key. Use a source that is not your production website source if you want auth events isolated.

Enable the add-on

In the Authdog console:

  1. Select the project and environment.
  2. Open Authentication > Add-ons.
  3. Select Segment.
  4. Enter the Write key. It is write-only. Leave it blank on a later edit to keep the stored key.
  5. Enable the add-on and save.

By default Authdog forwards:

  • signin_success
  • new_user
  • email_password_signup_success
  • user_joined_waitlist

Development and production need their own write keys so test traffic does not land in the production source. Add-on configuration does not copy between environments.

Test it

  1. Sign up a user in the environment you configured.
  2. In Segment, open the source debugger and confirm the event arrives.
  3. Repeat a sign-in and confirm signin_success as well.

A wrong write key makes Segment drop the event. Authdog still completes sign-in.

Read To learn how to
Events and webhooks The event names and what each one means
Google Analytics The same events, sent to GA4 instead
Marketplace The listing for this integration