Conversion tracking setup
To enable conversion tracking without third-party cookies, we use the solute-Click-ID ("soluteclid"). This allows clickouts to be assigned to sales.
The solute-Click-ID must therefore be sent to our tracking server when a conversion takes place. To simplify this process, we offer two small javascript snippets that do the sending of the solute-Click-ID. The use of the two Javascript snippets is of course not mandatory. It is also very easy to create your own solution (more on this below).
Integrate tracking: Javascript
By the offered Javascript users are recognized, who come from the solute network. For these users, the URL of the entry page is stored in the LocalStorage of the browser in order to be able to assign successful sales to the entry page later.
Offer page/entry page
The Landing Page Javascript is inserted on the offer pages. It checks whether a parameter "soluteclid" is contained in the parameters of the initial page URL. If this is the case, the called entry page URL is stored in the browser's LocalStorage. The initial page URL is also sent to solute. This gives us an overview of the number of clickouts that actually arrive at the offer page of your shop. This makes it easier to identify certain clickbots, for example.
<script>
(function soluteLandingTracking(){
if (location.href.indexOf("soluteclid") < 0) return;
localStorage.setItem("soluteclid", (new Date()).getTime()+" "+location.href);
var url = "https://cmodul.solutenetwork.com/landing";
url += "?url=" + encodeURIComponent(location.href);
var req = new XMLHttpRequest();
req.open("GET", url);
req.send();
})();
</script> Order confirmation page
The Conversion Page Javascript is inserted on the order confirmation page - the page that is displayed after a purchase has been made, for example.
A conversion should always be assigned a monetary (net) value (shopping cart amount excluding VAT and shipping costs), as well as an order number (OrderID), so that you have a reference to your own sales records. An optional proportional factor can also be specified. The default value is 1.
<script>
soluteConversionTracking({
VALUE: "123.98",
ORDER_ID: "abc-987",
FACTOR: "1",
});
function soluteConversionTracking(data) {
var ttl = 1000*60*60*24*30;
var a = localStorage.getItem("soluteclid");
if (!a) return;
var b = a.split(" ", 2);
if (parseInt(b[0])+ttl > (new Date()).getTime()) {
var url = "https://cmodul.solutenetwork.com/conversion";
url += "?val=" + encodeURIComponent(data.VALUE);
url += "&oid=" + encodeURIComponent(data.ORDER_ID);
url += "&factor=" + encodeURIComponent(data.FACTOR);
url += "&url=" + encodeURIComponent(b[1]);
var req = new XMLHttpRequest();
req.open("GET", url);
req.send();
} else {
localStorage.removeItem("soluteclid");
}
}
</script> That was already all to activate the new conversion tracking without cookies.
Integrate tracking: HTTP interface
Alternatively, landing and conversion calls can also be transmitted directly via an HTTP GET request. For example from the backend of the shop software. Here, only the URL of the initial page (with parameter "soluteclid") must be transferred.
Offer page/start page
To track the call of the initial page, the URL of the initial page is passed as parameter.
URL: https://cmodul.solutenetwork.com/landing Request: GET Parameter: - url: Die URL der Einstiegsseite. Response: 204 No Content
Example:
GET https://cmodul.solutenetwork.com/landing?url=ESCAPED_URL
Order confirmation page
To track the call of the order confirmation page, the same URL of the initial page is passed again as parameter. The total value of the shopping cart and the order ID are also transferred.
URL: https://cmodul.solutenetwork.com/conversion Request: GET Parameter: - url: Die URL der Einstiegsseite. - val: Der gesamte monetäre Wert des Warenkorbs. - oid: Die Order-ID in Ihrem Shop-System. - factor: Optional. Der Anteil des Clicks am Conversion-Wert. Response: 204 No Content
Example:
GET https://cmodul.solutenetwork.com/conversion?url=ESCAPED_URL&val=ESCAPED_VALUE&oid=ESCAPED_ORDER_ID
FAQ
Why is the complete URL of the starting page passed to the tracker and not just the solute-Click-ID ("soluteclid")?
Besides the well-known tracking by redirects, some providers (e.g. Google) also use parallel tracking. The user hereby is directed directly to the shop page. In these cases, tracking is not done directly via "soluteclid", but additionally via the tracking parameter generated by the respective provider (for example, the "gclid" at Google).
To keep the handling for shops simple and flexible, solute-Clicks always contain a parameter "soluteclid", so that this parameter can be used to detect solute-Clicks. In addition, the URL may contain other click-IDs for parallel tracking. Our tracking backend will automatically sort these out for you. Therefore it needs the complete URL to be able to find the correct tracking ID flexibly.
The URL itself is not used for any further purposes.
Why is the access to the initial page tracked?
The tracking of the entry page returns the information about a successful call of the offer detail page and serves to be able to recognize possible problems, such as the non-accessibility of your website, at an early stage. In addition, the landing page request information can facilitate error analyses and be taken into account in the solute click calculation process. For this purpose, the accessed URL of the landing page including the solute click ID is transmitted to a solute server.
Can I use conversion tracking with Google Tag Manager?
Yes. You have to implement both JavaScript snippets in the GTM, one on the route of landing pages and the other on the route of order confirmation page.
On the order confirmation page, the values for VALUE: "" and ORDER_ID: "" have to be set with the corresponding GTM values, e.g.:
soluteConversionTracking({
VALUE: "{value}",
ORDER_ID: "{order-id}",
{{ FACTOR: "1",}}
{
{ }
);}} 
Sie haben Fragen? Kontaktieren Sie uns!
Unser Technischer Shop Support hilft Ihnen gerne weiter.
Tel: +49 721-98993-60
(Wählen Sie zur direkten Durchwahl im Sprachmenü "1" und anschließend "2" )