Conversion Reporting - Which One Should I Use?


Conversion Reporting provides tracking, reporting and compensation of conversion events such as, phone leads and web sales. When a call results in a conversion event, you can pass that information to the Invoca platform for your records and to trigger affiliate payouts.

With two ways of reporting conversions to Invoca, it can be difficult to know which one to use for your specific business case.  In this article, you will receive an overview of each type of Conversion Reporting as well as tips on which one you should used based on your business’s capabilities of providing us with this information.

If you are not working with affiliates and would like to report call conversions and/or call dispositions please refer to our Signal documentation.

Conversion Reporting API

The Conversion Reporting API (formerly known as the “Call Center” or “Sales Reporting” API) is used to report completed order information (or other conversion events) from a server back into the Invoca platform.  Reporting order information through the API allows advertisers to compensate publishers for sales that convert over the phone.

For more information on how to get started with the Conversion Reporting API, visit our Developer Portal and follow the steps outlined there.

Conversion Reporting Email

The Conversion Reporting Email is used if you would like to report conversion events using an email message with an attached CSV formatted file.  This is the simplest way of being able to send in your conversion events since it requires very little in terms of technical development to be able to do this.

Once you have acquired the Conversion Reporting credentials, then you are able to start building your file to send in.  For matching purposes, the only required parameter within the file for Invoca to be able to match the sales transaction with a call will be the “Call Start Time”.

For more detailed information on each Conversion Reporting method, please visit the Invoca Developer’s Portal!

Feedback and Knowledge Base