Expand my Community achievements bar.

SOLVED

Migrating from an existing Adobe Analytics implementation

Avatar

Level 2

Hi,

I've an existing Adobe Analytics page code. I've checked the "Adobe Analytics page code is already present" button and changed the Object name to "s2".  Then i created a rule to fire on all pages. I'm expecting to see the page code on where there is no existing Adobe Analytics page code. But it doesnt seem to work on that way. I can see the all page rule is being fired by enabling debugger in console. However the Digital Pulse Debugger does not show any data. It seems like it never loads the s_code.js in order to gather analytics data.

Can you be any help with this problem?

Thank you very much.

Burak

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

In your Adobe Analytics "tool" settings (same place you checked the "already present" checkbox), are you using 'Managed' s_code, or have you set the URL for it?

If managed, you would need to click the 'Open Editor' button and paste in your s_code there.

If URL, can you confirm that opening that URL directly in your browser loads the s_code.js file?

 

Hopefully that helps you to resolve the issue, but if not, please reply back to let us know so we can help further.

Kind regards,

- Carey

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

In your Adobe Analytics "tool" settings (same place you checked the "already present" checkbox), are you using 'Managed' s_code, or have you set the URL for it?

If managed, you would need to click the 'Open Editor' button and paste in your s_code there.

If URL, can you confirm that opening that URL directly in your browser loads the s_code.js file?

 

Hopefully that helps you to resolve the issue, but if not, please reply back to let us know so we can help further.

Kind regards,

- Carey

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] ----