Discrepancy in last touch channel data rows between data warehouse and workspace

[Veron_DaiIT]

Hello,

I noticed that the data we're pulling form data warehouse consists more last touch channel detail rows rather than the ones in the workspace.

For context, data warehouse pull is using an SFTP. I already checked all the segements, filters, range of dates, and also the database that we're pulling.

Could there be any more causes to trouble shoot? I would really appreciate any advice on how to understand or fix these differences.

Thank you very much for your help.

[Jennifer_Dungan]

What metric are you using in regards to your "Last Touch Channel"...

Data Warehouse does NOT de-duplicate values... so if you are taking the flat, non-deduped data from your data warehouse, and adding the values, you will always get inflated stats due to the nature of how the information is presented.

Let's look at a few simple examples:

Visit 1 (single channel - search)

• (Google Search)
• Page 1
  • Marketing Channel explicitly set to "search"
  • Marketing Channel Instance triggered
• Page 2
  • Marketing Channel retains value "search"
  • Marketing Channel Instance is not triggered, since the channel was not set in this call
• Page 3 
  • Marketing Channel retains value "search"
  • Marketing Channel Instance is not triggered, since the channel was not set in this call

Visit 2 (Multiple Channels)

• (Google Search)
• Page 4
  • Marketing Channel explicitly set to "search"
  • Marketing Channel Instance triggered
• Page 5
  • Marketing Channel retains value "search"
  • Marketing Channel Instance is not triggered, since the channel was not set in this call
• (User checks their social feed, clicks on a link)
• Page 6
  • Marketing Channel explicitly set to "social network"
  • Marketing Channel Instance triggered
• Page 7
  • Marketing Channel retains value "social network"
  • Marketing Channel Instance is not triggered, since the channel was not set in this call
• (User gets a Marketing Email, and clicks on a link)
• Page 8
  • Marketing Channel explicitly set to "email"
  • Marketing Channel Instance triggered
• Page 9
  • Marketing Channel retains value "email"
  • Marketing Channel Instance is not triggered, since the channel was not set in this call

Now, let's look at this how Adobe Workspace would present the info:

		Marketing Channel Instance	Page Views	Visits
Marketing Channel		4	9	2
	search	2	5	2
	social network	1	2	1
	email	1	2	1

Now, let's look at how the same information is going to come out in Data Warehouse:

Marketing Channel	Page	Marketing Channel Instance	Page Views	Visits
search	Page 1	1	1	1
search	Page 2	0	1	1
search	Page 3	0	1	1
search	Page 4	1	1	1
search	Page 5	0	1	1
social network	Page 6	1	1	1
social network	Page 7	0	1	1
email	Page 8	1	1	1
email	Page 9	0	1	1

As you can see, there is no "total" row, and if you are looking at something like "Visit" which needs de-duplication to be correct, you cannot achieve this with the Data Warehouse export...