Expand my Community achievements bar.

SOLVED

How to Pass Source Codes from AEM to Applicant Tracking System (ATS)

Avatar

Level 1

We recently built our career site on AEM. When potential candidates come to our new AEM site by clicking a trackable media source link (i.e., a link from our Facebook page), they then click a link on our new site which directs them to our applicant tracking system (ATS) to apply. That ATS tracks the source where our applications are coming from. In this example, it should track as Facebook. Currently, no source is being passed through from our new AEM website. Is there something we need to do on AEM to ensure the source code from our media URL (where the person actually originally came in from to AEM site) is passed through to our ATS? Thank you.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@PortChuck it is basically an website implementation question rather than AEM specific question.

 

Are you getting any campaign ID or any other specific query parameters from media sources when they click aem site link? If yes, use javascript to pass along that information to all subsequent down stream systems.

 

If no, then use JS to get referrer and build logic to determine the media and pass along information to down stream systems.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

@PortChuck it is basically an website implementation question rather than AEM specific question.

 

Are you getting any campaign ID or any other specific query parameters from media sources when they click aem site link? If yes, use javascript to pass along that information to all subsequent down stream systems.

 

If no, then use JS to get referrer and build logic to determine the media and pass along information to down stream systems.

The following has evaluated to null or missing: ==> liql("SELECT id, subject, body, depth, post_time, author.login, author.id, author.rank, metrics.views FROM messages WHERE topic.id = '${topicId}' AND is_solution = true").data.items[0] [in template "analytics-container" at line 82, column 31] ---- Tip: It's the final [] step 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 acceptedAnswer = liql("SELECT... [in template "analytics-container" at line 82, column 5] ----