Custom Parameters

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.
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

External ID and Cost fields are located at the top of custom parameters.

External ID is used to pass the data on unique click IDs from traffic source.
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 tracker and then it is used to return the click ID data to the traffic source via postback URL.
More details on external ID and postback settings for a traffic source can be found in Postback Settings article.

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.

If you 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 - it is required to select one of the cost models according to your requirements. You can find out more details concerning the cost tracking in the dedicated guide.

Custom 1-10

Apart from External ID and Cost values you can also receive the essential data on other parameters of incoming traffic.
There are 10 fields where you can place the corresponding tokens and parameters to track the publisher, website, target, keyword etc.

Query Param should be completed with a parameter related to corresponding token from traffic source. When introducing the value in Query Parameter field, it will become pre-populated in Token field but with the curly brackets.
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 token for passing the data on custom parameter differs, it is required to introduce the correct value.

Token part is required to be completed with a macro of your traffic source to pass the data variables.
It is required to specify the token exactly in the form it is provided on the side of a 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:

Select the required campaign or traffic source.
Press on Report button.
Find the Custom tab or select Custom through the grouping lists.

👍
If you have any questions or need the assistance with the settings, contact our support team through the live chat or at [email protected]