Not able to see couple of context data in sitecatalyst ,but able to see them in bloodhound | Community
Skip to main content
anand_modi
anand_modi
Level 2
October 16, 2015
Solved

Not able to see couple of context data in sitecatalyst ,but able to see them in bloodhound

  • October 16, 2015
  • 9 replies
  • 3126 views

Hi All,

We have implemented the latest iOS omniture sdk & I am able to see all the context data on all the pages in Bloodhound 

I am able to see all the data in Sitecatalyst/Discover ,but for couple of variables I am not able to see the data in Sitecatalyst.

What could be a possible reason for this as for the attached screen shot I am not able to see all the context data in sitecatalyst other than sourceofvisit

 

I have attached a screen shot for same

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by anand_modi

Hi Alexis,

 

I have got the solution,The issue is that when we set up a proxy in bloodhound win 2.2 then the data is not sent to rsid,but when I remove the proxy setting then

I am able to see the data.

 

Thanks

Anand

9 replies

anand_modi
anand_modiAuthor
Level 2
October 16, 2015

Can someone please help me out.Its extremely urgent

Alexis_Cazes
Adobe Employee
Alexis_CazesAdobe Employee
Adobe Employee
October 16, 2015

Hi Anand,

ContextData variable names can take some time to appear in the processing rule interface or in the mobile variable mapping interface.

However you can still use these names and set up the rules. The rules will work straight away.

See doc :

https://marketing.adobe.com/resources/help/en_US/reference/processing_rules_copy_context_data.html

"you can add a value by typing the variable name and clicking Add variable name context data: "

Best regards.

 

Alexis Cazes.

Senior Technical Support Engineer

Alexis_Cazes_
Alexis_Cazes_
Level 10
October 16, 2015

For the response above I have taken into consideration that you know that for contextData you need to create processing rules in Adobe Analytics or create variable mapping in Adobe Mobile Services and that you could not see the contextData in the one of these interface to create the rules. There were no screenshot attached to your initial email either.

anand_modi
anand_modiAuthor
Level 2
October 16, 2015

Hi Alexis,

 

The context data is already seen in the processing rule interface.I have attached  the screenshot of same.

Alexis_Cazes_
Alexis_Cazes_
Level 10
October 16, 2015

Please add a full image request sent with these contextData so we can review the issue further.

anand_modi
anand_modiAuthor
Level 2
October 16, 2015

Hi Alexis ,

 

I am attaching the screenshot of bloodhound.In the attached screen shot I am not able to get sourceofvisit value in teh Evar .Except for sourceofvisit I am able to get all the data.

 

Thanks & Regards,

Anand

Alexis_Cazes_
Alexis_Cazes_
Level 10
October 16, 2015

Hi Anand,

 

I need the foul content of the image request not just a screenshot. 

 

Best regards.

 

Alexis Cazes

anand_modi
anand_modiAuthorAccepted solution
Level 2
October 16, 2015

Hi Alexis,

 

I have got the solution,The issue is that when we set up a proxy in bloodhound win 2.2 then the data is not sent to rsid,but when I remove the proxy setting then

I am able to see the data.

 

Thanks

Anand

warrensander
warrensander
Level 6
October 16, 2015

one quick thing to check is the Batch Limit in your report suite setup in mobilemarketing.adobe.com (or in your json file). That is how many requests the app will batch up before sending them. If that number is too high then maybe you just haven't gotten to that limit in the version of the app you have hooked up to bloodhound and while you see it in bloodhound it's not going out to analytics.

try setting it to zero (0) in your development environment and see if things start showing up. However, don't leave it at zero for production a number like 5 or 6 is good so you don't eat your customers data network sending lots of analytics requests.

Terms & ConditionsAccessibility statement

Loading footer...