Home > Tracking Campaigns > FunnelFlux

Tracking and Sorting FunnelFlux Visitors Between Sessions (9)


04-03-2017 07:39 AM #1 weekendwarrior (Member)
Tracking and Sorting FunnelFlux Visitors Between Sessions

I have a campaign where I need to sort visitors by their previous visits to offers.

I have been trying to use the method described in this post to get this done: https://support.funnelflux.com/99384...-on-User-Input

So far the visitors are not getting sorted - meaning it's as if they aren't tagged/ don't have a tracking token attached to them.

Here is what I do:
1. Have visitor click on traffic link with tracking token Invincible=PLC1
2. Passes through a PHP accumulated vars update as described in the post that also adds the Invincible=PLC1 (this is how I originally wanted to do it - solely via php - I added the traffic link variable to see if that would help)
3. Later visits a traffic link which has condition filters set up immediately after they enter it to look for Invincible=PLC1, and divert based on the value of "Invincible"

How can I assure inter-visit tracking via these variables?

This is the screencast I submitted to support showing the funnel:

Thanks.


04-08-2017 06:58 AM #2 vitavee ()

I just had a look at your screencast and there are 2 reasons why it is not working.

In your PHP nodes, you are setting data in the accumulated URL params.
In your condition tests, you are checking values from the tracking fields.

They are 2 different things. Accumulated URL params are not stored into the database.
Here is more information of what they are:
http://support.funnelflux.com/076738...ted-URL-Params

Instead of using the accumulateParam() method, you would need to use the updateTrackingFields() method.
That way your conditions testing the tracking field values would get the values you set in your PHP nodes.

HOWEVER, from what I understand, your setup will not work even if you use the right setting method.

This is because both accumulated URL params and tracking fields are valid for ONE single visit. If a visitor comes back later through another link, he will get a new set of accumulated URL params and tracking fields.

Those 2 sets of data are attached to an entrance. They cannot be shared between different funnel entrances.

In your case, you want to tag those visitors with some conditional data that can be used later, when they come again through another tracking link, if I am not mistaken.

The easiest way to do this would be by saving a cookie in your PHP nodes, where you currently have the accumulateParam() calls, because those cookies would be saved on the visitors' devices, and be accessible in their future visits.

And in place of your conditions, you would use other PHP nodes that would test for those cookies.

Here is a post where I explained how to use PHP nodes to route the traffic to different paths:

https://stmforum.com/forum/showthrea...-Here-s-How-To!


10-24-2017 09:29 AM #3 weekendwarrior (Member)

Hi Vitavee,

This is a subject I have come back to and am trying to refine.

Since you last responded to this, and perhaps with tags and version 1.6, is there a better approach to this?

I understand that TAGs will soon be reported on in the Stats and they will also work between sessions?


10-24-2017 11:10 AM #4 vitavee ()

Hi D.

Yes, TAGs are definitely well suited for this. It makes it much simpler and also works between sessions and across different devices.

You can't drilldown into TAGs yet, but this will come soon.


10-24-2017 02:37 PM #5 weekendwarrior (Member)

Excellent, that's great to know. TAGs are a gamechanger for our funnels with what they can do then. Already solved some problems we had with redirecting traffic.

In the mean time, before we can get drilldowns with tags how can I tackle this just to get drilldown data from a session?

I'm using this post you made here to make use of Tracking Fields: https://support.funnelflux.com/99384...-on-User-Input

Example:
1. Someone arrives in funnel
2. He does something
3. I set a TrackingField update via PHP node to save his choice
4. I'd like to see this in stats

So far, this doesn't seem to be working because I'm not seeing this TrackingField info in the Stats Drilldowns - it says there is nothing there.

This is the PHP Code - is it something I'm doing wrong there? I select URL Tracking Field in stats and it comes up blank.

<?php

include 'PHPNodeHelpers.php';

// Set TrackingField Here
PHPNodeHelpers::updateTrackingFields([
'Outcome' => 'Outcome B'
]);

?>


10-25-2017 08:01 AM #6 vitavee ()

The tracking field name is case sensitive there.

Is it defined as 'Outcome' with an uppercase in your traffic source?


10-25-2017 10:20 AM #7 weekendwarrior (Member)

Yes, it is uppercase on first letter. So exactly the same.

I've set the Traffic Source incoming link to Outcome=None, and now all traffic is showing up in Stats as None. However, they are all passing through that PHP Node.


10-25-2017 12:42 PM #8 vitavee ()

I just tested it with your PHP code above to see if I would have the same issue but it's working well on my end.

Here is my setup, so you can check if you made a mistake somewhere.

My test funnel looks like this:

Click image for larger version. 

Name:	2017-10-25_16h35_23.png 
Views:	18 
Size:	22.3 KB 
ID:	17337

I've setup this test traffic source:

Click image for larger version. 

Name:	2017-10-25_16h37_13.png 
Views:	15 
Size:	11.4 KB 
ID:	17338

When I get my tracking url, it looks like that:

domain.com?flux_fts=trackingcode&flux_cost=0&Outco me=None

After I reach lander 1, I see this in my stats:

Click image for larger version. 

Name:	2017-10-25_16h41_01.png 
Views:	16 
Size:	9.6 KB 
ID:	17340

And after I click action 1 and pass through the PHP node, I see this in my stats:

Click image for larger version. 

Name:	2017-10-25_16h41_44.png 
Views:	15 
Size:	9.7 KB 
ID:	17341

If your setup is similar, best would be to contact the support so they can have a deeper look.


10-25-2017 01:36 PM #9 weekendwarrior (Member)

Hi Vitavee,

OK, thanks for testing the PHP code to make sure that is working. I will set up your exact config on our install to check that it works like yours and talk to Anthony about it.

Our configuration isn't identical, it has more steps in it - so I'm posting an image of it here in case you see something that wouldn't work.

This is how it is different - before hitting another lander after the PHP Node they go through several other steps:
1. A Tag
2. A rotator
3. Another PHP Node (same PHP code, different TrackingField set).
4. Then they arrive at another Lander

Click image for larger version. 

Name:	PHP-NODE-Setup.png 
Views:	19 
Size:	165.6 KB 
ID:	17344

UPDATE: I FOUND THE ISSUE. We had TWO PHP Nodes updating different tracking fields (cod economization) - one after the other. This was causing an issue. ALSO I moved the Tag to the front, then have one PHP Node now setting both tracking fields. For whatever reason this is what was needed to make it work.


Home > Tracking Campaigns > FunnelFlux