Platform Action Steps
Read, create, or update records in your tracker or traffic source via custom API endpoints.
Overview
Platform Action steps let you interact with a connected tracker (Affise, Binom, Voluum, RedTrack, Everflow, FunnelFlux Pro, BeMob, Cake) or traffic source (Adcash, PopAds, PopCash) API beyond just pulling stats. There are three types:
| Step | What it does |
|---|---|
| Platform Action - Get | Reads data from a tracker or traffic source API endpoint and exposes selected fields as variables |
| Platform Action - Edit | Updates an existing record via a tracker or traffic source API (e.g. change an affiliate's status, pause an Adcash campaign) |
| Platform Action - Add | Creates a new record via a tracker or traffic source API (e.g. add a new offer or affiliate, create a PopCash campaign) |
These step types were formerly called "Tracker Action Get/Edit/Add" — the step type IDs (tracker_action_get, tracker_action_edit, tracker_action_add) are unchanged, only the display name and scope (now including traffic sources) have expanded.
These steps are for advanced users who are comfortable working with API endpoints and JSON responses.
When to use Platform Actions
- Get: Read specific affiliate details, offer configurations, or conversion records that aren't available via standard Pull Stats stat types — or read an Adcash campaign, a PopAds campaign's details, or PopCash account info
- Edit: Update affiliate cap limits, change offer statuses, or modify conversion records based on conditions in your automation — or pause/start an Adcash or PopAds campaign, adjust a PopCash campaign's budget or targeting
- Add: Create new affiliates, offers, or campaigns programmatically as part of an automated workflow — or create a new Adcash or PopCash campaign
Prerequisites
Platform Action steps use your saved Connections — both trackers and traffic sources (Adcash, PopAds, PopCash), managed under Connections and Traffic Sources in the main menu respectively. You need a valid, active connection to the tracker or traffic source you want to interact with.
For trackers, the specific API endpoints need to be configured as Action Templates under Actions in the main menu — these define the endpoint URL, HTTP method, and parameter schema for each type of tracker action. For traffic sources (Adcash, PopAds, PopCash), the available actions come from a built-in catalog and require no additional setup — just select the connection and pick an action.
Adcash splits its API into two separate tokens: a Reporting API token (used by Pull Stats) and a Client API token (used by Platform Action steps). A connection only appears in a Platform Action step's connection picker if it has a Client API token configured.
Platform Action - Get
What it does
Makes a GET request to a tracker or traffic source API endpoint and lets you select which fields from the response to expose as variables.
Configuration
- Connection — select the tracker or traffic source connection to use
- Action — for trackers, select the pre-configured Action Template endpoint to call; for traffic sources, pick an action from the built-in catalog (e.g. Adcash "Get Campaign", PopAds "Get Campaign Details")
- Parameters — fill in any required parameters (e.g. affiliate ID, campaign ID, date range). Parameters can reference variables from previous steps.
Selecting response fields
After running a test request, the response JSON is displayed. Click on any field value to register it as a variable. Selected fields become available as {field_path_action_N} in subsequent steps.
Platform Action - Edit
What it does
Makes a PUT, PATCH, or POST request to a tracker or traffic source API endpoint to update an existing record.
Common use cases
- Updating an affiliate's payout cap after it's been reviewed
- Changing an offer's status from active to paused
- Modifying conversion approval status for specific records
- Pausing or starting an Adcash or PopAds campaign, or topping up its budget
- Adjusting a PopCash campaign's targeting, day-parting, or budget
Configuration
- Connection — select the tracker or traffic source connection
- Action — select the endpoint (tracker) or catalog action (traffic source) to call
- Parameters / Body — enter the values to update. You can use variables from previous steps (e.g. pass
{stats_1_affiliate_id}from a Pull Stats step to identify which record to update).
Platform Action - Add
What it does
Makes a POST request to a tracker or traffic source API endpoint to create a new record.
Common use cases
- Adding new affiliates to your network as part of an onboarding automation
- Creating new offers or campaigns programmatically
- Logging custom conversion events
- Creating a new Adcash or PopCash campaign from data pulled in an earlier step
Configuration
Similar to Edit — select the connection, the endpoint/action, and provide the required fields for creating the new record. Variable values from previous steps can be used in any field.
Setting Up Action Templates (trackers only)
Traffic source actions (Adcash, PopAds, PopCash) come from a built-in catalog and need no setup. For trackers, before using Platform Action steps you need to create the corresponding Action Template:
- Go to Actions in the left sidebar
- Click Add Action Template
- Select the connection (platform) this action is for
- Enter the API endpoint path, HTTP method, and define the parameters
- Save the template
Once saved, the template appears as an option inside Platform Action steps in the automation builder.
Action Templates are shared across automations — create them once and reuse in multiple workflows.
Tips for Using Platform Actions
- Test your endpoint using the Action Template's test feature (trackers) before using it in an automation
- Use variables in parameters — pass affiliate IDs, offer IDs, campaign IDs, or other values from Pull Stats steps to make actions dynamic
- Combine Get → Check → Edit — a common pattern is: Get a record, check a condition, then Edit it only if the condition passes
- Check your tracker's or traffic source's API documentation for available endpoints, required parameters, and rate limits