Banata

Operate Your Project

Add-ons

Extend your project with third-party integrations — Google Analytics, Segment, Stripe, and PostHog.

Add-ons let you connect third-party services to your authentication pipeline. You can toggle them on or off directly from your dashboard — no code changes, no redeployments. Once enabled, add-ons automatically forward relevant auth events to the connected service.

Available Add-ons

Add-onDescriptionUse Case
Google AnalyticsAttribute sign-ups to traffic sources and measure authentication funnel performanceMarketing attribution, conversion tracking
SegmentSend auth events to Segment destinations for centralized analyticsData warehouse integration, multi-tool analytics
StripeSync user creation and seat counts with Stripe subscriptionsBilling automation, seat-based pricing
PostHogSend auth events to PostHog for product analytics and feature flaggingProduct analytics, A/B testing, feature flags

Enabling and Disabling Add-ons

You manage all add-ons from the dashboard:

  1. Navigate to Authentication > Add-ons in the sidebar.
  2. Each add-on appears as a card showing its name, description, and current status.
  3. Click Enable to activate an add-on or Disable to turn it off.
  4. Your change takes effect immediately.

You can enable or disable any combination of add-ons at any time. Disabling an add-on stops event forwarding to that service but does not delete any data already sent.

Setting Up Each Add-on

Google Analytics

  1. Enable the Google Analytics add-on in the dashboard.
  2. Add your Google Analytics measurement ID to your application's environment variables.
  3. Auth events such as sign-up and sign-in are automatically attributed to traffic sources.
  4. Use GA4 reports to measure authentication funnel conversion rates.

Segment

  1. Enable the Segment add-on in the dashboard.
  2. Add your Segment write key to your application's environment variables.
  3. Auth events are sent to Segment as track calls.
  4. Use Segment destinations to forward events to your data warehouse, CRM, or other analytics tools.

Stripe

  1. Enable the Stripe add-on in the dashboard.
  2. Add your Stripe API keys to your application's environment variables.
  3. When a user is created, a corresponding Stripe customer is provisioned automatically.
  4. Seat counts sync when members are added to or removed from organizations.

PostHog

  1. Enable the PostHog add-on in the dashboard.
  2. Add your PostHog API key and host URL to your application's environment variables.
  3. Auth events are sent to PostHog as custom events.
  4. Use PostHog feature flags to gate features based on authentication state.

Security Considerations

  • Admin-only access — Only admin users can enable or disable add-ons.
  • API keys in environment variables — Third-party service credentials should always be stored in environment variables, not in the add-on configuration itself. The add-on toggle only controls whether the integration is active.
  • Data minimization — Only the auth event data required by each service is forwarded. Sensitive information such as passwords and tokens is never included.
  • Audit trail — Add-on state changes are tracked. Check your audit logs to see when an add-on was enabled or disabled.

Troubleshooting

Add-on is enabled but no data appears in the third-party service

  1. Confirm your service API keys are correctly set in your environment variables.
  2. Verify the add-on shows as "Enabled" in the dashboard.
  3. Trigger a test auth event (for example, sign in) and check both your audit log and the third-party service dashboard.

"Failed to update addon configuration"

Your backend may be unreachable or your account may lack admin privileges. Verify that your backend is running and that you are signed in as an admin.

Add-on states have reset

If your database was reset (for example, during a development environment rebuild), add-on states revert to their defaults with all add-ons disabled. Re-enable the ones you need from the dashboard.

Next Steps