I've followed the below steps for Marketing Channel Processing Rules setup.
Kindly review the below steps.
5. Clicked on Related Links and configured rules for the below URLs as:
PPC - Processing Rules:
Email - Processing Rules:
Display - Processing Rules:
let me explain: given the url
your parameters is eg. „utm_source“ and the value is „google“ (i marked the parameters)
in your rules, you need to check for the „parameters“ (not the values). looking at the pcc-rule you need to change the following:
the same needs to be done with the other rules in a similar way...
i hope that helps
The changes are effective as of the time you save them in Adobe Analytics and will fire for all calls coming into the report suite after that time. The one major drawback is that Marketing Channel Rules are not retroactive like Classification Rules, so any data before the date you activate your new Marketing Channel Rules will not be aligned to your channels. Make sense?
you can use whatever parameter you like! it's just a matter of your implementation.
but: I recommend either stick to the utm-parameters (because a lot of people know them and a lot of 3rd party publishers work with them) or ho with the Adobe "cid" parameter. It's completely up to you what you decide to implement.
Issue was dot (.) added in internel URL filter causing no channels reported under Marketing Channel report.
We have removed the dot (.) from internel URL filter.
Now, we can notice data is flowing now 🙂
Thanks ursulab50161321 for your help.
I wanted to provide some additional clarification about the time it takes for your Marketing Channel Rules to take effect. There are some important caveats you will want to understand around latency and visitor engagement expiration.
Jumping into this thread.
In the rule conditions (example above) are you also still including the 'Matches paid search detection rules' item? (I cannot see the full rule)
- or just relying on the utm_medium to drive the ppc attribution?
regarding your questions:
1) i think you‘re channel classification ist still wrong. see my earlier post about „set channel value to...“
2) „last touch page views“ mean „how many pages have the user seen in total after they matched a specific marketing channel“
this is strange - I assumed it would work...
can you please provide the following information so we can have a closer look at:
- original URL and Referrer you would expect the user to come to your side
- processing rules that might affect the data
- marketing channel classification rules both conditions and "details set to" code...
The following Adobe Analytics parameters has been set in Processing Rules. (refer attached screenshot)
Please review the below setup for Social Networks - Processing Rules
I can second this recommendation by ursboller.
Add to it the ability to do SAINT associations and imagine converting a URL with 10 UTM parameters, to just one! Then be able to report on any Associated hierarchies(UTM like parameter) and even be able to make adjustments post data capture...
Instead of using utm_source, utm_medium and utm_campiagn, is it possible to use d_ Adobe analytics parameter ?
If yes, what is the procedure ?
I believe the URLs will be tagged something like this :
Thanks urs.boller. Great article
We are noticing some numbers in the 'Marketing Channel Overview' report
Please let us know which metrics will be suitable for display, email and ppc campaigns.
At present, we have used Click-Through metrics. (refer screenshot attached)
And what does '300' meant in the Click-Through metrics ? (refer screenshot attached)
Rule order only comes into effect if you have hits that could match multiple processing rules. With your rules, the only way that could happen is if the end user has more than one query string parameter.
i think the steps are ok, but your processing rules might not trigger. you need to change the conditions to identify the utm_medium!
“query string parameter“ „utm_medium“ equals „ppc“ (or “email“/„display“)
and you need to set the channels vlaue to „utm_medium“ (i would even use something else like the full query string or a concatenated value of the parameters...)