RevX Cloud (Actions) Destination
RevX Cloud (Actions) 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.
Getting started
- From the Segment web app, click Catalog, then click Destinations.
- Find the Destinations Actions item in the left navigation, and click it.
- Click Configure RevX Cloud (Actions).
- Select an existing Source to connect to RevX Cloud (Actions).
- Add Revx Client ID as provided by the tse team.
Destination Settings
| Setting | Description |
|---|---|
| Revx Client ID | Required. Revx specific client id. This can be found by contacting the RevX support team |
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 with the following RevX Cloud-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
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 |
|---|---|
| Platform* | Type: STRINGPlatform of the device. |
| Identifier For Advertiser (IDFA/GAID) | Type: STRINGIdentifier For Advertiser (IDFA/GAID) |
| Event name | Type: STRINGA unique identifier for your event. |
| Request type | Type: STRINGA unique identifier for your request type. |
| Identifier For Vendor (IDFV) | Type: STRINGIdentifier for Device Id for IOS and Android |
| Timestamp | Type: DATETIMEThe timestamp of the event. If time is not sent with the event, it will be set to the request upload time. |
| Event Properties | Type: OBJECTAn object of key-value pairs that represent additional data to be sent along with the event. |
| User Properties | Type: OBJECTAn object of key-value pairs that represent additional data tied to the user |
| App Version | Type: STRINGThe current version of your application. |
| OS Name | Type: STRINGThe name of the mobile operating system or browser that the user is using. |
| OS Version | Type: STRINGThe version of the mobile operating system or browser the user is using. |
| Device Brand | Type: STRINGThe device brand that the user is using. |
| Device Manufacturer | Type: STRINGThe device manufacturer that the user is using. |
| Device Model | Type: STRINGThe device model that the user is using. |
| Carrier | Type: STRINGThe carrier that the user is using. |
| Country | Type: STRINGThe current country of the user. |
| Region | Type: STRINGThe current region of the user. |
| City | Type: STRINGThe current city of the user. |
| Designated Market Area | Type: STRINGThe current Designated Market Area of the user. |
| Language | Type: STRINGThe language set by the user. |
| Product | Type: OBJECTThe single product viewed or Added to cart. |
| Products | Type: OBJECTThe list of products purchased. |
| Latitude | Type: NUMBERThe current Latitude of the user. |
| Longtitude | Type: NUMBERThe current Longitude of the user. |
| IP Address | Type: STRINGThe IP address of the user. Use “$remote” to use the IP address on the upload request. |
Engage
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an 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.
Real-time to batch destination sync frequency
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.
| Setting | Description |
|---|---|
| Revx Client ID (required) |
string. Revx specific client id. This can be found by contacting the RevX support team |
This page was last modified: 07 Aug 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!