BeMob

This guide connects a BeMob campaign to UluMob traffic. BeMob reads the UluMob click ID from the externalId parameter and returns it in its postback when a conversion happens.

The Tracker setup section at /app/advertiser/tracking lists a ready-made BeMob line with your secret filled in. The macro names below follow BeMob's public documentation; check them in your BeMob account before going live. Note the capital I in externalId.

What goes where

cid and type are accepted aliases of click_id and conv_type, and key carries your postback secret. See Postback setup.

Step 1: create the traffic source in BeMob

1. In BeMob, add a new traffic source for UluMob.
2. Set the external ID parameter name to externalId with the UluMob macro {click_id} as its value.
3. Add custom parameters for other UluMob macros, for example zone with {zone_id}, sub with {subid}, campaign with {campaign_id} and device with {device}.
4. Map the cost parameter to {cost} if you want spend per visit in BeMob. It is filled for popunder, domain redirect and CPC clicks.
5. Paste the UluMob postback URL into the traffic source's postback URL field.

Step 2: create the campaign in BeMob

Create a BeMob campaign with UluMob as the traffic source, and copy the campaign URL with its parameters.

Step 3: add the URL to your UluMob ads

Use the BeMob campaign URL as the Destination URL in each UluMob ad:

https://tracker.example/abcd-1234?externalId={click_id}&zone={zone_id}&sub={subid}

UluMob macro names are lower case. Only the parameter name externalId uses a capital letter, because that is the name BeMob expects.

Step 4: test

1. After the campaign is approved and has had a click, copy that click's external ID from BeMob.
2. In the UluMob panel, paste the postback URL with the real ID into Test a postback and select Test.
3. An ok answer means live postbacks will be accepted. Nothing is recorded or charged during the test.

See Testing postbacks.

Conversion types and repeats

The template sends type=A. To separate events such as installs and purchases, create more types under Conversion types and send each event with its own letter. If you allow repeats on a type, also send a unique transaction ID as txid, using BeMob's transaction ID macro.

Reading results

With the zone and sub parameters in place, BeMob shows conversions per UluMob zone and sub-ID. UluMob reports show the same conversions next to cost. Use either to decide which sources to block. See Source lists and blocking.

Common problems