Adobe Metrics Calculation Raw Data Feed

[Basu212]

Hi,

I am trying to pull below data from Adobe data feed. Can I get some help on the query.

• eVar2 vs eVar2 Instances
• eVar3 vs event12
• eVar4 vs page Views

[SamuelPaulPeter]

All of these can be calculated from the Adobe Analytics raw data feed, but you have to compute the metrics manually because the feed is hit-level data.

Below is how each one works conceptually (and in SQL terms).

1. eVar2 vs eVar2 Instances

• eVar2 → count of distinct eVar2 values (after persistence rules)

• eVar2 Instances → count of hits where eVar2 is populated

Raw feed logic:

-- eVar2 Instances
COUNT(*) WHERE evar2 IS NOT NULL

-- eVar2 (distinct values)
COUNT(DISTINCT evar2)

2. eVar3 vs event12

• event12 is a counter event → count the hits where it fired

• eVar3 vs event12 = break down event12 by eVar3 value

Raw feed logic:

SELECT
evar3,
SUM(CASE WHEN event12 > 0 THEN event12 ELSE 0 END) AS event12_count
FROM data_feed
GROUP BY evar3;

3. eVar4 vs Page Views

• Page Views = hits where hit_type = 'page'

• Break those page hits down by eVar4

Raw feed logic:

SELECT
evar4,
COUNT(*) AS page_views
FROM data_feed
WHERE hit_type = 'page'
GROUP BY evar4;

Adobe Workspace metrics (Instances, Page Views, Events) are derived metrics.
The data feed only gives you raw hits, so you must replicate Adobe’s logic in SQL.

[leocwlau]

on evar instance and event, you may also refer to the event_list column and the event.tsv lookup file in the data feed package. especially if your event is not only a counter but a numeric or currency type.

[Jennifer_Dungan]

Yep, I was about to say "Instance of eVarX" is absolutely available in the event_list. No need to calculate that.

Also, Page Views in Adobe is not an actual event, but it is based on hits that have pagename or page_url value. There is no hit_type according to the documentation (https://experienceleague.adobe.com/en/docs/analytics/export/analytics-data-feed/data-feed-contents/d...) but even if there was, I wouldn't rely on that, since that is not how page views in Adobe are calculated... I wouldn't even use the page_event lookup (where 0 is "standard page view calls") since support literally told me that other hits could still count as page views (I had an issue early in our mobile apps where I set the page name and page url for apps in our processing rules, only to discover that all our custom links also counted as page views.... I had to modify my rule to ensure that the call wasn't an action before setting the value)

[Jennifer_Dungan]

Oh, I should also add, that in raw data, eVars can appear in 4 ways:

In the evarx field (usually this correlates to the instances), or in the post_evarx field (this is the persistent value).

But also, merchandising eVars will appear in product_list and post_product_list (in the products notation), these will also correlate to the proper eVar Instance in your events_list.

Relying solely on the evarx and post_evarx fields could lead to lost data.