Forward Analytics smetric requests to AEP

Still need to have the Common SDK plug in on the site.  Then API call to send event data to streaming HTTP endpoint in AEP.  That can be lots of work as the communications, as in my case, involved multiple Adobe Orgs.  Sounds like you may have the same issue.  We ended up sending profile data via API to HTTP streaming endpoint. 

More to your question, we did something different for the analytics data.  We set up a data feed for the site in one org and directed the data feed to AWS S3.  There we developed a process to build a flat file by integrating the columns, hits, and lookup data into a single file in S3, then ingested that resulting file into AEP.  Thus, for each site using analytics, create hourly data feeds to a single S3 bucket, process them to create a single file, then ingest into the single AEP system.  I suggest you vastly rationalize the attributes ingested.  Doing this hourly kept the data flowing into AEP without hitting processing limits.

I had a case like this measuring video view time.  In reality most people who viewed a long video/movie for 10 minutes was enough signal to state they engaged with it.  Another case sent signals at intervals:  Started watching, Watch 25%, Watch 50%, Watched 100%.  Perhaps consider discrete approximations of the behavior you seek and post events at those thresholds.  Another case with very short videos (~30 seconds) all we cared about is if they started the video or watched to completion.

@timytim75 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!