A Short History of Processing a Hit

In the article about Modifying Data Server-Side, we gave a brief list of the steps that every bit of data has to go through before your friendly marketer will see it in her reports.

Let’s expand on that and also mention the different points where you can add information or retrieve it.

Let’s start in your realm, the page or app.

On the Page

This is where you primarily enter information into Adobe Analytics. You “capture” data.

How you do that is up to you, of course, and it depends on the environment as well as the goals. To drop a few keywords:

This stage ends when you call the s.t() or s.tl() method and the core Javascript code takes over.

In Transit

The next step is for the core code to call the s.doPlugins callback which allows you to automate things that should happen on every hit.

The data is eventually being sent to “the cloud”. To be exact, it goes to one of the collection servers somewhere in the world.

At this point, you can very easily see what happens, which makes this the perfect spot to debug by looking at the URL (do I have to repeat that I use Charles for that? Or did I mention that before?).

This is where your — the developer’s — involvement with putting data into the system usually stops. But don’t stop reading, because it makes sense for you to know how your marketer can influence & change (and potentially mess up!) data later.

There will also be some points where you can get data out of the system for further use, and your friendly marketer might ask you to do that.

In the Cloud

Once the data arrives on Adobe servers, it goes through a number of processing steps. You might remember this diagram:

[Screenshot]

Data Processing Steps

There is actually more to it.

  1. Collection server resolves any Dynamic Variables
  2. Collection server does an IP-based geo-lookup
  3. Collection server passes data on
  4. System applies Processing Rules
  5. System applies VISTA Rules

At this point the data in the hit has been modified to an extent, but the view is still hit-based, i.e. so far the system hasn’t applied any prior knowlege.

The upcoming “Firehose” feature that allows you to receive raw hit data in realtime sits at this point. In other words: Firehose will give you a stream of hit-level data that has gone through all the steps we have seen so far.

  1. System applies the “Visitor Profile”, which basically means it adds data it collected in the past, like eVar values. The visitor profile is matched based on the “visitor ID“.
  2. System applies Marketing Channel Processing Rules (for the Marketing Channel reports)

So right now the hits have been enriched with data that is tied to the visitor via the visitor ID.

This is the point where data gets split: it goes into Data Warehouse (which means that Data Feeds contain what we have now), plus it is sent into a further processing queue for Adobe Analytics.

  1. System passes data into report servers
  2. Report servers process and store data for easy access in Adobe Analytics
  3. Friendly marketer navigates to a report
  4. System retrieves data
  5. System passes data through SAINT and displays report

The reports that your friendly marketer pulls are like a pre-defined view on aspects of the data that you have sent into the system. They are designed to help her find answers and make decisions.

And there is one more thing that we need to mention, one more thing you can do to help her: you can use the Reporting API to pull data for her, and you can make fancy displays or dashboards for her. The data that you pull out of the Reporting API has gone through all 12 steps.

Don’t forget to use the all new version 1.4 for added goodness.

*phew*, done.

If you are at the EMEA Summit in London in two weeks, you might want to come and see Bret Gundersen and myself at 11.20 on Thursday when we’ll talk about Processing Rules. Bret will also show a slide that’ll sum up a lot of what I wrote above.

Looking forward to seeing you there!

About

German expat living in Switzerland (formerly UK and France). Consultant and member of the Multi-Solutions Group at Adobe, working with the Digital Marketing Suite. Father of 4 girls.

Tagged with: , , , , , , , , , , , , , , , ,
Posted in Principles
7 comments on “A Short History of Processing a Hit
  1. […] in step 6 of my post on processing hits, I mentioned the “Visitor Profile” and didn’t really explain […]

    Like

  2. […] you think about the processing of hits, you can see that there are multiple points that tests could hook into. The simpler tests could […]

    Like

  3. […] might remember the article about the stages of processing that every hit you send goes through. Those stages are identical for mobile apps except for the […]

    Like

  4. […] an “image request”. The request will be recorded on a server farm, pulled apart and processed into […]

    Like

  5. […] Rules or VISTA might change the value after it has been sent. Depending on how eVar15 is configured, and […]

    Like

  6. […] Situation 1 — when someone comes to your site, we want to see referrers. That’s something handled completely in the back-end, on the Adobe servers during processing. […]

    Like

  7. […] hits go through Processing Rules and VISTA, the visitor profile is applied, but that is it. They are pretty much the same data that you sent […]

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 1,398 other followers

%d bloggers like this: