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.
- 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.
Revx specific client id. This can be found by contacting the RevX support team
RevX Cloud (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Send Revx Ping | Event type = "track", Event type ="screen" | Send Revx Ping |
Build your own Mappings. Combine supported triggers with the following RevX Cloud-supported actions:
Mapping limits per destination
Send event to revx
Send Revx Ping is a Cloud action. The default Trigger is type = "track" or type ="screen"
Platform of the device.
Optional
Identifier For Advertiser (IDFA/GAID)
Optional
A unique identifier for your event.
Optional
A unique identifier for your request type.
Optional
Identifier for Device Id for IOS and Android
Optional
The timestamp of the event. If time is not sent with the event, it will be set to the request upload time.
Optional
An object of key-value pairs that represent additional data to be sent along with the event.
Optional
An object of key-value pairs that represent additional data tied to the user
Optional
The current version of your application.
Optional
The name of the mobile operating system or browser that the user is using.
Optional
The version of the mobile operating system or browser the user is using.
Optional
The device brand that the user is using.
Optional
The device manufacturer that the user is using.
Optional
The device model that the user is using.
Optional
The carrier that the user is using.
Optional
The current country of the user.
Optional
The current region of the user.
Optional
The current city of the user.
Optional
The current Designated Market Area of the user.
Optional
The language set by the user.
Optional
The single product viewed or Added to cart.
Optional
The list of products purchased.
Optional
The current Latitude of the user.
Optional
The current Longitude of the user.
Optional
The IP address of the user. Use "$remote" to use the IP address on the upload request.
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.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Revx specific client id. This can be found by contacting the RevX support team