Revenue Conduit: Features & Settings

Infusionsoft Functionality: Overview of API Purchase Goals

API Calls are Infusionsoft's way to start, progress, or end Campaign automation based on a signal that gets sent to Infusionsoft from an external service, like Revenue Conduit!

Here's Infusionsoft's Campaign article with Section 3 covering Goal Methods initiated by an Integration like Revenue Conduit.

Revenue Conduit uses rfmcalc as the API call name to designate a successfully paid order. See the image below for an example of this Infusionsoft API call being utilized.

Screenshot_2015-12-04_16.31.06

After an order has been marked as paid in your Shopping Cart Revenue Conduit will:

  1. Calculate all RFM Fields to that contact record
  2. Then send the API signal rfmcalc to Infusionsoft.
  3. Per standard Infusionsoft functionality, any Published campaign that uses the rfmcalc API goal method as an entry point to the campaign will start any and all of those campaigns (these calls will also be run if you're conducting a Historical import with us, so be careful how you use these calls while older customers are being imported).

The same is also true of any API calls that you set up under the Account Creation Automation or Order Automation area of the Settings Page. When an Order or Account is successfully created, any API calls you've set up in these fields will be sent to Infusionsoft as well as any tags set up in those fields (these API calls and tags will also be run if you're conducting a Historical import with us, so be careful how you use these calls while older customers are being imported).

Revenue Conduit has created several additional API calls that you can utilize.
To see the full list of Order Status API calls that you can use, click here.