I am having what is either a strange issue, or a newbie issue.
I am setting up my landers as indicated in Dr_Ngo's guide here: http://charlesngo.com/Voluum-campaign-setup/
The call to action button should have the click URL from Voluum, no problem here.
When I open the lander on my computer and click the call to action button, it takes me to the offer no problem.
However once I upload the lander to the CDN, when I test click the call to action button, the page just goes blank and the url field in my browser gets filled with a bunch of voluum stuff eg http://www.domain.com/index.html?vol.....f047f000-db1........ and the offer does not actually load.
I am using rackspace cdn and namecheap.
Anyone know what is up? I just noticed this issue after spending too much on dead end traffic.
thanks for any help!
It's hard to give any adivce without seeing the coding
I have continued testing and have more data.
When I access the lander from my domain
www.shit.sitename.com/stuff/index.html
the cta button takes me nowhere
when I access the lander from rackspace url
http://pileofnumbers.stuff.stuff.rac...der/index.html
the cta button takes me to the right place
Does this provide any more insight into my problem?
I think you have to use the rackspace URL as lander-url in
Are you using the
You have to pass through the
Again, easier if we see coding.
E.g. show the actual <a href="" ...../> code that you are using in your lander.
The second thing is how you get to it. For this to work at all, you need to load your campaign URL and have
If you just load the lander directly the Voluum click CTA URL will not go anywhere as you are sending clicks to Voluum that it has not tracked before, so it has no idea what to do with them (think of it like teleporting inside a subway station and trying to walk out of the exit with a swipe card having never actually swiped in >> system confused!).
you don't usually use www. on a sub domain if you are using a CNAME to your rackspace url. just http://subdomain.url.com/
Thanks everyone! issue has been solved, I was redirecting with a URL frame and not a CNAME