Expand my Community achievements bar.

Join us for our next community Coffee Break on February 28th! Four of our Analytics Champions will be joining us to discuss Summit tips, best practices, and any of your Analytics questions!
SOLVED

Number of lines in my datawarehouse export is not aligned with the workspace figures

Avatar

Level 3

Hi, 
I have some scheduled exports defined to run each morning at 2AM about data of the previous day.
I noticed that sometimes the export is incomplete and sometimes it's ok.

To validate this, I scheduled (at the same time as the DWH export) a report to be sent  on the segment containing the data to extract.
So without any modification, the result can change by day.

EX : 
report send on the 14/10 (so about data of the previous day)

robinl39529461_0-1699431907051.png

Segment definition:

robinl39529461_1-1699432030333.png

robinl39529461_2-1699432081529.png

 

The export about this day:

robinl39529461_3-1699432172683.png

and the number of lines in the file:

robinl39529461_4-1699432236161.png

 

So some day it's ok and some day not ....

Did you already see this kind of behavior ?

 

Do you know if there is option in DWH to help by sending automatically info of the number of lines in the file ?

 

Thanks

 

Robin

1 Accepted Solution

Avatar

Correct answer by
Level 3

I think I found it.

With only using this option in the export:

robinl39529461_0-1699534955215.png

So without the digital signature file, the info looks OK :

robinl39529461_1-1699536691579.png

 

And with this now it seems ok:

robinl39529461_2-1699536752807.png

 

and it's aligned with the quantities of the file (without the header):

robinl39529461_3-1699536841125.png

 

So it seems OK

 

Robin

View solution in original post

7 Replies

Avatar

Community Advisor

With Data Warehouse export, this is a flattened table.. if you have anything like a list variable or a product or something that results in needing multiple rows to represent the data, then that will cause additional rows to appear... Even something like having Visit or Unique Visitor metrics in the Data Warehouse export, where maybe the user updated their browser, or changed something within the visit, each variant will show on a different line...

 

Your Workspace just has one consolidated, de-duplicated total.... your Data Warehouse is not de-duplicated, and is showing a lot more columns of data increasing the change of divergence...

 

Now, on the opposite side of things, you are using the Occurrences metric in Workspace... this metric isn't supported in Data Warehouse (unless that's added in the new UI which I don't have yet...)

 

But on the surface, these don't seem like comparable reports....

Avatar

Level 3

Thanks Jennifer for your answer.

In my export I don't request any metric to be present and one dimension used ensures unicity of the data, so no issue (theorically) with duplication.
That's the reason why I used occurences in my report.

But as said, majority of time, it's aligned but in some cases there is a huge difference between the report and the export.

I think it will be so much easier it here is any option in DWH to receive a report on the export with the number of lines.

 

I try play with the following options in the new interface:

robinl39529461_1-1699528186173.png

 

As result I have this:

robinl39529461_2-1699528231430.png

 

with details:

robinl39529461_3-1699528265860.png

 

robinl39529461_4-1699528315518.png

 



but the number of lines announced in not in line with the file itself: 

robinl39529461_0-1699528121947.png

 

So I'm a bit lost ...

 

Robin

 

Avatar

Correct answer by
Level 3

I think I found it.

With only using this option in the export:

robinl39529461_0-1699534955215.png

So without the digital signature file, the info looks OK :

robinl39529461_1-1699536691579.png

 

And with this now it seems ok:

robinl39529461_2-1699536752807.png

 

and it's aligned with the quantities of the file (without the header):

robinl39529461_3-1699536841125.png

 

So it seems OK

 

Robin

Avatar

Community Advisor

Excellent, I'm glad you found a solution!


For the record, I don't have the new IU yet, so I don't have those options... good to know there is some cool functionality coming soon.

Avatar

Level 2

Hi Robinl

 

One thing to notice that, The Excluded bucket will not be working in Data Whareshouse. So, Please try to create the segment with out exclude and try.

Hi,

thank for your feedback.
When you said 'will not be working', do you mean that the segment is not compatible with DWH?
Because this segment is available for DWH export:

robinl39529461_1-1699524733953.png

and my exports run (but sometimes with inconsistance result)

 

Excluding the session make it not compatible with DWH but I found a workaround:

in place of excluding the session directly, I exclude all hits of the session I want to exclude:

robinl39529461_0-1699524706941.png

 

I compare result in the workspace inteface by creating 2 segments:
- excluding a visit

- excluding all hits of a visit

And it gives the same result.

 

Robin

Avatar

Community Advisor

Yeah, I would expect if any part didn't work with Data Warehouse, the compatibility would reflect that...  this looks fine to me.