Expand my Community achievements bar.

Webinar: Adobe Customer Journey Analytics Product Innovations: A Quarterly Overview. Come learn for the Adobe Analytics Product team who will be covering AJO reporting, Graph-based Stitching, guided analysis for CJA, and more!

Marketing Channel Processing Rules: Not Tracking Correctly

Avatar

Level 1

One day last week saw a large increase in traffic from our "Organic Social" Last Touch Channel, jumping from roughly ~1K visits per day to ~10K. When broken down by Tracking code, we can see that it appears that there is some paid Prospecting traffic getting bucketed under this channel, which (according to our Channel Processing Rules) should really be bucketed under "Prospecting" LTC. We have not seen a dip in Prospecting traffic, so it does not appear to be a share shift. Instead it looks like the processing rules are just not correctly capturing this traffic as Prospecting or are somehow double counting it, and instead bucketing it as Organic Social.

Our Processing Rules have 'Prospecting' rule 10th in our list of 33 rules, and we have (3) Organic Social rules that are positioned 28 - 30 (lower than Prospecting).

Our 'Prospecting' processing rule states:
If Any of the following are true:
-Tracking code contains 'Prospecting, Visitation, Consideration',
-Query String Parameter cid contains 'Prospecting, Visitation, Consideration'
Then do the following:
Identify the channel as 'Prospecting'
Set the channels value to 'Tracking Code'

This is one example of a tracking code that is found under the "Organic Social" LTC.
"SRA:Prospecting:FBI:NA:Visitation-XXX-XXX" (XXX are unique campaign code)

Given the logic within our Prospecting channel processing rule, which is listed higher up than Organic Social, shouldn't this be falling into the Prospecting bucket? Do you have any reason why this may be ocurring?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Level 10

Hi @jenna_kosinski 

could it be case-sensitivity issues, so that the rule does not get triggered? e.g., "prospecting"?

Avatar

Level 1

According to Adobe:

 

Any text field that you define, such as query string parameter or lists of values to match against, are evaluated as case-insensitive values.

 

So I wouldn't think that should matter here.