Promotion tool

BeMob

BeMob is a cloud tracker for traffic sources, offers, and landing pages. You work in the browser, and the click record stays on BeMob’s side. A campaign connects a traffic source to an offer URL, with a lander if you add one, and gives you a link to place in the ads. BeMob’s own click id has to travel with that redirect if a later conversion is going to find the visit. This article explains how to put a Maxlead tracking link in the offer, how to pass that click id, and how the postback returns the conversion.

Maxlead is a CPA performance network that has operated since 2015. BeMob is a separate product. The network does not own it, and BeMob does not pay your approved conversions. Publishers open a Maxlead account, copy a tracking link that already includes their publisher id, and use a tracker when they need the visit labeled before it reaches the advertiser. Whether the conversion is payable is decided on the offer. If a BeMob setting has moved, follow the account you are in rather than a remembered screenshot.

Who it is for

BeMob suits publishers who want a hosted tracker with a clear split between the traffic source, the offer, and the lander. Media buyers use it to keep several sources in one campaign report. Anyone who would rather not run a server uses it for the same reason they use any cloud tracker: the click is stored without a machine to patch. It is not a tool for browsing the advertiser page. That page has a preview on the offer. Traffic does not go there.

The offer on Maxlead still has to allow the country and the source. BeMob can record a visit the offer will not accept. It cannot store that visit as your click if the country is outside the list, because a click is saved only when the country is allowed. A source the rules forbid can come back rejected. Check those lines on the offer before you build the campaign.

Afterward you read both sides. BeMob shows the campaign, the source, the lander, and the offer URL. The dashboard shows clicks, conversions, earnings, EPC, and CVR. Earnings are approved payout only. CVR is approved conversions divided by clicks. EPC is earnings per click. Approved earnings are paid weekly. Pending and rejected conversions are not treated as approved money.

Traffic sources, offers, and landers

Start with the traffic source. That object names the parameters the ad platform sends, including the parameter BeMob should treat as the external id when you later notify the platform of a conversion. Map only the parameters the platform actually sends. A source with empty tokens looks configured and then reports blanks. You can reuse the source across campaigns, which is the point of setting it up once.

The offer is the URL BeMob will redirect to. Create it from the tracking link, not from the preview. If BeMob has an option to append its click id automatically, the parameter it appends has to be a sub ID the network keeps, such as s1. If you append it yourself, you write the same parameter by hand and you do not do both, or you will send two click ids and the postback will not know which one you meant. A lander sits in front of the offer inside the campaign. The lander’s call to action has to go back through BeMob so the click id continues. Direct linking, with no lander, is the cleaner first test.

The campaign picks the traffic source, the offer, and any lander or rule you are ready to measure. The campaign link is what you paste into the ads. Rules that split traffic by country or device are useful after the basic redirect works. A rule that sends part of the traffic to a second offer is a second test, and that offer also has to allow the country and the source. Name the campaign so the report row tells you which test it was.

Pass the click id

Open the offer on Maxlead when your publisher account is allowed to run it. Public offers are available after account approval. Other offers need an approved request. Copy the tracking link. It already has the offer code and pid. Paste it into BeMob’s offer URL and add the sub IDs. Do not drop the query string and rebuild it.

BeMob’s token for its click id is {clickId}, with that capital letter in the middle. Put the token in s1. Put a source label in s2 and a creative label in s3. Maxlead stores s1 through s8. It creates a separate click id of its own, which the postback can return as {click_id}. BeMob does not know that id. BeMob knows {clickId}, and it will look for that value in the postback parameter it calls cid. If s1 is where you placed the token, cid has to be filled with {sub1}.

The external id is the ad platform’s click id, not BeMob’s. You pass it back to the platform with the token BeMob provides for that purpose if you want the platform to see the conversion. You can also copy it into a later sub ID if you want it on the network report. Do not store it in s1 in place of {clickId}. One slot cannot be both keys. Pick s1 for BeMob, and keep it there for the life of the postback.

How the postback returns the conversion

The network sends a postback when a conversion is approved or rejected. Pending conversions do not send one. A global postback covers every offer that does not have its own URL. An offer postback replaces the global URL for that one campaign. Paste BeMob’s postback URL into the matching field. The host is the tracking domain on your BeMob account. Copy it from BeMob rather than guessing the subdomain.

BeMob expects cid for its click id and can take payout for the amount. Set cid to {sub1}. Set payout to {payout}. The payout token is the amount for that conversion, in dollars with two decimals. If you track statuses in BeMob, you can pass {status}, whose values are approved and rejected. Only approved should count as revenue. You may also send {offer} and {sub2} through {sub8} so the campaign report can show the labels you attached. Those tokens are extra. cid is the one that joins the conversion to the click.

