# How are you handling server-side remote evaluation changes in Amplitude Feature Experimentation?

I like the clean, intuitive interface and how easy it is to monitor experiments after launch and make statistically sound, data-backed decisions. But for fully server-side implementations using remote evaluation, the March 10, 2026 update means we now have to send an additional $exposure event ourselves, which adds work and can increase costs if events go through a TMS. It still helps us test complex engineering features and decide what to deploy quickly using solid statistics (sequential testing or t-test). If you run server-side experiments, how did you handle the migration and documentation gaps?

##### Post Metadata
- Posted at: 18 days ago
- Author title: Lead product analyst
- Net upvotes: 1



## Related Product
[Amplitude Feature Experimentation](https://www.g2.com/products/amplitude-feature-experimentation/reviews)

## Related Category
[A/B Testing](https://www.g2.com/categories/a-b-testing-tools)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


