Marketing Attribution Tool FAQ

Our Marketing Attribution Tool is currently in the BETA phase.

However, despite this fact, in most cases it works reliably and will return a valid result.

However, there are currently ways to "crash" the application, which means that it needs to be restarted in a new browser window.

If you have tried everything below and you still can't get the result from our app, email us. We will arrange the exact time of the test and together we will find a solution.

How do I know that an application has "crashed" and needs to be restarted?

  1. It´s easy to see because application "turns gray" and "Disconnected from the server" appears at the bottom of the screen. see picture below.

  2. In this case, we recommend that you reopen the application in a new browser window (or tab).

  3. In the case of a crash, all settings need to be re-run, however, we are already working on a version where the calculation settings can be loaded from the saved file (expected release of this version is in Q2 2019).

The most common issues

  1. The application can remain active for a maximum of one hour (1 hour = current maximum session time). If the application disconnects from the server itself very fast (that is, grayed out) without making any settings, it is very likely that you have problems with Internet connection stability, see point 2.

  2. Poor Internet connection.

    • Yes, such a thing as the stability of the Internet connection is important for the use of our DDA application (due to the need for a continuous connection to the Google Analytics API, which unfortunately ends the session completely even during a short-term interruption).

    • If you are not connected via cable, we recommend using a HotSpot from your mobile operator, which has proven to be very stable.

  3. Missing Implementations custom dimension ClientID in Google Analytics.

    • As you learned at our workshop, or you had read the instructions for implementing custom dimensions, the ClientID implementation is required.

    • This dimension must be available in the Google Analytics account under investigation for the entire analysis period (ie, the entire "Transaction window" and "Lookback window").

  4. Zero transactions in the period under review.

    • If there is no transaction in the entire investigation period ("Transaction window"), the application will not work.

  5. Choosing "Custom channel grouping" without defining it

    • If you want to use custom channel grouping (instructions here), you need to insert the correct Google Sheet configuration ID into the application interface, which must be published as a web page.

    • Also, be sure to set "Level of custom channel grouping depth" correctly.

    • If you can't make a calculation using "Custom Channel Grouping", first try using the channel grouping option "GA default" or "AA default". If this is the case, the problem is somewhere in the configuration sheet settings.

  6. Incorrectly defined ClientID dimension number in the calculation settings.

    • Often, it happens that the numbers of these dimensions are exchanged, for example. You can read how to correctly find out your dimension number in the implementation guide here.

In the calculation from the Marketing Attribution Toole, the total count of transactions (or the sum of sales / goals) does not match the total count of transactions for the same period that I see in Google Analytics.

  • Please perform the ClientID dimension implementation check below.

  • The meaning of this check is to see if all transactions that are generated have a ClientID dimension.

  • Verification is easy with the Google Query Explorer Tool.


Determine the count of transactions with ClientID

  1. Always use "Default GA channel grouping" as part of this check.

  2. As a date range, set a period when you are 100% sure that a custom ClientID dimension is implemented on each day.

  3. Enter ga: transactions as the metric.

  4. As a dimension, enter the number of your dimension where you have ClientID implemented (eg, ga: dimensionXX).

  5. Type ga: transactions> 0 as a filter.

  6. Set "max-results" min. to "Total results found:".

  7. Set "samplingLevel" to HIGHER_PRECISION

  8. Download the TSV file and calculate the sum of the GA transaciton column (eg, in Excel, just drag and drop the file to the open sheet).

  9. Compare the resulting amount of exported transactions to the total count of transactions for the same period in the Google Analytics interface (e.g., acquisition report -> source / medium).

Here we have prepared a preset query where you only need to change the GA profile, time period and custom dimension number

Conclusion from test of implementation of custom dimension ClientID

  • The total count of transactions in the downloaded export is less than the count of transactions for the same period in Google Analytics = a problem with the implementation of the ClientID dimension, which is not always written to each visit where the transaction occurred. Here you need to verify the implementation of ClientID dimension and transaction measurement with your Google Analytics administrator. This problem may indicate more general deficiencies in the measurement of transactions in Google Analytics, which should be captured and resolved.

  • The total count of transactions in the downloaded export is the same (+ - 1%), such as count of transactions for the same period in Google Analytics. In this case, it looks like a problem on our side. Please send us a message and we will arrange a meeting date or call to find a solution to the problem.

If you have tried everything above and you still can't get the result from our app, email us. We will arrange the exact time of the test and find a solution together.

©2019, created with love by Marek & Milan