Data Discrepancy in Adobe. | Community
Skip to main content
N
nirmalr86267654
July 11, 2019
Solved

Data Discrepancy in Adobe.

  • July 11, 2019
  • 3 replies
  • 1933 views

Hi All,

There is data discrepancy in Last touch channel report. I'm not sure why 80% of the orders have been attributed to Referring Domains. further digging into it  and found that Unitll payment gateway page the user seems to have last clicked channel for e.g. PPC but once the user goes through the payment and returns back to confirmation page. User is referred as referring domain.

Should I change the processing rules or add payment gateway pages and confirmation page in the internal URL'S

It would be great if shed light on this or any suggestions to resolve this issue?

Regards

NR

    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 kumararajak

    Dear Nirmal,

    Adding to ashokkumarm​

    s.linkInternalFilters: The linkInternalFilters variable within the s_code.js file is used in exit link tracking. If s.trackExternalLinks is set to true, it is used to determine if a specific link a visitor clicked is internal to your organization's site or not. Clicked links that match a value in s.linkInternalFilters are ignored. And, links that don't match any values are sent to SiteCatalyst as an exit link.

    Internal URL Filters: The Internal URL filters within the Admin Console are used in Traffic Sources reports, such as the Referring Domain report. Every s.t() request checks to see if the referring URL (contained within the referrer variable) matches any of the rules. Referring URLs that match any of these rules are excluded from all Traffic Sources reports, while referring URLs that do not are included.

    it recommended that s.linkInternalFilters and Internal URL filters match each other. However, the two operate independently and serve separate functions.

    Regards,

    Kumararaja K

    3 replies

    ashokkumarm
    ashokkumarm
    Level 4
    July 18, 2019

    Hi NR,

    Yes. You need to map the payment gateway domain in Internal URL List. Then it is not consider as referring domain.

    Whenever domain changes happen in customer journey, processing rule consider non internal URL as Referring Domain and it replace the actual channel as Referring Domain. After updating Internal URL list with payment gateway, Actual channel has carry forwarded to Check out page.

    Regards

    Ashok

      kumararajak
      kumararajakAccepted solution
      Level 5
      July 18, 2019

      Dear Nirmal,

      Adding to ashokkumarm​

      s.linkInternalFilters: The linkInternalFilters variable within the s_code.js file is used in exit link tracking. If s.trackExternalLinks is set to true, it is used to determine if a specific link a visitor clicked is internal to your organization's site or not. Clicked links that match a value in s.linkInternalFilters are ignored. And, links that don't match any values are sent to SiteCatalyst as an exit link.

      Internal URL Filters: The Internal URL filters within the Admin Console are used in Traffic Sources reports, such as the Referring Domain report. Every s.t() request checks to see if the referring URL (contained within the referrer variable) matches any of the rules. Referring URLs that match any of these rules are excluded from all Traffic Sources reports, while referring URLs that do not are included.

      it recommended that s.linkInternalFilters and Internal URL filters match each other. However, the two operate independently and serve separate functions.

      Regards,

      Kumararaja K

        N
        nirmalr86267654Author
        July 22, 2019

        Thanks for getting back to me on this. Will try to get hold it now.

        Terms & ConditionsAccessibility statement

        Loading footer...