Keitaro

This guide connects a Keitaro campaign to UluMob traffic. Keitaro stores the UluMob click ID it receives as external_id and sends it back to UluMob in the postback.

The Tracker setup section at /app/advertiser/tracking has a ready-made Keitaro line, filled with your secret. The macro names below follow Keitaro's public documentation; check them in your Keitaro version before going live.

What goes where

In the postback, cid is an accepted alias of click_id, and payout carries Keitaro's {revenue} value. The key parameter authorizes the call with your secret, because a tracker cannot compute a signature per call. See Postback setup.

Step 1: add UluMob as a traffic source

1. In Keitaro, create a new traffic source named UluMob.
2. Add a parameter external_id whose value is the UluMob macro {click_id}.
3. Add further parameters for the UluMob macros you want to report on, for example zone with {zone_id}, sub with {subid}, campaign with {campaign_id} and geo with {geo}.
4. If you track cost in Keitaro, map the cost parameter to {cost}. It is filled for popunder, domain redirect and CPC clicks.
5. Paste the postback URL from the UluMob panel into the traffic source's postback field.

Step 2: build the campaign in Keitaro

Create the Keitaro campaign with UluMob as its source and copy the campaign URL Keitaro generates. Keitaro normally appends the source parameters you defined, so the URL already contains external_id={click_id} and your other macros.

Step 3: use it as the destination URL

Paste the Keitaro campaign URL as the Destination URL of every ad in your UluMob campaign. It should look like this:

https://tracker.example/AbCdEf?external_id={click_id}&zone={zone_id}&sub={subid}

Leave the macros in curly braces. UluMob fills them on each click or open.

Step 4: test

1. After the campaign is approved and has had a click, copy that click's external_id from Keitaro's click log.
2. Paste the postback URL with the real ID into Test a postback in the UluMob panel and select Test.
3. An ok answer means Keitaro's postback will be accepted. Nothing is recorded during the test.

See Testing postbacks.

Several conversion events

Keitaro can send a postback per status, for example lead and sale. Create one UluMob conversion type per event under Conversion types, then use a different type letter in each postback. If a type allows repeats, also send a unique transaction ID as txid, using Keitaro's transaction or sub-ID token, so each conversion is kept apart.

Common problems