Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards

Tracking Code Logic

Avatar

Level 1

How does Adobe Analytics collect tracking codes within URLs?

If there are two tracking codes in one URL, which one does Adobe Analytics collect? According to the data set I'm referring to, it appears to collect the latter tracking code at the end.

E.g. www.abc.co.kr/?csref=dsp:ABC&csref=dsp:DEF

In this case, Adobe Analytics only collects dsp:DEF and not dsp:ABC.

3 Replies

Avatar

Level 3

Hi @SeongHyunPa ,

Adobe Analytics collects tracking codes based on the query string parameter defined in your implementation (commonly cid, cmpid, sc_cid, csref).

If the same parameter appears multiple times in the URL, Adobe Analytics will capture the last occurrence of that parameter by default. So in your example www.abc.co.kr/?csref=dsp:ABC&csref=dsp:DEF ,analytics will only collect dsp:DEF, since it’s the latter instance of csref in the query string.

If you need both values, you’d need a custom implementation in Adobe Launch (e.g., concatenate duplicate parameters into a single eVar before sending the beacon).
Let me know if you need more clarification on custom implementation .

Avatar

Level 4

This is exactly right and according to standards, setting another value to the same variable will override without custom solutions. The same applies to the receiving end, so make sure you can store multiple values so they're, depending on your business case, either seen as a combination and a single value or seen as two separate values, which would require support for a list-type variable.

Avatar

Community Advisor

Hi @SeongHyunPa 

Adobe Analytics will capture tracking codes based on the query parameter you’ve set up (e.g csref). If that parameter appears more than once in a URL, the platform takes the last occurrence, so in your example, only dsp:DEF is stored.

If your use case requires both values, you’d need a custom approach in Launch/implementation (e.g. concatenate multiple parameter values into one eVar, or use a list-var if you want them stored separately).