How to fix googleads.g.doubleclick.net sources and tpc.googlesyndication.com in Google Analytics

On most Google Analytics accounts, our customers see traffic sources that for many professionals may not be clear in understanding and conducting efficient analytics using source/medium sharing. Of course, we are talking about googleads.g.doubleclick.net and tpc.googlesyndication.com.

Our solution

If you want to verify revenue and have more accurate data from advertising campaigns, it’s a good idea to assign these traffic sources to Google paid campaigns (google/cpc). According to the article “References come from the address googleads.g.doubleclick.net or tpc.googlesyndication.com” – this is traffic from the Google Ads campaign and Google Ad Manager.

It is worth noting, however, that the solution to the problem, contained in the article from Google, did not work for our customers. Although auto-tagging was enabled, the above sources in the reports still happened.

Solution? Filters!

Below I would like to present in a few steps how to add the above mentioned sources to “google/cpc”. This is not ideal because Google Analytics will not recognize the exact movement campaign, but only the source and medium. However, this will help minimize negative situations and avoid assigning these transactions to inappropriate sources.

What filters to use?

(graphic version under the text guide)

We change the medium to “cpc”

 

  1. We go to Filters in Google Analytics administration.
  2. We add a new filter with a name, e.g. “googleads.g.doubleclick.net / referral – medium“.
  3. We set the filter type to“Custom”.
  4. Click on “Advanced“:
    1. “BoxA – Extract A”we select“Campaign Source”and paste “googleads.g.doubleclick.net“.
    2. “FieldB – Extract B”we select“Campaign Medium”and paste “referral“.
    3. Output – Constructor” we select “Medium campaign” and paste “cpc“.
    4. Checkboxes ” Requiredbox A“, “Required field B” and ” Replace outputfield” should be selected.
  5. We save the filter.

We repeat the action with the inclusion of “tpc.googlesyndication.com”

 

  1. We go to Filters in Google Analytics administration.
  2. We add a new filter with a name, e.g. “tpc.googlesyndication.com / referral – medium“.
  3. We set the filter type to“Custom”.
  4. Click on “Advanced“:
    1. “BoxA – Extract A”we select“Campaign Source”and paste “tpc.googlesyndication.com“.
    2. “FieldB – Extract B”we select“Campaign Medium”and paste “referral“.
    3. Output – Constructor” we select “Medium campaign” and paste “cpc“.
    4. Checkboxes ” Requiredbox A“, “Required field B” and ” Replace outputfield” should be selected.
  5. We save the filter.

After following the above steps instead of “googleads.g.doubleclick.net/referral” and “tpc.googlesyndication.com/referral” Google Analytics will present in the reports “googleads.g.doubleclick.net / cpc” and “tpc.googlesyndication.com / cpc”, which is not yet a total solution.

 

We change the source to “google”

 

  1. We go to Filters in Google Analytics administration.
  2. We add a new filter with a name, e.g. “googleads.g.doubleclick.net – source“.
  3. We set the filter type to“Custom”.
  4. Click on “Search and replace“:
    1. “Filterbox”is set to“Campaign Source”.
    2. In the“Find the string”box, paste “googleads.g.doubleclick.net“.
    3. In the“Replace “paste “google”box.
    4. We can verify the data after you save the filter.
  5. We save the filter.

 

We repeat the action with the inclusion of “tpc.googlesyndication.com”

 

  1. We go to Filters in Google Analytics administration.
  2. We add a new filter with a name, e.g. “tpc.googlesyndication.com – source“.
  3. We set the filter type to“Custom”.
  4. Click on “Search and replace“:
    1. “Filterbox”is set to“Campaign Source”.
    2. In the“Find the string”box, paste “tpc.googlesyndication.com“.
    3. In the“Replace “paste “google”box.
    4. We can verify the data after you save the filter.
  5. We save the filter.

 

Graphic guide

 

 

 

Referrals from banks and payment intermediaries in Google Analytics – solution

If you use payment gateways in your shop and conversion counting is integrated after the payment process, you may have encountered different banks or payment intermediaries in your Google Analytics reports. This article explains how to resolve the situation so that Google Analytics assigns transactions to the correct traffic sources.

 

List of exclusions of referring sites

The solution will be to use the List of Exclusions options for referring sites. When you add domains from payment gateways, the system will not split the session into two, so that the correct traffic source will remain.

  • Go to administration and select The List of Exclusions of referring sites in tracking notices.

  • Add the domains of payment intermediaries that you follow in the Source (or source/medium) report in turn. You can also use the finished list below based on several online stores of our customers.

List proposal

  • ssl.dotpay.pl
  • secure.przelewy24.pl
  • go.przelewy24.pl
  • pay.bm.pl
  • paypo.pl
  • online.mbank.pl
  • login.ingbank.pl
  • bankmillennium.pl
  • aliorbank.pl
  • m.mbank.pl
  • e-bank.credit-agricole.pl
  • ebank.db-pbc.pl
  • online.t-mobilebankowe.pl
  • citibankonline.pl
  • secure.getinbank.pl
  • secure.ideabank.pl
  • online.eurobank.pl
  • cloud.ideabank.pl
  • m.online.t-mobilebankowe.pl
  • bosbank24.pl
  • sbe.pbsbank.pl
  • secure.payu.com
  • ipko.pl
  • pekao24.pl
  • pekaobiznes24.pl
  • eblik.pl
  • centrum24.pl
  • platnosci.pl
  • inteligo.pl
  • planet.bgzbnpparibas.pl
  • vpos.polcard.com.pl
  • bankmillennium.pl
  • system.aliorbank.pl
  • ca24.credit-agricole.pl
  • login.nestbank.pl
  • login.ingbank.pl
  • bosbank24.pl
  • 3dsecure.mbank.pl
  • cloud.ideabank.pl
  • plusbank24.pl
  • pbn.paybynet.com.pl

This is worth remembering

The above list is not tailored to the individual needs of your online store. This is just a collection of referrals from several of our customers. You may be using a different payment gateway that is not included in the list. In such a situation, the most important thing is to analyze the traffic in your own store and add the appropriate exclusions of the referring sites.

If you work with one of the above websites and there is a link to your store, as a result of the steps presented, the domain will be excluded (and exactly the traffic will be assigned as direct – direct). In this case, the solution will be to appropriately mark the link with UTM values, using the source value, medium, and campaign.

Summarizing

  1. By adding the appropriate Exclusion to the referring site, Google Analytics will not split the session into two separate ones when you return from the payment gateway. The session source is retained.
  2. If traffic comes from a excluded site, the source is assigned direct/none, so it is important that UTMuse manual tagging.