NeoMedia Technologies, Inc (NEOM)

[bleedingedge]

It was my understanding that the NeoReader was going to log the click (i.e. send information that the click/resolution occurred) but that it will still "direct connect" an direct encoded code. They may have implemented this as a pass through at the NEOM server; i.e. the NeoReader calls the NEOM server, logs the "click" and passes through the destination/embedded URL.

In a true redirect (the former qode system and currently the NeoReader + routing server), when the NEOM server is called, it accesses a data base that, based on rules such as language preference, gender, age, location, time-of-day, etc., chooses the correct URL from the data base to redirect the query to and link the phone's browser to the content.

On the direct encoding, if elementus was looking at a transaction log from his phone, it could look like two "calls" from the browser (one to the logging server/system and the other to the embedded/encoded target URL) or, if NEOM is using the pass-thru methodology at the server, it would look like a redirect to his phone and web logs. Since NEOM does not have the target URL stored in any data base, it can not be a true indirect method.

I'm not sure that this helps or is totally clear; a flow chart would better depict the situation.