View errors during Ingestion

[bjonesek]

I have an Electron desktop application I have integrated with the Adobe Analytics script, I can see my requests for tracking pages and actions in the network tab being sent with what appears to be the appropriate data collection query parameters.  The network request has a 200 status, however the data doesn't seem to make it to my dashboards. I am assuming there is an error in the ingestion engine somewhere. Is there a way to view the error logs for the ingestion of specific requests? Or another method I can use to debug what might be happening?  I am unable to install a chrome extension within the electron window.

[Jennifer_Dungan · Accepted solution]

Is this a new implementation? Data Processing can take about an hour in Adobe's server, so you won't see any data immediately in your suite.

I've never worked on a desktop app, so my experience is limited.

You mentioned the network tab, do you have a developer network tab available within your app?  You could also try running Charles or Fiddler on your machine as a double check for the network calls...

[bjonesek]

It's not new, I've been working on this implementation for a few weeks.  I had impressions working, and then they randomly stopped after making a few changes to the code.  I couldn't figure out what had changed that would affect the impressions no longer posting.  I have run Fiddler and am able to see the Adobe tunnel so the request is completing. 

I DID finally figure out the problem, it was the `k` data query parameter was being set to "N".  Turns out there was a race condition, the AA script attempts to read the cookie it sets as soon as it writes it, and does a comparison to see if those values match.  Because I am using an electron application I have to send the cookies to an ipc handler so the cookie wasn't immediately available, which meant the writeCookie method was returning false.  Without cookie support, my impressions do not show up.

Curious to know if there is a better way to debug this?  Logs on the ingestion side that would tell me cookies are hard required for the impressions to be accepted? 

[Jennifer_Dungan]

I'm glad you got it sorted out! If you are using a "traditional" implementation, I am not sure there's a better way to debug... (Fiddler is about the best tool I can think of, and it can only see what is sent)

However, if you decide to use WebSDK, you should be able to use AEP Assurance to debug... this should show you what is sent to Adobe, plus a lot of debugging and event logs, and most importantly, you should be able to see the post-processed data (to ensure that the values are actually being set in Adobe).

But, this means learning a whole new tracking methodology... I think we will all get there eventually... it's just a matter of when...  

I've not used WebSDK, but I would assume it should work in Desktop Applications, if traditional tracking is working, I can't see why it shouldn't.

Good luck!