tying offline conversion data to sessions is artificially extending session length
Our conversions happen offline via phone call. We are pushing events (tracking them as goals) for calls, answered calls, and orders filled (conversions). These are all mapped back to sessions.
So, the session starts on the first page hit, but the sessions length will get extended if our offline conversion data is pushed and mapped to that session.
Any thoughts as to how we could avoid extending those session lengths when associating a conversion event with those sessions at a later time?
Re: tying offline conversion data to sessions is artificially extending session length
by default the session timeout should kick in (depends how you have set this up in GA admin - 30 minutes by default). When you send an additional hit to GA - probably via Measurement protocol you can use the sc parameter to either star or end a session - https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters#sc
Hope it helps.