# Cloud Destinations

RudderStack supports integration with over 150 popular destination platforms like Google Analytics, Amplitude, Braze, Mixpanel, Salesforce, and more.

This section provides detailed documentation on setting up these destinations in RudderStack to send your event data in no time.

## Supported destinations

{{< destinations type="streaming" >}}

## Webhook

RudderStack's HTTP Webhook destination lets you send the events tracked by the RudderStack [SDKs]({{< ref "sources/event-streams/sdks/_index.md" >}}) and [cloud apps]({{< ref "sources/event-streams/cloud-apps/_index.md" >}}) sources.

{{< success >}}
This integration is helpful in cases where you want to apply some custom logic on the event payloads before sending them to your preferred destinations.
{{< /success >}}

{{< destinations type="webhook" >}}

## Web device mode destinations

If you are looking for destinations that support web device mode in particular, see the [JavaScript SDK repository](https://github.com/rudderlabs/rudder-sdk-js/tree/develop/packages/analytics-js-integrations/src/integrations/).

## Event properties with reserved keywords

Do not include any property named `__proto__`, `constructor`, or `prototype` in your calls when tracking events in web [cloud or device mode]({{< ref "destinations/rudderstack-connection-modes.md" >}}) (that is, using [JavaScript SDK]({{< ref "sources/event-streams/sdks/rudderstack-javascript-sdk/" >}}) as source).

RudderStack will automatically drop the properties containing these names, as these are considered reserved keywords.

Note that this is applicable to all events (`identify`, `track`, `page`, `screen`, and `group`) supported by RudderStack.