Home > Technical & Creative Skills > Tracking Campaigns

Cpv lab testing passing target to lp (7)


12-06-2014 08:42 AM #1 t33media (Member)
Cpv lab testing passing target to lp

Question for anyone that can answer, when testing campaign setup with passing target to LP, why am I getting the token showing if I manually input "target.com" in url.
http://domain.com/d/index.php?target...om%7Bdomain%7D

So the landing page I wanted to say "hello walmart.com visitor"
But I am getting "hello walmart.com{target} visitor"

Any thoughts ?


12-09-2014 06:17 AM #2 zeno (Administrator)

I don't understand.

You're putting ?target=walmart.com{domain}

Why would it not then show "hello walmart.com{domain} visitor"?

It's showing you exactly what the value of target is as you have specified in the URL.

If you want tokens to be parsed to their stored values then the tracking system has to do this, it doesn't happen by magic - thus you would need to start with the tracking URL and put ...something=walmart.com... in that, then let the tracker pass the value of "something" to the lander using the {something} token in your configured LP URL.


12-09-2014 06:23 AM #3 qureyoon (AMC Alumnus)

Not enough info.


12-09-2014 06:24 AM #4 t33media (Member)

Zeno,

Thanks for reply, my apologies for not being clearer. So I have a landing page that I am using the option in cpvlab to pass target. I have proper php on landing page. Problem is when I am testing , as in this example the target "walmart.com" is being passed to landing page but the {target} stays on the page. If I use the wildcard and maually inject it does work and {target} does not display


12-09-2014 06:41 AM #5 twinaxe (Senior Moderator)

Right now I am not on my PC to check it.
But as far as I remember CPV Lab you have to delete the {domain} from the "URL Append" fields.
You have to add the token {domain} (you use 50OnRed I suppose) to your tracking link then to have the target dynamically passed.


12-09-2014 10:04 PM #6 zeno (Administrator)

The thing here is, in a live URL i.e. a click from a real user, {target} would never exist as it would be changed to "walmart.com" before the URL is ever handed off to the user.

So, if the {target} parameter is present, either there is something wrong with the configuration, or the click didn't result in parsing of dynamic tokens to real values - e.g. if it wasn't a real click from the traffic source and it was the traffic source that parsed {target}.


12-10-2014 07:14 PM #7 t33media (Member)

So I found that in the parameter field I had keyword, I was using 50onred pops for traffic source, so I over looked the placement which as soon as I used target in the settings, the brackets left and all is good.
Thanks guys I appreciate it.


Home > Technical & Creative Skills > Tracking Campaigns