Adobe analytics - Tealium IQ Integration

Jayakrishnaa
Frequent Visitor
Jayakrishnaa

Team,

We are using tag management Tealium IQ for our all site to be tracked under adobe analytics and we are so new for the Tealium IQ tool as well. Recently we faced some technical glitch on our analytics, some of our stage site URL data are firing into production report suite and we want that to point to Dev report suite instead of prod. Please suggest how to point those particular URL's data in to dev report suite. Hope, that we need to write some JS code for the same, what that line should contain and where we can put the same on Tealium IQ.

Please let me know for any other information.

Thank you,
Jay.

 
7 REPLIES 7

Adobe analytics - Tealium IQ Integration

VIP
VIP VIP

Hi @Jayakrishnaa  - I think I saw your post on the Adobe forum too!

Are you firing your Adobe Analytics code using the integration or was it implemented as a custom tag?   You will want to use the Tealium-built integration from the Tag Marketplace in TiQ and you'll want to use extensions and mappings to detect which environment is running and set the Dev/QA/Prod variable properly.  

See https://community.tealiumiq.com/t5/Tags/Adobe-Analytics-SiteCatalyst-Tag-Setup-Guide-for-Tealium-iQ-... to get detailed information with screenshots and procedures.

 

After reviewing those docs, come back with your questions and we'll continue helping....  

 

 

 

Adobe analytics - Tealium IQ Integration

Jayakrishnaa
Frequent Visitor
Jayakrishnaa

Thanks for the document, it helped me to understand the integration of Adobe and Tealim IQ. Howevere, we have two URL's which we don't want to get those data to the production report suite. Instead we need those to Dev report suite. So, is there any specific way to do this. Can we use load rule for that? please guide me in that way if possible.

Adobe analytics - Tealium IQ Integration

VIP
VIP VIP

Hi @Jayakrishnaa  - there's many ways to accomplish this - it's probably best at this point for you to contact your Tealium account manager and/or open a Support Desk ticket.  

 

(Or,  give it a try and come back with some specific questions.)

Adobe analytics - Tealium IQ Integration

mvenkatesan
Occasional Contributor
mvenkatesan Occasional Contributor

Hello @Jayakrishnaa,

Currently we are setting the report suite id based on 2 approaches -

  1. Based in URL
  2. Based on UDO variable

 

Common for both the Approaches -

  • In Report Suite configuration under tag configuration map it to prod report suite so that we dont lose any production traffic (going in to dev suite)

scTag.png

 

Steps to Follow - Approach 1

  1. Create a JS variable 's_account'
  2. In SC tag mapping section map 'js.s_account' to 's_account'
  3. Create an Lookup extension per below screen shot, populate the s_account JS variable based on the URL 
    url_based.png
  4. This would direct the traffic to respective report suite.

Steps to Follow - Approach 2

  1. Request the Application Dev team to create a Application level UDO variable 'app_environment' 
  2. Variable has to be polutated based on the application environment
    1. dev
    2. qa
    3. prod
  3. Create an Lookup extension per below screen shot, populate the s_account JS variable based on the UDO Variable
    udo_based.png

Hope this helps and please do let me know if you need more info.

 

Thanks!

Highlighted

Adobe analytics - Tealium IQ Integration

Jayakrishnaa
Frequent Visitor
Jayakrishnaa

My sincere thanks for you giving this much of detailed explanation. I have read your points and I think we can accomblis our scenario with look up extension. In regards to that I have few clarification, please let me know.

FYI - we are using SiteCatalyst tag under tags tab.

Do we need to create new JS s_account variable? since I dont see any JS variable under the same name in our datalayer. if I create will it affect or overwrite any existing data. Also, I dont understand your second point  - 

  1. In SC tag mapping section map 'js.s_account' to 's_account'

please let me know what is that "js.s_sccount" and how to map it. let me know the steps to do that.

Meantime, we hope that we need to give the domain/URL and respective report suite under “Lookup Match” and “Output” field. Please correct us if we are wrong.

Adobe analytics - Tealium IQ Integration

Jayakrishnaa
Frequent Visitor
Jayakrishnaa

I was analysing on the article, @mvenkatesan and @mitchellt, which you have send and I got the point. You wanna create JS variable as s_account and map it to s_sccount. Please refer the below screenshot and let me know. 

Will it affect any exisiting account if I create new s_sccount and map it? I am bit worried due to this. Please let me know.

aaa.png

 

 

 

Adobe analytics - Tealium IQ Integration

mvenkatesan
Occasional Contributor
mvenkatesan Occasional Contributor

Hello @Jayakrishnaa,

You gt it right, you need to create a JS variable and map it to SiteCatalyst s_account.

Mapping Conflict - I believe currently you are using the Report Suite configuration option in the tag(left arrow in the below image).

scTag.png

  • When you do a lookup extension make sure to give the defaut value as a production report suite
  • You had mentioned that you will be using the URL in the lookup extension, please make sure that respective environment url's are matched exactly.
  • Please deploy them stage by stage, I mean publish them to Dev environment first and test it, then to QA and then finaly to Prod. In this way we can test for traffic and make sure we are not messing up.
  • After deplying to QA and testing it, before pushing it prodution try environment switching and test it in prod. Let me be more clear here - 
    • Open production URL
    • use the Tealium web companion or Tealium environment switcher to change the prod profile to QA profile and see weather the Sitecatalyst call is redirecting to SiteCatalyst production report suite.
      • top arrow shows the current environment
      • bottom arrow shows what needs to be selected, select QA and when refresh button appears click refresh.
        T_WebComp.png
    • This will help you to make sure that your extension will work as expected in production as well.

Hope this helps and please let me know if you need any help.

Thanks!