Make sure you have your AdsKeeper account active before creating a campaign on the side of BeMob.
As AdsKeeper is already listed in BeMob templates all the required fields will be completed automatically when this traffic source is selected.
To add AdsKeeper from templates:
If you are an experienced BeMob user or have tracking background, you can replace ‘e=REPLACE’ with valid values provided on the side of AdsKeeper and click Save button to store the traffic source for your future campaign.
However if you are at the stage of getting familiar with BeMob or even tracking in general, we strongly recommend to read this guide till the end.
The traffic source template consists of two sections: Traffic Source Details with postback settings and Parameters.
Setting up a postback between tracker and traffic source is extremely important if you require to pass the conversions data to your traffic source.
The AdsKeeper pre-configured postback on the side of BeMob looks the following way:
http://a.adskeeper.co.uk/postback?e=REPLACE&r={payout}&c={externalId}
{externalId} is BeMob dedicated token which will pass the ID of conversion.
{payout} will forward the amount of revenue received from the conversion.
Always make sure the {externalId} token is available in the postback URL as this token is required to pass the ID of conversion from BeMob to AdsKeeper.
It is required to replace ‘e=REPLACE’ with valid values which are available on the side of AdsKeeper.
For this you should press Add campaign button in the AdsKeeper Dashboard. There you should specify name and type of your campaign, required category and language.
After that it is required to Add custom tracking tag. By default it is {click_id} but this value is arbitrary.
In Conversion sensors section it is required to select NEW GOAL and specify its category. As we want to set postback between AdsKeeper and BeMob, it is required to select POSTBACK and specify event name. In our case it is lead12345.
Also, there you may add the required CPA value.
After all these steps you should Save your settings.
Postback URL for such event type will look the following way:
http://a.adskeeper.co.uk/postback?e=lead12345&r={payout}&c={externalId}
On the side of BeMob Approved status should be selected to pass conversions data to the side of AdsKeeper.
The list of parameters and tokens supported with AdsKeeper are already preconfigured in the template.
These parameters and tokens are required to transfer the additional details on traffic to your report in tracker, e.g. widget IDs, teaser IDs, campaign IDs etc.
If you pass the data on conversions to the AdsKeeper side, make sure that External ID field is completed.
If you wish to receive the cost data automatically from AdsKeeper, it is required to assure that cost token is available in the template.
All the tokens available with traffic source settings will be automatically added at the end of Campaign URL once you select AdsKeeper in campaign settings.
The data will be available in report on Custom parameters and can be used for further optimization and targeting of your campaigns.
Press Save to store the traffic source settings for your future campaign.
After AdsKeeper is added from the templates, the campaign can be created in tracker.
🔎 Get to know Workspaces better
Flow can be selected if you have a preconfigured list of offers and landing pages configured in the rule-based paths.
Built-in Flow should be selected if the endpoint of traffic is an offer link with landing page.
If the traffic is forwarded straight to the offer, it is required to switch off the landing page in Built-in Flow settings.
Select URL if the traffic is forwarded to a single destination URL e.g. your website with no offer and landing page created beforehand.
After your campaign is approved on the side of AdsKeeper, you can start driving traffic to your campaign and track all the data with BeMob.
If you have any questions or need the assistance with the settings, contact our support team through the live chat or at support@bemob.com