Marketing Channel Processing Rules - Paid Search | Community
Skip to main content
H
HeatherTh2
October 15, 2021
Solved

Marketing Channel Processing Rules - Paid Search

  • October 15, 2021
  • 1 reply
  • 1839 views

Do you guys follow the recommended processing rule for paid search per the AA documentation? https://experienceleague.adobe.com/docs/analytics/components/marketing-channels/c-rules.html?lang=en

 

I am seeing an unusually high amount of traffic without a search referrer from mobile devices, but with my paid search campaign code. I know users can save those URLs and navigate back to them, but the amount of traffic seems too high for that. I'm wondering if there is a known issue with any device or browser that may not pass the search engine referral data and therefore making it fall into the direct channel?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by yuhuisg

    I had probably misread your original post, so got the wrong understanding from it. 😞

    I think mobile browsers are still able to pass referrer information properly. But then, there are 2 kinds of mobile browsers: in-app browsers and standalone browsers. So the referrer information (and cookies etc) stay within each kind of mobile browser, i.e. if the user has opened a web page in an in-app browser, then presses the button to open that page in the standalone browser, it will be as if the user has opened that page directly, i.e. without any referrer.

    Making things complicated: if the user had searched with a search engine app (e.g. Google Search app), then found your ad and opened it in the standalone browser, I don't think the referrer would be set. If so, then it would be tracked as direct too, yet the Entry Page's URL would have your paid search tracking code. (Someone please correct me if I'm wrong on this point about the search engine apps.)

    1 reply

    yuhuisg
    Community Advisor
    yuhuisgCommunity Advisor
    Community Advisor
    October 18, 2021

    Yes, I follow the recommended Marketing Channel processing rules, including for Paid Search.

    Some things to check:

    • Build a table with Marketing Channel dimension and Marketing Channel Instances metric. Are the numbers of "Paid Search" still very high?
      • If the numbers are still high, then breakdown Marketing Channel by device or browser or operating system. Does any device/browser/operating system "stand out"?
    • Have you configured your report suite's Paid Search detection properly?
    • Could your Paid Search tracking code(s) have been used wrongly with URLs in the app?
    H
    HeatherTh2Author
    October 19, 2021

    As I mentioned, I'm seeing the majority of the traffic without a search referrer coming in from mobile, which made me wonder if mobile browsers might be more likely to fail to pass the proper referrer information. 

    yuhuisg
    Community Advisor
    yuhuisgCommunity AdvisorAccepted solution
    Community Advisor
    October 19, 2021

    I had probably misread your original post, so got the wrong understanding from it. 😞

    I think mobile browsers are still able to pass referrer information properly. But then, there are 2 kinds of mobile browsers: in-app browsers and standalone browsers. So the referrer information (and cookies etc) stay within each kind of mobile browser, i.e. if the user has opened a web page in an in-app browser, then presses the button to open that page in the standalone browser, it will be as if the user has opened that page directly, i.e. without any referrer.

    Making things complicated: if the user had searched with a search engine app (e.g. Google Search app), then found your ad and opened it in the standalone browser, I don't think the referrer would be set. If so, then it would be tracked as direct too, yet the Entry Page's URL would have your paid search tracking code. (Someone please correct me if I'm wrong on this point about the search engine apps.)

    Terms & ConditionsAccessibility statement

    Loading footer...