Connector Improvement: Adobe Analytics lookup data
AnsweredWith Adobe Analytics data feed, it sends lookup files in a zipped file to the target destination. Fivetran doesn't currently ingest these lookup files (i.e. event.tsv) which enables mapping/meaning for event id's in the data feed. Ingesting these lookup files would enable our team to gain more insight and use the Adobe Analytics data more efficiently.
-
Official comment
Hi Lauren,
Thank you for your feature request.
The Fivetran Adobe Analytics Data Feed connector actually already reads the standard lookup files (such as event.tsv, browser.tsv, country.tsv, and others) from each data feed delivery. Rather than syncing them as separate tables, the connector applies the lookup values directly to the hit data during the sync. So numeric IDs in columns like `event_list`, `browser`, `country`, and `os` should be automatically replaced with their human-readable names before being written to your destination.
For example, event IDs in the `event_list` column are resolved to their event names using event.tsv, so you should already see readable values like "Purchase" or "Product View" rather than raw numeric IDs.
Are you not seeing that for your connections?
If you are, could you let me know if this addresses your use case, or if you have a specific need for the raw lookup tables as separate destination tables? That would help us understand whether any additional work is needed here.
Thank you for helping us improve the Adobe Analytics connector!
Luke
-
Hello,
Following up on this, I have opened a ticket with Support team as we're seeing numeric IDs in the post_event_list field rather than the human-readable values. Any idea why that might be happening? We ideally wouldn't need the lookup table and would prefer for the human readable values to be applied directly in our post_event_list field.
-
Hi Lauren,
Thanks for opening a support ticket and granting access. I'm not sure why the IDs are not being replaced by the human-readable mappings. I saw you granted access to the connection. We'll check the data the connector has access to and determine the root cause. Our support team will keep you updated.
Luke
Please sign in to leave a comment.
Comments
3 comments