Skip to main content

Multiple Events in a Postback

Many offers pay for more than one step: a registration, then a deposit, then a repeat purchase. Rinku records each of these steps as its own conversion on the same click, lets you price them separately, and lets you choose which step counts as the conversion for your reports and optimization.

Conversions and events​

  • Every postback your network sends creates one conversion record attached to the click.
  • A click can therefore have several conversions, one per event (reg, deposit, sale, …).
  • Each record keeps its own event type, payout and time since click.

Example journey on a single click:

StepPostbackResult
User clicks your ad—1 click
User registersevent_type=regConversion #1
User depositsevent_type=depositConversion #2
User makes a purchaseevent_type=saleConversion #3
note

Conversions are counted per event, so one click can add several conversions to your totals.

Setting it up​

1. Enable event type on the offer​

In the offer's Postback Parameters block, enable Event type. The Preview Postback URL now includes an event_type={EVENT_TYPE} parameter. Give this URL to your network and make sure it substitutes the real event name on every call.

https://<your-tracking-domain>/postback?click_id={click_id}&event_type={EVENT_TYPE}&payout={PAYOUT}

2. Set a payout per event (optional)​

Add one pricing rule per event name your network sends, for example:

Event typePayout
reg$1.00
deposit$3.50
sale$10.00

Event names must match exactly what the network sends. If your network sends ftd or dep, create the rule with that exact name. An event that matches no rule falls back to the default payout.

3. Choose which event counts as a conversion​

Set the offer to either:

  • Always: every event counts as a conversion (default).
  • A specific event (for example deposit): only that event counts. Other events are still recorded and stay visible on the click, but they are marked Not counted and do not enter conversions, CR, CPA or the cap.

4. Set a default payout (optional)​

Used when no other rule applies.

How the payout is chosen​

For each postback Rinku checks, in this order:

  1. Payout in the postback: if Payout is enabled on the offer and the postback carries a value, that value is used.
  2. Event payout: the pricing rule whose event type matches the postback.
  3. Default payout of the offer.
  4. $0 if none of the above applies.

With the example above (default $2.50, payout in postback disabled):

PostbackPayout
event_type=reg$1.00
event_type=deposit$3.50
event_type=sale$10.00
event_type=lead (no rule)$2.50
no event_type$2.50

What the counting rule controls​

The event you pick in step 3 drives the metrics that depend on "a conversion":

  • Conversions, CR, CPA, ROI are calculated on counted events only. If only deposit counts, CPA is cost per deposit.
  • Optimization rules use the same numbers, so a rule such as CPA above your target works on deposit economics rather than cheap registrations. See Optimization Rules.
  • Conversion cap counts conversions, not clicks. A click that produces three counted events adds 3 to the cap. An offer capped at 100 where every click yields three counted events is full after 34 clicks.
  • Postback to your traffic source is sent for each counted event, with that event's payout (see Traffic Sources).

The counting rule is set per offer. The same traffic source can feed one campaign that counts deposits and another that counts registrations, and each uses its own offer's rule.

Where you see events​

  • Click details: open a click to see every event on it with event type, payout and time since the click.
  • Conversions list: each event is a separate row with a Conversion or Not counted status.
  • Reports: clicks stay at one per click, while conversions and payouts of all counted events add up, so profit and ROI reflect the whole funnel and not only its first step. Reports can also break conversion count, postback count and revenue down by event type. Postbacks sent without an event type are grouped under a blank label.

Late events​

Reports attribute a conversion to the day of the click, not the day the postback arrived. If a deposit arrives three days after the click, it still counts toward that click's zone and date, so numbers for recent periods keep growing as late events arrive. If your offer has a meaningful deposit lag, wait for it before judging a zone on deposit-based CPA.

Next steps​