Adobe Analytics CID

Highlighted

Adobe Analytics CID

Hi - We have started using Adobe Analytics and CID as our URL tracker of choice.  I am new to using the CID so please excuse my inexperience.  I've been assigned to determine the channel, source, medium etc. of about 300 leads by only using their CID that we began capturing since August, via a hidden field on our forms.

We still have GA URL tracker fields hidden in all of our forms -- it was wonderful to easily determine campaigns, channels, source, etc.  and easy to report on how many leads came in through the various channels, etc.

And as I mentioned, we have since then added another hidden field to capture CID - this is hell. 

Since I am completely new to CID's are these correct statements?

- that there is no industry 'cheat sheet' to reading a CID because each company can organize them any way they want.

- every value is separated by an underscore.  

- there can be infinite values depending on the set up of a CID

With that, has anyone out there successfully been able to parse CID data from a column in a spreadsheet, (perhaps using an excel program?) and been able to break it out to channel, source and medium?

 

 

 

 

3 REPLIES 3
Highlighted
Level 10 - Community Moderator

Re: Adobe Analytics CID


- that there is no industry 'cheat sheet' to reading a CID because each company can organize them any way they want.


Yes.

 


every value is separated by an underscore.  


No, but you'll know what the delimiter is for your org.

 


- there can be infinite values depending on the set up of a CID

Yes.

 


With that, has anyone out there successfully been able to parse CID data from a column in a spreadsheet, (perhaps using an excel program?) and been able to break it out to channel, source and medium?


Yes, we parse incoming CIDs on the fly from a CSV, using a webhook-compatible service.

 

If you dump all your Activity Logs you can also do it in Excel. Probably want a regular expression plugin for Excel. I personally wouldn't work on it from that angle; if you're already doing a lot of reporting offline, then it's better to process the data using your ETL tool (which almost certainly will be better at shredding a value by regexp while importing).

Highlighted
Level 1

Re: Adobe Analytics CID

CID Parameters are just one example of a parameter you can use to track your marketing activities.   What is unique about Adobe Analytics, is the platform doesn't track utm source, medium or campaign as you might be use too.   A single string value preferred and is much more flexible than restraining to defined utm parameters...   

 

Here are a few articles on how Adobe Classifications and Groupings work (aka SAINT)

https://webanalyticsfordevelopers.com/2013/05/21/saint-classifications/
https://blog.adobe.com/en/publish/2013/05/22/revisiting-a-sitecatalyst-classic-classification-saint-...

 

That said, if you're looking to break this up into hidden form fields, there are a few way to do this with JS.  If you're looking to parse this out, you can do this as Stanford notes, via workflow or ETL process or more simply through an Excel formula.

 

Highlighted
Level 10 - Community Moderator

Re: Adobe Analytics CID


A single string value preferred and is much more flexible than restraining to defined utm parameters... 

Hard disagree there. A single opaque string value isn't preferred by people who want to work with standard encoding & escaping structures, and saying it's flexible is a bit of a gloss... it's just the way the product works, no more, no less!

 

After all, the very reason &- and =-delimited URL search params are standardized — this is actually a quite recent standard, before which it was merely a convention and support wasn't built into any browsers — is that having a giant query string without a standard delimiter & escaping mechanism was clearly primitive.

 

(And in fact GA isn't restricted only to the well-known utm_* params, you're free to use other parameter names and map them to the same purposes and also to create your own additional attached data.)

 


That said, if you're looking to break this up into hidden form fields, there are a few way to do this with JS. 


Infinite ways to encode it, so infinite ways to decode it.  Both sides need to agree on the encoding and escaping mechanism, unlike with standard URLSearchParams.