# RevX Cloud (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **RevX Cloud (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[RevX Cloud (Actions)](https://revx.io/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) helps app marketers achieve their growth objectives by simplifying programmatic advertising for them. With RevX, your reach extends to over 90% of app users globally, encompassing more than 1 million mobile apps. Leverage audience intelligence to achieve highly precise targeting, accompanied by personalized messaging. Employ advanced AI-driven audience segmentation to identify high-intent players, while optimizing creatives to amplify performance to new heights.

This destination is maintained by RevX. For any issues with the destination, [contact their support team](mailto:tse@revx.io).

## Getting started

1. From the Segment web app, click **Catalog**, then click **Destinations**.
2. Find the Destinations Actions item in the left navigation, and click it.
3. Click **Configure RevX Cloud (Actions)**.
4. Select an existing Source to connect to RevX Cloud (Actions).
5. Add Revx Client ID as provided by the tse team.

## Destination Settings

| Field          | Description                                                                    | Required | Type   |
| -------------- | ------------------------------------------------------------------------------ | -------- | ------ |
| Revx Client ID | Revx specific client id. This can be found by contacting the RevX support team | Yes      | string |

## Available Presets

RevX Cloud (Actions) has the following presets

| Preset Name    | Trigger                                     | Default Action |
| -------------- | ------------------------------------------- | -------------- |
| Send Revx Ping | Event type = "track", Event  type ="screen" | Send Revx Ping |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following RevX Cloud-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Send Revx Ping](#send-revx-ping)

### Send Revx Ping

Send event to revx

Send Revx Ping is a **Cloud** action. The default Trigger is `type = "track" or type ="screen"`

| Field                                 | Description                                                                                                | Required | Type     |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------- | -------- |
| Platform                              | Platform of the device.                                                                                    | Yes      | STRING   |
| Identifier For Advertiser (IDFA/GAID) | Identifier For Advertiser (IDFA/GAID)                                                                      | No       | STRING   |
| Event name                            | A unique identifier for your event.                                                                        | No       | STRING   |
| Request type                          | A unique identifier for your request type.                                                                 | No       | STRING   |
| Identifier For Vendor (IDFV)          | Identifier for Device Id for IOS and Android                                                               | No       | STRING   |
| Timestamp                             | The timestamp of the event. If time is not sent with the event, it will be set to the request upload time. | No       | DATETIME |
| Event Properties                      | An object of key-value pairs that represent additional data to be sent along with the event.               | No       | OBJECT   |
| User Properties                       | An object of key-value pairs that represent additional data tied to the user                               | No       | OBJECT   |
| App Version                           | The current version of your application.                                                                   | No       | STRING   |
| OS Name                               | The name of the mobile operating system or browser that the user is using.                                 | No       | STRING   |
| OS Version                            | The version of the mobile operating system or browser the user is using.                                   | No       | STRING   |
| Device Brand                          | The device brand that the user is using.                                                                   | No       | STRING   |
| Device Manufacturer                   | The device manufacturer that the user is using.                                                            | No       | STRING   |
| Device Model                          | The device model that the user is using.                                                                   | No       | STRING   |
| Carrier                               | The carrier that the user is using.                                                                        | No       | STRING   |
| Country                               | The current country of the user.                                                                           | No       | STRING   |
| Region                                | The current region of the user.                                                                            | No       | STRING   |
| City                                  | The current city of the user.                                                                              | No       | STRING   |
| Designated Market Area                | The current Designated Market Area of the user.                                                            | No       | STRING   |
| Language                              | The language set by the user.                                                                              | No       | STRING   |
| Product                               | The single product viewed or Added to cart.                                                                | No       | OBJECT   |
| Products                              | The list of products purchased.                                                                            | No       | OBJECT   |
| Latitude                              | The current Latitude of the user.                                                                          | No       | NUMBER   |
| Longtitude                            | The current Longitude of the user.                                                                         | No       | NUMBER   |
| IP Address                            | The IP address of the user. Use "$remote" to use the IP address on the upload request.                     | No       | STRING   |

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to RevX Cloud (Actions)  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field          | Description                                                                    | Required | Type   |
| -------------- | ------------------------------------------------------------------------------ | -------- | ------ |
| Revx Client ID | Revx specific client id. This can be found by contacting the RevX support team | Yes      | string |
