Mostly all the traffic sources are passing the data on publisher, website, target, keyword etc. All these details are required for further optimization on campaign level.
These parameters are passed from a traffic source through the campaign link or Impression URL.
Each traffic source offers a custom list of tokens to pass the data.
To catch all this incoming data it is required to specify the supported tokens in Parameters section of the traffic source settings on the side of BeMob.
External ID and Cost fields are located at the top of custom parameters list.
External ID is used to pass the data on unique click IDs of visit on your ad campaign.
Each time your ad is accessed, the unique ID of click is passed through dedicated token to BeMob.
The click ID is stored on the side of BeMob and then it is used to return the click ID data to the traffic source via postback URL.
Cost placeholder should be completed with the dedicated token and parameter used with your traffic source to pass the traffic cost data.
Cost token allows to use the Auto model in campaign settings as all the cost data will be passed through the dedicated token via Campaign URL or Impression URL.
Besides BeMob is offering the cost tracking via API for the following traffic sources: PropellerAds, MGID, Revcontent, ExoClick.
To enable the integration for your account contact our support team via live chat or at email@example.com.
If your traffic source is not providing the cost token, this field should be empty in traffic source settings. The cost setup should be done on the campaign level.
When setting up the cost tracking manually it is required to select one of the cost models according to your requirements.
Apart from External ID and Cost values you can also receive the essential ad visit data from the traffic source platform for example, publisher, website, target, keyword etc.
To track these characteristics it is required to complete the fields of Query Param, Token and Name.
There 10 available field in each traffic source window.
Query Param should be completed with a parameter related to corresponding token from a traffic source.
When introducing the value in Query Parameter field, it will become prepopulated in Token field but with the curly brackets.
Token part should be completed with a macro of your traffic source to pass the visit data values. Token part should be specified exactly how it is provided on the side of a traffic source.
If your traffic source is not using curly brackets for tokens, you should remove them and specify the token exactly as it is provided on the side of your traffic source.
In cases when the traffic source uses a token that is different from a parameter value, then it is required to introduce the correct value exactly as it is provided on the side of your traffic source.
Name field is required for introducing custom names. You can specify any name you wish in these fields as it only affects how the data will be displayed in the report on custom parameters.
The report on Custom Parameters should be accessed through the campaign or traffic source report:
Other guides you may find helpful:
If you have any questions or need the assistance with the settings, contact our support team through the live chat or at firstname.lastname@example.org