Descrizione del progetto
INTERNATIONAL DATA:
It is necessary to configure the integration between the online store and the SalesDoubler CPA network according to the technical specification described below.
To simplify the integration, a specialist contact from SalesDoubler will be provided.
Website:
WordPress + WooCommerce
Address:
================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================
Technical Integration Tasks from SalesDoubler:
Information about the principle of operation of the SalesDoubler system and configuration of integration:
1. Webmasters send all traffic to SalesDoubler server at the address
Where:
{AFFILIATE_ID} - the webmaster ID in our system.
2. SalesDoubler server stores all information about each user transition, by rdr-link, assigns him a unique ID and sends it to your site at the address (example):
Where:
{CLICK_ID} is a unique transition identifier in our system.
{AID} - the webmaster ID in our system.
With the addition of mandatory parameters (aff_sub and aff_id) and parameters agreed with the specialist SalesDoubler. You can request that you add the parameters you need (for example, utm tags) to the link. The name of the parameters can be changed according to the wishes of the advertiser.
3. Cookies are used to identify the user’s transition to the site as initiated by the SalesDoubler system.
You need to put on all (!) pages of the site a URL-parameter processor, whose task is to save {CLICK_ID} in the user's browser cookie for the agreed lifetime of the cookie - 30 days (for example, call cookie sd_user).
Cookies should be installed in the user's browser immediately after he/she has accessed the site.
4. To avoid discrepancies in your statistics and the SalesDoubler system, you need to implement the Last Cookie Wins rule.
The principle of last cookie wins implies a configuration in which the conversion is counted only to the paid source, the link from which the last click was made.
For example, the target action is the purchase. The user clicked on our redirect link, but did not make an order, returned after 14 days through another paid source (contextual advertising, for example) and made a purchase. In this case, our cookie must be deleted, payment for the targeted action is made only to the last paid source of traffic.
To implement the Last Cookie Wins rule, you need:
• Create a list of utm_tags or other parameters that users from other paid channels come with (for example, utm_medium=cpc, utm_medium=retargeting, gclid, uid, etc.). These labels should be at the person engaged in advertising (marketer) in your company. You will need to track the addition and removal of these paid sources and change the labels in the list accordingly.
• add to the handler on each (!) page of the site a check for the presence of these parameters in the user's URL. Check only if there is a cookie with {CLICK_ID}.
If you have at least one of these options, delete the cookie with {CLICK_ID} (the one we call sd_user for example).
This applies only to paid traffic sources, organic traffic (transfers from search engines) and direct clicks of cookie values should not be changed.
For example, you can delete the SalesDoubler cookie in this way:
Setcookie ("sd_user", $sub, time() + 2592000, "/");
Setcookie ("sd_user",", time() - 2592000,"/");
5. When performing a targeted action, the user needs to set up a check for the presence of a cookie with {CLICK_ID}. If there is a cookie, you must insert the following code on the page "Thank you for the application" (ie the page to which the visitor is redirected after filling out the application):
Where
{TRANS_ID} - ID of the application left in your system. It should be unique to each conversion. Mandatory parameter. It must be saved and then used to adjust conversion statuses. Format - numbers and/or letters in upper and/or lower case.
The code must be installed directly on the page (not via GTM) and output only once for each target action. When reloading the page, the code should not be re-outputed.
6. After the conversion of the cookie with {CLICK_ID} (the one we called sd_user for example) you do not need to delete. This way, you will pay us for all conversions made during the lifetime of cookies, but only those for which the last paid source was SalesDoubler.
In this scheme, the access to our server will only go if the user who made the targeted action had previously passed through us, and we were the last paid source of traffic. No code will be displayed for all other users.
It is necessary to configure the integration between the online store and the SalesDoubler CPA network according to the technical specification described below.
To simplify the integration, a specialist contact from SalesDoubler will be provided.
Website:
WordPress + WooCommerce
Address:
================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================
Technical Integration Tasks from SalesDoubler:
Information about the principle of operation of the SalesDoubler system and configuration of integration:
1. Webmasters send all traffic to SalesDoubler server at the address
Where:
{AFFILIATE_ID} - the webmaster ID in our system.
2. SalesDoubler server stores all information about each user transition, by rdr-link, assigns him a unique ID and sends it to your site at the address (example):
Where:
{CLICK_ID} is a unique transition identifier in our system.
{AID} - the webmaster ID in our system.
With the addition of mandatory parameters (aff_sub and aff_id) and parameters agreed with the specialist SalesDoubler. You can request that you add the parameters you need (for example, utm tags) to the link. The name of the parameters can be changed according to the wishes of the advertiser.
3. Cookies are used to identify the user’s transition to the site as initiated by the SalesDoubler system.
You need to put on all (!) pages of the site a URL-parameter processor, whose task is to save {CLICK_ID} in the user's browser cookie for the agreed lifetime of the cookie - 30 days (for example, call cookie sd_user).
Cookies should be installed in the user's browser immediately after he/she has accessed the site.
4. To avoid discrepancies in your statistics and the SalesDoubler system, you need to implement the Last Cookie Wins rule.
The principle of last cookie wins implies a configuration in which the conversion is counted only to the paid source, the link from which the last click was made.
For example, the target action is the purchase. The user clicked on our redirect link, but did not make an order, returned after 14 days through another paid source (contextual advertising, for example) and made a purchase. In this case, our cookie must be deleted, payment for the targeted action is made only to the last paid source of traffic.
To implement the Last Cookie Wins rule, you need:
• Create a list of utm_tags or other parameters that users from other paid channels come with (for example, utm_medium=cpc, utm_medium=retargeting, gclid, uid, etc.). These labels should be at the person engaged in advertising (marketer) in your company. You will need to track the addition and removal of these paid sources and change the labels in the list accordingly.
• add to the handler on each (!) page of the site a check for the presence of these parameters in the user's URL. Check only if there is a cookie with {CLICK_ID}.
If you have at least one of these options, delete the cookie with {CLICK_ID} (the one we call sd_user for example).
This applies only to paid traffic sources, organic traffic (transfers from search engines) and direct clicks of cookie values should not be changed.
For example, you can delete the SalesDoubler cookie in this way:
Setcookie ("sd_user", $sub, time() + 2592000, "/");
Setcookie ("sd_user",", time() - 2592000,"/");
5. When performing a targeted action, the user needs to set up a check for the presence of a cookie with {CLICK_ID}. If there is a cookie, you must insert the following code on the page "Thank you for the application" (ie the page to which the visitor is redirected after filling out the application):
Where
{TRANS_ID} - ID of the application left in your system. It should be unique to each conversion. Mandatory parameter. It must be saved and then used to adjust conversion statuses. Format - numbers and/or letters in upper and/or lower case.
The code must be installed directly on the page (not via GTM) and output only once for each target action. When reloading the page, the code should not be re-outputed.
6. After the conversion of the cookie with {CLICK_ID} (the one we called sd_user for example) you do not need to delete. This way, you will pay us for all conversions made during the lifetime of cookies, but only those for which the last paid source was SalesDoubler.
In this scheme, the access to our server will only go if the user who made the targeted action had previously passed through us, and we were the last paid source of traffic. No code will be displayed for all other users.
Sviluppo web Contante, Bonifico bancario, Denaro elettronico
