Hi,
The event post_event_list contains a comma-delimited list of events, which may have a value and/or a unique ID. You should be doing all processing on the post_event_list because it is de-duplicated and has already applied logic to remove duplicate events with the same ID.
When an eVar is set on a hit, event_list contains an instance of that eVar, find your event number in the event_lookup.tsv file. Now use that to build your sql query. e.g.
/* Returning rows containing a custom event */
SELECT event_list
FROM online_users
WHERE CONCAT(',', event_list, ',') LIKE "%,103=%,"
AND hit_source = 1
AND exclude_hit = 0;
Example Output:
+--------------------+
| event_list |
+--------------------+
| ,1,103=17,201, |
| ,1,103=20, |
| ,1,103=10, |
| ,1,103=17,201, |
| ,1,203,103=7,201, |
+--------------------+
5 rows in set (0.01 sec)
you can also use post_evar4 in your query to get results by terms, you will then need to split your event list to make it meaningful for analysis.
Ex. Data Feed contents - overview
Thanks,
Asheesh