Skip to main content
Use the campaign’s 2. Events tab to define conversions. Start with Simple for one paid action. Use Advanced for several stages or different settings for selected traffic.

​
Track one conversion

Use this setup for a new campaign with one conversion event.
Saving an existing setup in Simple keeps only Event ID 1. It removes the other events and conditional rules. Keep Advanced to retain them.
  1. Open the campaign’s 2. Events tab.
  2. Choose Simple. Event ID 1 counts as a conversion and uses the incoming payout as revenue.
  3. Leave Event cost as No event cost, unless each conversion creates an additional expense.
  4. Save the campaign.
  5. Copy its Incoming event URL and configure your site or affiliate network to send the event.
For one test event with payout=15, expect Event 1 = 1, Conversions = 1, and Revenue = USD 15. To send the conversion to another platform, configure Outgoing postback.

​
Choose a useful event structure

Use Advanced when a campaign has several stages, such as a submitted lead and an approved lead. A campaign can track Event IDs 1 through 10. For a campaign that pays only for approved leads, use: If 40 leads are submitted, 12 approved, and 8 rejected, expect 12 conversions. At USD 15 per approval, revenue is USD 180. Counting both submissions and approvals would produce 52 conversions.

​
Configure the campaign

  1. In 2. Events, choose Advanced.
  2. In Defaults, add the events and enter an Event name for each.
  3. Set Count as conversion for the stages you want to include in conversion totals.
  4. Choose Revenue and Event cost. For the example, Event 2 uses From incoming event and No event cost.
  5. Enable Outgoing postback only for events you want to send to another platform.
  6. Save the campaign.
  7. Copy each Incoming event URL to the sending system and set its trigger.
The sending system identifies the event by its numeric idx, not its name. Send an approval with idx=2&payout=15. See incoming events for the complete URL and transaction ID.

​
Verify the business result

For the lead example, test a submission and an approval for one new tracked visit:
  1. Send Event 1 with a transaction ID for the lead.
  2. Send Event 2 with the same transaction ID and payout=15.
  3. Find both records in Events.
  4. Open the campaign report for the original visit date.
Expect Event 1 = 1, Event 2 = 1, Conversions = 1, and Revenue = USD 15. If the event appears but conversions do not increase, check Count as conversion. For an incorrect amount, check revenue and cost.

​
Use a rule when the same event needs different treatment

For example, use a fixed USD 18 revenue for approved leads from one offer and the incoming payout for other offers. Add a rule for that offer, then set its event revenue. Place specific rules first. The first enabled rule that matches supplies the event settings. Defaults applies when no rule matches. Include every event you need in each rule. Click Add missing to copy missing events from Defaults, then edit the exceptions.
Use Visitor … fields for the original visit. Use Event request IP, Event request User-Agent, and Event request referrer for the system that sends the event.Use AND for another required condition. Use OR for an alternative group. All conditions in at least one group must match.Visitor is bot includes detected bots and non-browser clients. A blank Visitor bot category does not confirm that the visitor is human.

​
Treat statuses as separate events

Use separate Event IDs for approval and rejection. Count the approved stage if that is your desired result. A later rejection does not subtract an earlier conversion or its revenue.