Grabbing SiteCat data at source (i.e. on page) and sending on ecommerce sales order? | Community
Skip to main content
A
alexbuck
October 16, 2015
Solved

Grabbing SiteCat data at source (i.e. on page) and sending on ecommerce sales order?

  • October 16, 2015
  • 3 replies
  • 1938 views

Hi

I'm looking for a way to grab specific elements of SiteCat data (browser type, device type etc etc) at the point an order is placed so that I can transmit it on our sales order message and store the data inside our sales order system..

On the face of it, surely it is as simple as extracting the data from the SiteCat variable and populating it into our sales order, but is this the right way to do it? Is this even possible?!

The alternative would be to send all order numbers generated by our website into SiteCat and report that way (by order number), but this won't give us the flexibility we need to be able to provide our customer service team with some user data in their own system.

Does anyone have any thoughts on this?

Thanks in advance,
Alex. 

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 Alexis_Cazes_

Hi Alex,

 

There is a lot of data that is only available after the hit data is sent to Adobe server, after processing. 

I will advise you to set up purchaseID for each purchase, then asked Adobe ClientCare to se up data feed, hourly, daily... that you can feed in your database.

 

You can find all the information about data feed here : http://microsite.omniture.com/t2/help/en_US/sc/clickstream/index.html#Clickstream_Data_Feeds_Help

All the columns that you can export are here : http://microsite.omniture.com/t2/help/en_US/sc/clickstream/index.html#Clickstream_Data_Column_Reference

Make sure to use the column duplicate_hit as this data is not in SC.

 

Best regards.

 

Alexis Cazes

3 replies

Alexis_Cazes_
Alexis_Cazes_Accepted solution
Level 10
October 16, 2015

Hi Alex,

 

There is a lot of data that is only available after the hit data is sent to Adobe server, after processing. 

I will advise you to set up purchaseID for each purchase, then asked Adobe ClientCare to se up data feed, hourly, daily... that you can feed in your database.

 

You can find all the information about data feed here : http://microsite.omniture.com/t2/help/en_US/sc/clickstream/index.html#Clickstream_Data_Feeds_Help

All the columns that you can export are here : http://microsite.omniture.com/t2/help/en_US/sc/clickstream/index.html#Clickstream_Data_Column_Reference

Make sure to use the column duplicate_hit as this data is not in SC.

 

Best regards.

 

Alexis Cazes

A
alexbuckAuthor
October 16, 2015

Hi Alexis

Thanks for your response.

So to clarify, other than the data that is visible using Debugger and in the JS code on the page, nothing else is accessible before it has been transmitted to SC?

I think I'll set up the TransactionID and look at developing our backoffice to accommodate the data. Or at least some sort of interface that links the two data sets.

Thanks, Alex.

Alexis_Cazes_
Alexis_Cazes_
Level 10
October 16, 2015

Hi Alex,

 

The transactionID in SC implementation is used to link offline data to SC. In you case I think you should use purchaseID. Data that is not visible in the Debugger is only available once  processed. (i.e: browser, keyword, geolocalisation ...)

Data feed can provide you the data sent to/received by the Adobe servers and the processed data used in SC.

For example pagename column is for the value received by the adobe server and post_pagename is the value received.

For eVars it allow you to see when the eVar was set and when it persisted over time, when there is only a value for post_eVar then it means that it is a persisting value.

Best regards.

 

Alexis Cazes

Terms & ConditionsAccessibility statement

Loading footer...