Passing UTM Values From Source To Lander To Offer Site Via FunnelFlux (5)

Hi all,

I'm sure this is a simple set up but i've been wrecking my brain with this for a few days.

I have a source driving traffic directly to my landing page with several UTM parameters attached to the url that are filled out dynamically. For instance:

https://www.mydomain.com/?utm_campaign={campaignid}&utm_source={referral}

The lander has links to multiple offers, each of which I would like to pass the above UTM values through to. I have this set up as following:

Offer 1: https://www.offerdomain1.com/?utm_campaign={campaignid}&utm_source={referral}
Offer 2: https://www.offerdomain2.com/?utm_campaign={campaignid}&utm_source={referral}
Offer 3: https://www.offerdomain3.com/?utm_campaign={campaignid}&utm_source={referral}

However when i look in funnelflux, I literally see {campaignid} and {referral}. how do i pass the source values to the offer itself?

Thanks in advance for your help

I'll ask the great @zeno about this - please stay tuned...



Amy

Whenever you use a tracker and set URLs in it, you have to use tokens the tracker recognises and processes.

{campaignid} and {referral} for example are not tokens in FunnelFlux, and even if they were, they would not correspond to the info you had passed to the lander (more likely for campaignid to be an internal code for a campaign, not what you passed in some URL earlier).

The easiest way to deal with this is to modify your traffic source in FunnelFlux and set utm_campaign and utm_source as tracking fields, so the tracker is expecting to capture and store this data.

Then use the FF Javascript tracking on your lander. You should then pass flux_fts in your URL to the lander (funnel + traffic source), as well as the utm parameters. FunnelFlux will then be aware that the traffic source is X, it is expecting to capture data under utm_campaign, utm_source etc., and will see these in the URL > capture and store in the DB for the user.

Then, in your offer URLs in FunnelFlux, use the tracking field tokens to pass this info forward, e.g.

https://www.offerdomain1.com/?utm_campaign={trackingfield-utm_campaign}&utm_source={trackingfield-utm_source}

Hi @zeno,

Thank you so much for your response. A couple of follow up questions here:

1. What if I don't control the header of the page and can't install the funnel flux javascript tracker. Is there an easy work around here. One that comes to mind is basically pulling referral code before taking the user to the lander page and decoding it for all the information. Hoping you might have an easier route.

2. This is a really noob level question but when setting up a new traffic source, I didn't realize tracking fields have to match the URLs exactly. is that true? Would same be said for Tokens?

thanks

1. Do you mean you don't control the lander? Little confused there, as if you didn't control the lander, you wouldn't be able to do much at all i.e. place JS, change CTA links, etc. Are you linking from traffic source > tracker > some page you do not control?

2. Yes, tracking fields must exactly match how you pass them in the URL. These systems are programmatic -- so if you set up "banana" as a tracking field but pass ...&bananana=something... in your tracking URL, it will not log or save any information from this field. Likewise for tokens used within FunnelFlux. E.g. if {visitor-id} is the token that evaluates to a visitor ID, you must use this exactly -- {visitorid}, {visitorsid} and {visitor_id} are all invalid from the tracker's perspective. Unless we have specifically added these for some reason, they won't work -- its a binary situation, the token is either correct or it is not. The same applies for virtually every traffic source, tracking system or affiliate network system.