Share your feedback about the AdWords API! Take our annual survey.

Parallel Tracking FAQ

I append static parameters to the URL on redirect. What options do I have?
If you currently append static parameters while redirecting to the landing page you should enter those in Google Ads in the finalUrl or finalUrlSuffix field. When parallel tracking is enabled, we send the parameters to the landing page when loading it directly in the browser.
I append dynamic parameters to the URL on redirect. What options do I have?

If the dynamic parameter is a unique click identifier, then we suggest you add the Google Click ID by enabling auto-tagging or adding the {gclid} parameter to your URLs. You can then use this value to join different data sets for click measurements. If desired, you can also retrieve and join attributes from Google Ads Click Performance report using our API. See the section on Per-click IDs for more details.

No other dynamic parameters are supported, and you need to switch to using static parameters, as explained in the Landing Page Parameters section.

I set first-party cookies on redirect. What options do I have?

With parallel tracking your cookies will be written to the main browser jar in a third party context. There are no workarounds.

Will my customers know what to update in their Google Ads account?

Most likely not. If you have access to your customer's Google Ads accounts, we recommend you make the URL modifications for them on their behalf with their permission. If this isn't possible, then you need to give them detailed guidance on what changes to make to their Final URL, Tracking URL and Final URL Suffix fields.

If I add or edit the URLs in Google Ads will my ads be paused and re-reviewed?

If you make the change at groups levels (accounts, campaigns, ad group), current ads will continue to deliver but the re-review process is initiated in parallel. Unless the ads fail re-review there is no further change or action needed. If you make edits to the ads themselves, ad delivery will be paused until re-review is complete. In most cases re-review will be completed within a couple of hours, but it could take up to 24 hours. Refer to our Help Center article for more details.

Should I migrate all my accounts at once?

Since this change could affect a lot of accounts, we expect a higher-than usual re-review volume during this migration. We recommend phasing your migration over several weeks to ensure that ad review queues don't get backlogged for a large number of your accounts.

Do I need to update all the tracking template URLs to use HTTPS?

It is recommended that you do this for your client, provided they have granted you access to their account. To help with the migration, Google Ads will always rewrite the first tracking call to HTTPS if it's not entered as such. This will ensure that parallel tracking will work even if you don't update tracking template URLs to HTTPS. See the Redirects section for more details.

Does the Final URL field need to use HTTPS?

No. The final URL can be either HTTP or HTTPS. We urge all advertisers to use HTTPS as it provides a more secure user experience.

What will be the referrer on the advertiser's landing page?

Currently, the landing pages receive google.com (or a country specific domain such as google.co.uk) as the referrer, even when the ad click is routed through trackers issuing server side redirects. This continues to be the case with parallel tracking.

If you are currently using a page-based redirect (for example, JavaScript as opposed to a server side redirect), then the landing page is currently receiving your domain as the referrer. Since parallel tracking doesn't support content execution, any redirect mechanism that uses an on-page method, like a JavaScript redirect won't work in parallel tracking. You need to make changes at your end to support server-based redirects. See the Redirects section for more details.

Does parallel tracking impact site analytics and conversion tracking tags on the landing page?

If you tag URL parameters, or if the analytics provider captures certain URL parameters (e.g. utm_ parameters used with Google Analytics) then you need to ensure continuity for those parameters being sent to the landing page by entering them in Google Ads in the tracking template field, Final URL field or Final URL Suffix field. This is true for any script on the page that processes URL parameters.

Does Parallel Tracking work for all Google ad clicks?

Not at this time. Currently, parallel tracking is only available for Search and Shopping ad clicks from Chrome on Android. We will be supporting more campaign types and browsers in the coming months. Accounts that are opted-in will be automatically enabled for those as well.

Will the Final URL suffix be applied only to clicks from supported campaign types and browsers?

No. Final URL suffix field will apply to all ad clicks independent of parallel tracking.

Does URL Recomposition apply even if I enter a value in Final URL suffix field?

Yes, parameters entered in the tracking template field (following the correct encoding method) and in Final URL suffix fields are both sent to the landing page.

When will Parallel Tracking become mandatory?

Starting October 30, 2018, parallel tracking will be required for all Google Ads accounts.

I have landing page params already in tracking templates. Should I move them to the Final URL suffix field?

We recommend that all landing page parameters be entered in the Final URL suffix field. However, if you choose not to, the URL Recomposition feature will parse the parameters from your tracking template and send it to the landing page provided you have used the encoding rules correctly. Irrespective of the method you choose, please ensure that you specify parameters for the landing page in only one of the fields.

Where can I get additional support?

If you need additional support, please email us at ads-clicktracking-support@google.com.

Enviar comentarios sobre…

¿Necesitas ayuda? Visita nuestra página de asistencia.