Home > Tracking Campaigns > FunnelFlux

How would you deal with parked domains and lp's? (6)


11-15-2018 07:34 AM #1 heavyt (Senior Member)
How would you deal with parked domains and lp's?

Say I have 4 lps, and 5 domains, i have the 4 lps on the first domain and park 4 other domains ontop of that domain. I want to park them incase one of the domains gets taken or the dns goes down or it just stops working. It also makes it easier to edit files in ftp and if a domain gets flagged the other 4 aren't. is there any way yo do this because i have actions on these lps and since they are the same files and not on 5 actual domains how would that work?


11-19-2018 10:46 AM #2 zeno (Administrator)

If you're considering the domains of landers, changing these doesn't affect the tracking itself -- if you wanted to change them all within the tracker for some reason, you'd need to manually change the domains in the FunnelFlux lander config, or use some sort of token approach (a bit fiddly but possibly), or use the API to bulk update.

Usually for switching domains the best approach is to use the API to swap out domains -- we don't have a bulk lander edit feature but its relatively easy to do via the API.

Note however that even if the domain the lander is using changes, it won't affect the JS/action links in any way since they would be a different domain from the lander in the first place (well, usually), so are not explicitly connected.

If you're looking to change the tracking domains, which is also relevant in cases where you want to use many tracking domains concurrently e.g. lander.com and track.lander.com, with different campaigns/landers using different tracking domains, the annoying part is having any reliance on cookies, since the initial tracking domain (or JS), action links etc. need to use the same domain else they can't read the initially dropped cookies.

The easy way around this is to adopt an approach using our JS of injecting session IDs into action links -- if you do this then the domain mismatches won't matter and it makes the tracking more robust (e.g. in cases like the FB mobile browser where it blocks third-party cookies by default).

More on that in this guide: http://docs.funnelflux.com/funnelflu...tracking-guide


11-19-2018 01:11 PM #3 heavyt (Senior Member)

Actually I think I solved it in the fact I wasn't using universal links and using the organic ones so it was confusing me.


11-19-2018 01:53 PM #4 zeno (Administrator)

Heya,

Yeah there would be no need to change up those action links, so you can just change the lander domain without worrying.

If you wanted to make this dynamic while still using only the 4 landers, you could use a PHP node and get a little crafty with tokens.

You could either define a field for your traffic source such as "lpdomain" or create this as a buffer field (temporary) -- pro's and cons to both.

If using a traffic source field this info would be stored in the DB so you could check the domain served to users in the reporting. But, you would need to define this field for every traffic source being used and make sure it's being sent with every click, otherwise a redirect would go to an invalid URL. Actually, now that I think about it, you could use a PHP node in the middle to validate/sanitise and only pass in the URL if you want to force it.

Anyway, with a buffer field, you could set this on the fly with a PHP node and make it randomly pick a domain that then gets used by the lander, but what domain is served would not be tracked or visible in any data.

Confused? Welcome to the power of PHP nodes haha. What I mean is something like this:





Then you could use a PHP node like so:





And adjust your landing page to use the token for "lpdomain" in the URL. If using a buffer param it would be {buffer-lpdomain} instead.






The PHP code above is:

Code:
<?php
require_once 'PHPNodeHelpers.php';
$domain = "{trackingfield-lpdomain}";
if( empty($domain) )
{
    $domain[0] = 'domain1.com';
    $domain[1] = 'domain2.com';
    $domain[2] = 'domain3.com';
    $domain[3] = 'domain4.com';
    $number = mt_rand(0,3);
    PHPNodeHelpers::updateTrackingFields([
            'lpdomain' => $domain[$number]
        ]);
}
return 1;
?>
My PHP is a little rusty so I'm not 100% sure it's valid (I can never remember whether to use empty, null, isset etc. for those kinds of things), but hopefully it gets the gist of it across.

You could do something similar but with the PHP node directly generating an accumulated buffer param instead, in which case the lander URL would use the buffer token. The PHP would be similar.


11-19-2018 02:04 PM #5 heavyt (Senior Member)

omg thank you, this helps so much I was gonna go in and just copy the landers lol


11-19-2018 03:23 PM #6 zeno (Administrator)

Quote Originally Posted by heavyt View Post
omg thank you, this helps so much I was gonna go in and just copy the landers lol
No problem. There is a lot you can do with PHP nodes once you figure out there usefulness, especially if you have a developer around who can write what you need (you can do basically anything, access all tracker tokens/info, and even save data locally to cache files if needed).

By the way - point of clarification: with action links, the organic params are just fallback parameters. If you have ...?flux_action=1&flux_f=xxxx&flux_fn=xxxxx, these extra parameters do not override the intended destination of a click.

So if you have the same lander used in many funnels, the presence of a hard-coded flux_f is not an issue. These parameters only get used when the user's identity is unknown and the generic, universal action link would result in a 404 -- e.g. if someone came to your lander directly and you had no JS on it, so to FunnelFlux their click was the first time the user interacted with the system.

FunnelFlux has a lot of hierarchy like this when it comes to URLs, redirect links, the JS, action links, etc. -- as much as possible it avoids overriding what is already known and uses the highest ranking value of a parameter.


Home > Tracking Campaigns > FunnelFlux