[AEP Community QnA Coffee Break] 7/21/22, 10:30am PT: Adobe Experience Platform Experts Travis Jordon

[NimashaJain]

Join us for first Adobe Experience Community QnA Coffee Break taking place on 21st July,22.

There will be livestream session where our AEP experts Eric Matisoff, Rudi Shumpert and Jeff Chasin will provide a deeper dive into Adobe's advanced data collection capabilities.  It will be followed by coffee break with Travis Jordan, Senior Product manager in digital experience. Coffee breaks are live threads which are answers instantly by the experts.

Details of live stream session -> here

Coffee break Timings  21st July @ 10:00 AM PDT/10:30 PM IST

How to participate in Coffee break 

• Must be signed into the Community during the 1-hour period 
• Must post a Question about Adobe Experience Platform
• THAT'S IT!  *(think of this as the Adobe Experience Platform Community equivalent of an AMA, (“Ask Me Anything”), and bring your best speed-typing game) 

Instructions

• Click the blue “Reply” button at the bottom right corner of this post
• Begin your Question with @DoMoore 
• When exchanging messages with Travis about your specific question, be sure to use the editor’s "QUOTE" button, which will indicate which post you're replying to, and will help contain your conversation with Travis.

Travis Jordan is currently a Senior Product Manager on the Adobe Experience Platform product team. He is an outcomes focused product leader with 10 years of experience in product strategy, design, marketing, and delivery. He is obsessed with conceptualizing and shipping amazing tech products that solve real customer problems and drive business value. Travis is also the Founder and Owner of Instructional Design Central (IDC) with a Master of Science Degree in Instructional Technology from Utah State University.

Eric Matisoff is the Principal Evangelist for Analytics & Platform at Adobe with 10+ years of digital experience working with data and visualizations. Eric has spent his time in the industry driving implementation, optimization, analysis, and data integration projects for dozens of Adobe customers on hundreds of digital experiences across all verticals. Eric works with Adobe’s largest accounts to help align their business strategies to the vision Adobe has defined for data ingestion, analysis, and action.

Jeff has been working with computers since learning Basic and playing Star Raiders on an Atari 800. He works closely with businesses to build scalable systems and repeatable processes. He helps companies like Marriott, Apple, AT&T, and others increase the value of their digital investments. Jeff came to Adobe with the acquisition of the Satellite technology management platform in August of 2013. He’s now a Sr Evangelist for Adobe Experience Platform and an advocate for improving the developer experience.

See you all with AEP experts!!

[tksol207]

We have a situation where we are re-tagging 2 sites with existing Analytics (appmeasurement) implementations with the Web SDK. These sites have 2 different solution designs and we will need to send data both into AEP directly and into 2 different (new) Analytics report suites.

Is best practice here to create 1 schema within AEP to receive data from both sites and use custom schema fields for the props/ eVars / events instead of the Adobe Analytics predefined field groups? Or would it be better to have 2 schemas, one for each solution design, that are based off of the Adobe Analytics predefined field groups?

[EricMatisoff]

I'd say both are options depending on your long-term goals.

You may want to utilize a single schema if you foresee a lot of overlap in terms of the types of data that you collect between the two sites.

If there's a very low number of custom fields that overlap between the two, and you don't ever foresee a world where the data from the two sites should be merged/combined for analysis/activation across sites, then it may make sense to keep them separate.

IMO, most likely, a single schema will work for you.

[rajivs93815582]

@DoMoore  Till today I was only passing single datalayer variable into a data element. How do you pass the entire object? How does Event forwarding parse through the different variables within the object?

[EricMatisoff]

Great question! You can actually return the entire object using a Data Element Type of JavaScript Variable like this:

Then Map that Data Element to the Data Section of your Web SDK Event in the Rule Action

[Chasin]

There are a few different Data Element types that can be used to get, set, and return an object. 

Cookie, Custom Code, JavaScript Variable, Local Storage, and others, for example. More details here: https://experienceleague.adobe.com/docs/experience-platform/tags/ui/data-elements.html

[SatheeskannaK]

@DoMooreI have about 20 different segments which i need to export and all it has data about profile email. I don't want to export 20 segments rather one file with email address in one column and part of segment flag (yes/no) for each segment. Total it will be 21 columns. Is there a way we could achieve this?

Thanks!

[Chasin]

Hey @SatheeskannaK, if you are talking about exporting a file (table) with one column of email addresses, and 20 more columns for each segment, with "yes" or "no" in each of those segment columns, I think the easiest way to approach that would be through Query Service. Or if you currently have access to Data Science Workspace, or using the Platform APIs. You could also check out this post for other ideas.

[tksol207]

For data ingested to AEP via the Web SDK, is 15 minutes the minimum time that it will take for an event to be available for activation without use of a custom solution to get the data faster (like using the HTTP API)?

For example, if we want a click event that includes ID stitching information (e.g. a user identifies themselves by providing personal information to download a brochure) to be available ASAP to share downstream with a call center rep who would expect a call from that customer, would the Web SDK be quick enough to provide this in real time?

[Chasin]

If your use case is to send event data from your site/web app via Web SDK to Experience Edge, and then you need to send that event data to a call center or other system via web API, you could do that through event forwarding, and it would be very fast. "Real time" there would largely depend on the call center API performance.

If you need to get profile data to some downstream system like a call center CRM or issue management system, you could look at an HTTP API Destination https://experienceleague.adobe.com/docs/experience-platform/destinations/destination-types.html#stre... for streaming Profile export.