CTA view tracking & click tracking
Mar 2, 2017 9:16 AM
We really dislike the delay that your CTA code has. Our main home page has a hero button that doesn’t load with the rest of the content and although we don’t have data to support it, we believe that some users will scroll past the hero before the CTA has loaded depending on ISP speed. The CTAs we use are all just html a href with some bootstrap button styling attached so we really don’t need much of the functionality your CTA modules bring with them.
Do the CTA click links change or can we hard code them?
If we can hard code them, which variables are required? We currently see cta_guid, placement_guid, portal_id, redirect_url, hsutk, canon, utm_referrer as the variables. Do any of these change on every page load? (obviously the referring URLs do, ignore those)
Assuming we’re able to do what we want, how is redirect_url encoded? We thought it might be base64 but that does not seem to be the case. We don’t actually care how it’s encoded IF it is static and doesn’t change from page load to page load between different visitors.