The call is a GET, and the URL must start with http or https. Test by opening the campaign link, not by inventing a cid. Activity should list the click, your publisher id, and the three sub IDs. BeMob should list the same visit under the click id it created. After approval, BeMob should show the conversion and the payout the network sent. If the network row is approved and BeMob is empty, cid is pointed at the wrong sub ID, or the postback was left inactive. Repair the URL. Do not rewrite the click id to “make a test conversion.”

Clicks versus approved conversions

BeMob counts the hit on the campaign link. The network counts the hit on the tracking link when the country is allowed. More clicks in BeMob than on the dashboard usually means a lander exit that never fired, a country outside the offer, or an offer URL that is not the tracking link. More clicks on the dashboard than in BeMob is rare and worth checking for a second link in the ads that skips the tracker. Neither gap is a reason to raise the budget.

Decide from EPC and CVR after approvals exist. EPC is approved earnings per click. CVR is approved conversions per click. A conversion that is still pending is not in the publisher reports that count, and it is not in the weekly payout. BeMob can only show what the postback delivered. If the postback has not fired because the advertiser has not approved, the tracker is not late. The decision is unfinished.

Scale the same s2 and s3 you tested. us-native has to remain that source, and headline-a that creative, while the volume grows. A new headline is a new s3. A new source is a new s2 and, if the offer forbids it, it is not a test you should run. Changing labels and bids together makes EPC a number you cannot attribute.

A worked example

Run this only if the offer allows the United States and allows native traffic. If it does not, BeMob will still accept the campaign link, and the network will not treat the traffic as allowed. Stop before you spend.

Create the native platform as a traffic source and map its click id into BeMob’s external id field, using the parameter that platform documents. Create an offer from the tracking link. Set s1 to {clickId}, s2 to us-native, and s3 to headline-a. us-native is the label for this United States native test. headline-a is the label for the first headline. Build a campaign with that source and that offer, and no lander. Use the campaign link in the native ads.

A visitor reaches BeMob. The token in s1 becomes a real click id. s2 stays us-native. s3 stays headline-a. The tracking link receives pid and those three values. The network stores the click, because the country is allowed, and redirects to the advertiser. The postback, global or on this offer, sets cid to {sub1} and payout to {payout}. Add status as {status} if you want approved and rejected visible in BeMob.

On approval, BeMob matches cid to the click and stores the payout from the network. The dashboard should show us-native and headline-a with clicks, approved conversions, EPC, and CVR. If BeMob shows the click and the network does not, the offer URL or the country is wrong. If the network shows an approval and BeMob does not, cid did not carry s1. Leave the ads off until those two rows describe the same visit.

Mistakes

The advertiser preview is not an offer URL. It lets you read the page before you send anyone. It does not carry your publisher id, so BeMob has no conversion to attach and you have no click to be paid on. Put the tracking link in the offer. If you add a lander later, its button still has to arrive at that link through the campaign.

Rewriting the click id is a broken key, even when the rest of the URL looks tidy. {clickId} has to stay spelled the way BeMob replaces it. A lowercase variant you invented, a shortened id, or a sample cid from a help article will not match the visit. Do not put {click_id} in cid. That token is the network’s click id. cid wants {sub1}, the value BeMob wrote into s1. Appending the click id automatically and also typing s1 by hand can produce two parameters. Use one method.

One hour of campaign data is enough to see a redirect and not enough to see a business. Clicks arrive quickly. Approvals often do not. EPC and CVR on a handful of clicks swing when a single conversion lands. Wait for approved conversions on the dashboard, then compare them with BeMob, then decide whether more of the same traffic is justified.

A forbidden country or source will not be saved by a neat external id. us-native is only appropriate when the offer allows the United States and native. Other countries are not stored on the offer. A banned source can be rejected with the click id perfectly intact. Rejection means the rule held. Pause when the offer pauses. BeMob will keep counting campaign hits for as long as the ads call the campaign link.

Start from the homepage

BeMob organizes the click. It does not issue the tracking link. Open a publisher account from the Maxlead homepage, copy the link for an offer that allows your country and your source, and set s1 to {clickId} with labels such as us-native and headline-a. Save the postback with cid set to {sub1} and payout set to {payout}. Send a small test, and scale only after clicks and approved conversions agree. Approved earnings, not the cloud report alone, are what the weekly payout pays.