No one can fake it though as they have to integrate with real services and we monitor it actively. That's the whole point of using a 3rd party. But curious to known why you thought it would be fake?

The op meant someone can make their own component that’s fake. Not that they’d send fake data to your service.

And there’s no way to distinguish a component that uses your real social proof from someone else’s fake social proof.

Gotcha, We added a verified by ProofyBubble text there but Do you think there’s a better way to distinguish?