Anchor text sitelinks cause errors with CallRails ability to recognize GCLID

I've been noticing inconsistency with my integrations from CallRail to other platforms (zapier, salesforce).

The pattern is users that click sitelinks of which we use anchor text - to kinda bypass having multiple pages.

It has been especially useful to use anchor texted URLs for sitelinks as it helps use get more from our Unbounce pages etc.

See how this screenshot doesn't have gclid as a landing page URL variable?
Also, the gclid is inserted after the anchor (#2).

I've noticed this is a pattern. Anyone else? 

I have tried adding gclid={gclid} to my final URL suffix - but google doesn't use it. I image it's because I have auto-tagging turned on. But, I also don't want to turn that off as it could cause a whole other list of integration issues.

What can I do here?



1 comment
Date Votes
  • Hello Preston. The short answer here is that we are unable to read a parameter in the URL if it appears after a # character, such as those that appear when using anchor points. 


    A fragment is an internal page reference, sometimes called a named anchor. It usually appears at the end of a URL and begins with a hash (#) character followed by an identifier. It refers to a section within a web page. They look like this:

    Query parameters cannot be read after a hash # character. So if a lead clicks a link like this:

    We are not able to read that gclid value (gclid=12345_bWe).

    If you can move the query parameters before the hash # and it doesn’t affect the page that loads, that should allow our tracking code to pick up any query parameters that you want to use.

    Alternately, you will need to configure your Google Ads landing pages (or wherever you are serving links that are stripping query parameters) to point to a page without the fragment or anchor.


Please sign in to leave a comment.

Didn't find what you were looking for?

New post