Affise

This reference guide maps the key performance entities between the Affise Performance UI and the Affise Performance API. 

___________________________________________________________

Please contact the Affise Customer Support team regarding all raised questions via the e-mail: <b><a href="mailto:support@affise.com" rel="nofollow noopener noreferrer" target="_blank">support@affise.com</a></b>.

UI entities vs. API entities matching

Request for Trial

API doc

Support

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

UI Term	API Field	Description
Clicks	`raw`	Total clicks tracked.
Hosts	`uniq`	Unique clicks.
Conversions	`actions`	Conversions
Revenue	`total` (offer payouts) / `charge` (statistics)	Total revenue generated (approved conversions).
Payout	`revenue`	Payment sum to an affiliate.

UI Term	API Field	Description
Approved	`confirmed`	Conversion is payable.
Hold	`hold`	Conversion is not payable. The system considers it invalid.
Declined	`declined`	Conversion will become payable automatically after a certain amount of time.
Pending	`pending`	Conversion is not payable, but the system consider it valid.

UI Term	API Field	Description
Active	`active`	The offer is active and accepts traffic
Disabled	`stopped`	The offer isn't live and doesn't accept traffic
Paused	`suspended`	The offer is temporary on pause and accepts postbacks for clicks done before a pause.

UI Term	API Field	Description
Balance	`balance`	Total balance.
Hold	`hold`	Balance for the conversions in Hold.
Payout	`available`	The balance payable.

UI entities vs. API entities matching

Statistics

Conversion statuses

Offer statuses

Affiliate balance