Binom

This guide connects a Binom campaign to UluMob traffic. You pass the UluMob click ID to Binom in a parameter named externalid, and Binom returns it in the postback.

The Tracker setup section at /app/advertiser/tracking lists a ready-made Binom line with your secret already filled in. The macro names below follow Binom's public documentation; confirm them in your Binom installation before going live.

What goes where

cid and type are accepted aliases of click_id and conv_type. The key parameter carries your postback secret. See Postback setup for the full parameter list.

Step 1: create the traffic source in Binom

1. In Binom, add a new traffic source for UluMob.
2. Set the external ID token so that Binom reads the click ID from the URL parameter externalid, with the UluMob value {click_id}.
3. Add tokens for other UluMob macros you want in Binom reports, for example zone with {zone_id}, sub with {subid}, cmp with {campaign_id} and os with {os}.
4. Map the cost token to {cost} if you want Binom to record spend per visit. {cost} is filled for popunder, domain redirect and CPC clicks.
5. Paste the postback URL from the UluMob panel into the traffic source's postback URL field.

Step 2: create the Binom campaign

Create a campaign in Binom with UluMob as the traffic source and copy its campaign URL, including the tokens Binom adds from the traffic source.

Step 3: put the URL in your UluMob ads

Use the Binom campaign URL as the Destination URL of each ad:

https://tracker.example/click.php?key=abc123&externalid={click_id}&zone={zone_id}&sub={subid}

The key in this example belongs to the Binom campaign URL, not to UluMob. Do not put your UluMob postback secret in the destination URL.

Step 4: test

1. Once the UluMob campaign is approved and has received a click, find that click's external ID in Binom.
2. Paste the postback URL with that ID into Test a postback in the UluMob panel and select Test.
3. Check the answer. ok means a live postback would be accepted. The test records nothing.

See Testing postbacks.

Conversion types

The template sends type=A. If you track more than one event, add types under Conversion types in the UluMob panel and send a separate postback per event with its letter. When a type allows repeats, send a unique txid with each conversion, using Binom's transaction ID token.

Using Binom data to block sources

With zone and sub tokens in place, Binom reports show which UluMob zones and sub-IDs convert. Block the ones that do not from a UluMob report row, or collect them in a saved list. See Source lists and blocking.

Common problems