InveoStore.com

[Fred]

Hello,

I am running MSU 1.1 on OSC. The OSC framework has been quite modified, but no new variable has been introduced so far... until now. And that's the point of this topic. What I need is to track some incoming visits sent through an "adserver". The adserver team would format URLs to contain the "origin" and the "landing page", and our system would:

1) Detect the "origin" and keep it in session (for tracking purpose)
2) Go to the landing page
3) And if possible, I would like to get SEO benefits from these incoming links

So my initial idea (idea A) was to give a URL (example: [domain.com]/catalog/p-2345.html?origin=x) that would be 301-redirected to the [product 2345 page] through .htaccess, but rewritten to include the "origin" info... which would be dealt with and added in session by application_top in the landing page.

Do you think this would really mean any SEO advantage (i.e. link to final page), compared to let's say "idea B" - an intermediate "non-OSC" PHP page that would do the job (detect the origin, put it in session and soft redirect to the real landing page)...?

In any case (A or B), please advise on how I should handle that on the MSU-side.
Thank you.