If you enter a URL tracking code when you create your content, it will be embedded in your landing page URL so that you can monitor the behavior of users who click on your content.
.png&blockId=b9bb7e77-1815-44cc-9cc1-1eca3464e019)
You can customize the parameters to suit your needs. You can enter up to 8 parameters, and you cannot enter the same parameter. Also, characters other than English case, numbers, [], and _ are not allowed in parameters.
You can enter a passback macro in the URL parameter to receive the desired information as a passback.
Dable supports the following passback macros.
•
[CAMPAIGN_NAME] : The campaign name is passed.
•
[CAMPAIGN_ID]: A unique ID for each campaign.
•
[CONTENT_NAME]: Content title is passed in.
•
[CONTENT_ID]: A unique ID for each content.
•
[SERVICE_NAME]: The name of the medium is passed.
•
[SERVICE_TYPE]: The category of the medium is passed.
•
[CPC]: The bid price is passed in.
◦
CPC is Base64 encoded value of UTF-8 string
◦
CPC price is always provided in KRW, not the client's local currency.
•
[DEVICE]: Information about what device the user was using, such as desktop, mobile, tablet, etc.
•
[CLICK_ID]: This parameter must be entered when using Server to Server (S2S) conversion tracking. Each time a user clicks on content, relevant information is passed.
How to use S2S (Server to Server) conversion tracking
You can use S2S conversion tracking if you don't want to use Dable scripts or mobile app integration tools. If you are an advertiser looking for S2S integration, please contact your Dable business manager.
When using S2S conversion tracking, be sure to add click_id to the parameters when creating content.
Input format : URL + &click_id=[CLICK_ID]
Adding the [CLICK_ID] parameter will generate a randomized click ID for each click on your content, which will be put into the corresponding macro parameter, allowing you to track data with that value later.
Once you've received the value via the parameter, send a conversion event to Dable Server instead of the conversion event code with that CLICK_ID value and EVENT information in the postback URL for that conversion.
Please change the values corresponding to :click_id and :event in the postback URL as shown below.
(Dable only supports the ‘get’ method, so it won't work with the ‘post’ method).
POSTBACK URL : https://ad-log.dable.io/postback/s2s/:click_id/:event
1.
Fill in :click_id with the value generated by replacing the [CLICK_ID] value from the click of the Dable user. This value is used for internally only. It must be populated with the same value as the [CLICK_ID] value generated at the time the click occurred so that the conversion is linked to the initial click.
2.
:event Fill in the value with the event name that corresponds to the conversion event in the table
ex) click, install
[Example]
https://ad-log.dable.io/postback/s2s/abcdefgh/lead
Types of conversion events supported by Dable
•
registration
•
lead
•
adview
•
inlinkview
•
visit
•
checkout
•
content
•
search
•
cart
•
wishlist
•
payment
•
login
•
install
•
re_install
•
re_engagement
•
app_open
•
purchase
◦
If the conversion event is a ‘purchase’, you should also include ‘price’ in the URL.
◦
[example] https://ad-log.dable.io/postback/s2s/abcdefgh/purchase?value=10000¤cy=KRW
