Expand my Community achievements bar.

Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
SOLVED

Mapping custom events (from mParticle)

Avatar

Level 2

Can anyone point at a decent step by step guide to mapping custom events in Adobe Analytics. The Package sending the event is mPartcle.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hey oodaddy2 - the mParticle Adobe integration leverages Adobe's data insertion API. mParticle maps their custom events to Adobe's track actions, their page views to Adobe track states, and their e-commerce API maps to Adobe's as well. Their docs lay things out in pretty good detail: https://docs.mparticle.com/integrations/amc/event/

Once your mParticle data is in Adobe, you can leverage processing rules to map the data into props, evars, etc. and begin populating your reports. The guide you seek is here: Processing Rules

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Hey oodaddy2 - the mParticle Adobe integration leverages Adobe's data insertion API. mParticle maps their custom events to Adobe's track actions, their page views to Adobe track states, and their e-commerce API maps to Adobe's as well. Their docs lay things out in pretty good detail: https://docs.mparticle.com/integrations/amc/event/

Once your mParticle data is in Adobe, you can leverage processing rules to map the data into props, evars, etc. and begin populating your reports. The guide you seek is here: Processing Rules

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----